Add basic support for HomeWizard v2 API configuration flow #135414
+447
−28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed change
This API allows the user to configure the device via the v2 API. This API is now using a authorization step similar to Hue, where the user has to proof the possession by pressing the button on the device. Therefore the config flow has to be adjusted.
To keep this PR a bit concise, I didn't implement reauthorization, extensive error handling and migration. This will be done in follow-up PR's if that is okay.
Documentation update is WIP.
You can test this with real hardware, ask me via a DM on discord for instructions.
Waits for #135315
Type of change
Additional information
Checklist
ruff format 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
.To help with the load of incoming pull requests: