feat: hub-based architecture for automatic shade discovery#29
Open
safepay wants to merge 19 commits intopatman15:mainfrom
Open
feat: hub-based architecture for automatic shade discovery#29safepay wants to merge 19 commits intopatman15:mainfrom
safepay wants to merge 19 commits intopatman15:mainfrom
Conversation
Reuse the home key from already-configured shades so adding subsequent shades skips the key step. Show human-readable shade names from the hub in the device picker. Allow selecting multiple shades at once instead of repeating the flow for each one. Default to hub fetch as the key method.
…ated descriptions
Add ShadeCapability lookup to replace hardcoded model string checks for tilt/tilt-only selection. Add velocity number entity (0–100) and pass velocity through all movement paths including open/close. Remove redundant device_info property overrides and deduplicate hex parsing.
…harging control lock
This was referenced Apr 11, 2026
Author
|
Sorry about the monster PR, but this brings the integration in line with modern HA architecture and should work with most blinds except the ones that have multiple blinds. Thanks for a great integration. My setup is working perfectly. But I don't own all the blinds so I can't test everything. At least it has the necessary information to move to the next step regarding dual and triple blind support, but that requires a bit of a refactor. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is this?
This PR takes a different approach to managing PowerView BLE shades. Instead of setting up each shade individually as its own config entry, this introduces a hub-based model where a single config entry represents your PowerView home and shades are discovered automatically via BLE.
This includes all the work from #25 and #28 which I have closed (but left the branches).
What this PR changes (hub-based)
You set up the integration once — point it at your hub (or enter the key manually) — and shades are automatically picked up as they're discovered over BLE. New shades appear without any additional config. Shade names are pulled from the hub so they match what you already see in the PowerView app.
The main changes:
__init__.py— manages a collection of coordinators (one per shade), registers a BLE callback to pick up new shades, and fetches friendly names from the hub APIconfig_flow.py— simplified to a single setup step: choose how to provide the home key (fetch from hub, enter manually, or skip)number.pyWhy I think this is the better path
Closes #3
Closes #8
Closes #21
Closes #27