Skip to content

Config flow for Velux integration#49348

Closed
bramstroker wants to merge 15 commits intohome-assistant:devfrom
bramstroker:feature/velux-config-flow2
Closed

Config flow for Velux integration#49348
bramstroker wants to merge 15 commits intohome-assistant:devfrom
bramstroker:feature/velux-config-flow2

Conversation

@bramstroker
Copy link
Contributor

@bramstroker bramstroker commented Apr 17, 2021

Breaking change

Proposed change

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

@iMicknl
Copy link
Member

iMicknl commented Apr 18, 2021

@bramstroker are you aware that there is another PR open (#42773) with the same functionality? I see it is still limited, but perhaps there are other improvements that can help your PR.

Copy link
Member

@iMicknl iMicknl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just had a quick look, happy to give it a more extensive review later on.

@bramstroker
Copy link
Contributor Author

@bramstroker are you aware that there is another PR open (#42773) with the same functionality? I see it is still limited, but perhaps there are other improvements that can help your PR.

Ik was not aware of the other PR @iMicknl. It contains mostly the same functionality, but also support for tilting covers. However the other PR seems quite stale tot me atm. Not sure what the best approach would be as I am a new contributer to home assistent.
Close mine and wait for the other PR to progress? Or continue my development in this PR to get this mergeable asap?

Thanks for your review BTW. This is useful anyway.

@iMicknl
Copy link
Member

iMicknl commented Apr 18, 2021

Close mine and wait for the other PR to progress? Or continue my development in this PR to get this mergeable asap?

To be honest, I wouldn't know either. If the other PR is stale and not in development anymore, it would make sense to see if you could use the best of both PR's 👍🏻.

It can take a while until a PR is merged due to the huge backlog, thus this could also be the reason it is marked as stale. Perhaps you could discuss this with the author of the other PR? Or wait until a core member chimes in.

@bramstroker
Copy link
Contributor Author

Alle review remarks are resolved. Could you guys please have another look?
Maybe it's a good idea that I also merge the branch for velux light support #49338 into this one, so it can be one PR?
I'm pretty sure there will be merge conflicts, so better to fix them now.
What do you think?

@bramstroker bramstroker marked this pull request as ready for review May 16, 2021 18:47
Copy link
Contributor

@mtdcr mtdcr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Handling connection failures as described in my inline comment would be nice, but as it doesn't introduce a regression, I consider it optional.

await hass.data[DATA_VELUX].async_start()
veluxModule = VeluxModule(hass, config_entry)
veluxModule.setup()
await veluxModule.async_start()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

async_start() may fail (see #34844), in which case you should raise ConfigEntryNotReady. That would really resolve #34844, I guess. The issue was closed due to inactivity.

"invalid_auth": "[%key:common::config_flow::error::invalid_auth%]"
}
}
} No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No newline at end of file.

@mtdcr
Copy link
Contributor

mtdcr commented Jun 4, 2021

Maybe it's a good idea that I also merge the branch for velux light support #49338 into this one, so it can be one PR?
I'm pretty sure there will be merge conflicts, so better to fix them now.

I wouldn't recommend adding more complexity to this PR. Conflicts can still get resolved once one of the PRs got merged.

@github-actions
Copy link

github-actions bot commented Jul 4, 2021

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 4, 2021
@github-actions github-actions bot closed this Jul 11, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants