Closed berland closed 4 years ago
If you press the two blue buttons both rails will be in the middle with a duette shade.
You want the both at the top to be fully open
- Can you please infirm me what sequence of two buttons must be pressed (with the latest build) to achieve this?
@berland and @mstroeve I think the latest build is stable and good to go, and the ReadMe matches the reality, so I would like to open a Pull Request for it. Is that OK with you?
Perhaps a picture makes it clearer. What I intended is
- Press the two RED buttons => room is dark
- Press the two BLUE buttons => room is light
Pressing the two RED -> dark - this is correct. Pressing the two BLUE does not make sense, because the secondary rail cannot be below the primary (bottom) rail.
There are two possibilities for "room is light", both rails at the bottom or both rails at the top, clicking UP on both, or DOWN on both yields this. So the binding works correct as far as I can see.
When both are to be sent down, the primary/bottom rail must get the DOWN command first if it is not already at the bottom.
When both are to be sent up, the secondary rail must get UP first, otherwise the bottom rail stops at the secondary rails current position.
@berland and @mstroeve I think the latest build is stable and good to go, and the ReadMe matches the reality, so I would like to open a Pull Request for it. Is that OK with you?
Ok with me! I can't find any further issues. Thanks again for the good work!
For Duette shades, the top position of the shade is also steerable, but this is not supported by the binding.
Supporting this is only a matter of a new channel and adding a parameter
position2
in the json body, like this:{"shade": {"id": 63778, "positions": {"position1": 0, "posKind1": 1, "position2": 1000, "posKind2": 2}}}
and POSTing this json to
http://powerviewhub/api/shades/63778
posKind2: 2
is important to get it to work.(and interpreting this
position2
while polling).