I have about 24 Z-wave Smartwings shades that generally work fine with the Hubitat built in driver ("Smartwings Z-wave Shade"). However, in trying to group and control them in the Room Lighting app I've run into trouble. From the threads I've read, I gather the gist of the problem is this:
Room Lighting does not send open/close commands, but only set position.
The smartwings z-wave driver has the open/close percentages reversed from usual (99% is open, rather than 0%).
I can edit the "activation setting" to open them with RL, but I can't edit the "off" setting to close them.
What's my best workaround here?
Is there a still working user created smartwings z-wave driver I should switch to?
Is there a way to make RL send a close command instead of a position one?
Can I edit the code on a native HE driver to fix the reversal, and where would I do that?
Do I create a virtual shade for every blind and a pile of rules to transpose the correct value to the actual shades? Sounds like a lot of work for 20+ shades when I don't need another full page of go-between virtual devices.
Can someone fix the native smartwings driver to act like every other shade driver?
(this issue also makes the shade animation on the dashboard tiles opposite of reality which is another annoyance of this driver reversal)
Playing around with it a bit. But the only way to do that is to use mode or time period presets, and since I just want to define "closed," I'm setting a single time period, and then it wants me to enter two states: "blinds closed" and "preset off." Is that not the same thing? I've gotten it so my assigned activation button works to open and close the group, but the activation button both closes and opens them instead of just opens, even though it's only set as the activator. I mean I suppose I could intentionally set it up that way, but I was leaning towards force open and close since poor reporting is a thing, and sometimes only half a group will respond to a command.
Just using button controllers and assigning them multiple blinds has been a far easier way to control a group of blinds, I was really just hoping the built in group functionality to create groups to work with for future automations and rules would simplify my life, but it's looking like it will do the opposite.
Hmm, I guess calling my time period "blinds closed" is causing some of my own confusion. I'll play with it. When using RL this way then I assume I'm defining my two states within the lighting period subsection, rather than within the main rule then?
OK, sorted myself out. I didn't realize I could use "no time periods" for a preset closed setting (which is much simpler), and realized I accidently set my activate button as a toggle instead of a push button. I think I can work with this- thanks.
Still curious why this driver is backwards and if it's easy to fix. Would save a bunch of headache.
