Config flow for Velux integration#49348
Config flow for Velux integration#49348bramstroker wants to merge 15 commits intohome-assistant:devfrom
Conversation
|
@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. |
iMicknl
left a comment
There was a problem hiding this comment.
Just had a quick look, happy to give it a more extensive review later on.
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. Thanks for your review BTW. This is useful anyway. |
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. |
Co-authored-by: J. Nick Koston <nick@koston.org>
…ore into feature/velux-config-flow2
… the global hass object, so we can have multiple instances
|
Alle review remarks are resolved. Could you guys please have another look? |
mtdcr
left a comment
There was a problem hiding this comment.
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() |
| "invalid_auth": "[%key:common::config_flow::error::invalid_auth%]" | ||
| } | ||
| } | ||
| } No newline at end of file |
I wouldn't recommend adding more complexity to this PR. Conflicts can still get resolved once one of the PRs got merged. |
|
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. |
Breaking change
Proposed change
Type of change
Example entry for
configuration.yaml:# Example configuration.yamlAdditional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: