Add integration doc for Leviosa_Shades #17063
Conversation
|
Hey there. I'm sorry but I don't understand what is happening here. I originally created #17062, using |
|
Probot never asks you to rebase to Wanting to merge a |
Thanks you so much for taking the time to enhance this document, I really appreciate your help!
|
Changes applied as requested. Thanks for your help! |
| - If you have more than one Leviosa Zone in your Network, Home Assistant will display a list, with one IP address for each Leviosa Zone discovered, in the same order as they were discovered. Once a Leviosa Zone is configured in Home Assistant, it will not appear in this list. Refer to the next section to find the IP address of each zone group. | ||
| - If you have only one Leviosa Zone, then you'll be taken directly to the screen to enter the Leviosa Zone name and shade group names. | ||
| - You can name the shade groups as you wish. They do not have to match the names already in the Leviosa App. | ||
| - A `cover` entity for each shade group will be ready for you. An additional `cover` entity is created with the name of the zone (prefixed `all_`) to move all groups in a Leviosa Zone at the same time. |
There was a problem hiding this comment.
The additional all_ group/entity should not be created. It is not the responsibility of integration to provide that.
There was a problem hiding this comment.
Hi! thank you for taking a look at this. I would like to clarify that the Leviosa Zone can handle 6 shade groups, plus a special group (called Group 0 in the Leviosa Zone hub) that allows moving all Blind groups up or down. The additional shade group 'all' is just a way to expose this Group 0 functionality to the user, otherwise there would not be a way to use it. If after this explanation this appears incorrect, could you please help me to understand how the Group 0 should be exposed?
There was a problem hiding this comment.
I think it should not be exposed? They can be grouped in Home Assistant if one wishes to do so.
There was a problem hiding this comment.
I see your point, and I agree that all shade groups could be grouped; that would produce a different user experience. I'll explain: Group 0 commands all shades to move at exactly the same time, using only one RF command over the air. All motors react to this command immediately, as they all belong to Group 0 in addition to their configured group. If I understand HASS grouping correctly, HASS would send a command to each Group in the Leviosa Zone in rapid succession, which would start raising the shades at different times, possibly with a different order each time. This happens because the Zone would send multiple RF commands over the air, one for each shade group (RF transmission is slow, so it takes about 100 ms per command). I'm sure this behavior would lower the 'wow' factor that is expected from all blinds reacting at exactly the same time. Hope this clarifies why the 'all_' shade group is important for these blinds.
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
…ty Services work in HASS
|
Closing PR as the parent PR has been closed. |
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.