Definition of open/close in a top down bottom up shade

Normal shades are pretty well defined, open/close are readily apparent just by looking at a window. Position is also defined, 99/100 is fully open, 0 is fully closed.

But what about a TDBU shade, with two separate bars. The bottom bar is pretty easy and should probably mirror any other shade.

But what about the top bar? What does open mean as the bar at position 100 (aka at the top) could mean either fully open or fully closed depending on what the bottom bar is doing. Similarly, the top bar at position 0 (the bottom) means the window is fully open, which is opposite of a normal window shade.

So what should open and close mean for the top bar of a TDBU shade? Should open bring the bar to position 99 or to position 0? And what should the top bar report for open/closed - should it update its value based on the position of the bottom bar to reflect what is actually happening physically?

I suppose this is more of a thought experiment more than anything, as I’m not writing any drivers. But as I’ve got a handful of motorized TDBU shades, I’ve somewhat struggled with implementation due to the unique nature of these shades.

Can you successfully control these as two separate shade motors?

Yes but I’ve paired them via zwavejs and home assistant.

1 Like

I also have a few motorized TDBU. Each of mine are paired as two separate shades - the top bar, and the bottom bar. As you wrote, if you use the bottom bar only, it works just fine with the default drivers.

However, I typically use the top bar only, and it is always exactly opposite the default language.

This works fine as I am aware of the issue, but it makes dashboards unusable for my household.

  1. First was a plea for Hubitat to revise the default language from open/closed to up/down, but that has fallen on deaf ears.
  2. Then I tried to edit the driver on my own. That was a disaster.
  3. Then I tried to reset /switch the top bar so it would think it was the opposite of what it really was. That only worked for one cycle, and then it "corrected" itself.
  4. Next (probably over the holiday or this coming weekend), I'm going to try this: TDBU shades - revising shade driver for top bar - #4 by calinatl