I'm using a custom driver for my blinds only because I can't stand that when talking about blinds...100% = Open.
That number from 0 to 100 should be the amount of covering they are doing...not the opposite.
Is there any chance Hubitat could add a switch for reversing that for people who feel the same way. It "seems" like that would be easy? ZERO should be no covering...not fully shut IMHO.
It was confusing to me until I learned why it's done that way... Consider the blind/shade a light -- 100% equates to full on (max brightness), and 0% equates to off (no light).
If I’m following OP, their expectation can be met by using a custom driver?
It’s possible this could be added to a built-in driver as a configurable option.
Sometimes they avoid adding too many options like that to built-in drivers, to avoid overcomplicating the hub UI. That can be a good use case for community developed alternatives.
Thanks! Yes, the custom driver using the opposite values. I truly appreciate the guys that code custom fixes...but would like to think built in support would be the best answer long-term.
With custom...you just never know when they'll just move on to working on something else.
Yes, just think that would be a fairly easy change and a simple improvement to the driver....which I'm sure is Hubitat's goal. But, there are a billion new things changing all the time...so they have my sympathy!
So change the name of your blinds, so that "Living Room Blinds" is now named "Living Room Sun", so if you want full open blinds you will be setting the sun to 100% (not the blinds) Just joking around
I was in the same camp. Took me a while to "get over it." Turns out it isn't a SmartWings thing but in fact an industry norm. I'm trainable but it was difficult
If others agree and post here accordingly, I’m sure it’s possible the devs will consider the feature request.
FWIW you may not have much to worry about wrt to this concern:
For a zigbee device driver at least.
If it works now, it’s likely to continue to work for a long time, although it’s of course possible that major/fundamental platform changes in the future could disrupt that.
But it’s not as if the code in question here is for integrating with an outside service’s API.
That would be at much greater potential risk of breaking as time goes on without ongoing/active development of such an integration.
I have (community-developed) device drivers that are still working fine even though they haven’t been touched/updated since Hubitat came into existence eight years ago.
Yes, think of contact sensors. Open means the door is open. If you were to assign a % to how "open" it is, then closed is 0%.
Think of Valves. Closed would also be considered 0% open. We normally refer to valves as being a % open, not a % closed.
It really depends if you view curtains as opening to let the light in, or closing to keep the light out. The default state of a window with no shades or curtains is not 0% blocked, it is 100% open.
Glass half full or half empty, it's all the same. Just be a positive guy and say 100% is open and bright and 0% is closed and dark, if it's such a problem stick with the custom driver that works, you will always have more flexibility with custom drivers than stock as they should be drivers, I would be very surprised if they do add this feature as the way it is at the moment is the standard.
I’m not gonna get into what I would guess I call semantics. It’s a feature. I would like to see. No more no less. It seems like a reasonable request that it appears others would like as well and I’ll leave it at that.
I found a work around today if your shades can do it. I just updated a second shade I had to Matter. The new MAtter motor has a new type of remote and when I set up the shade I didn't realize I had the remote upside down. So The motor direction was reversed. 100% was closed and 0% was open. So if you can reverse the motor direction on your shade it would be as you want it.
I did not want this and had to reverse the motor direction back but it would be a way to set it up until a driver could be updated, if it ever is.
I can flip this just by changing between the Hubitat driver and the custom one. (which btw must mean at least someone agrees the Hubitat values seem wrong)
However,,,,While I SO RESPECT the people writing custom stuff...I prefer running built in/native long term.