I've got a large installation of smartwings zwave motorized shades. Here's the issue. The shades respond as expected to close or set position commands but won't respond to open commands. The open command seems to set the position to 100%, but the shades won't respond. Set the position to 99% and they work like a champ. As a result they won't respond to voice commands from Alexa to open. Is this an issue with the driver? The driver doesn't have a way to limit the open % to 99.
The workaround I've come up with is to build a rule that checks to position of every shade every time a shade position changes. For every shade position at 100%, it changes it to 99%. It kind of works, but is tedious to build, not highly reliable, and probably resource intensive.
My z-wave Smartwings shades respond to "open" on the device page and from Alexa. They open to 99%. If I "set position" to 100% they do not respond. 99% is perfect. I wonder if that is related to the limit settings when the shades were first setup.
I probably have close to 30 shades and all of their limit settings were set during installation. If it was related to that, I'd expect at least a few would be fine.
It appears that "open" from alexa equates to 100% which the shades don't like. I'm curious why alexa works for you. If you're looking at a shade device page when you do an alexa open, does the position go to 100 or 99?
New user to Hubitat here - I'm also experiencing the same issue as I'm attempting to setup my Smartwings Zwave shades. Open position is equivalent to position 99, so that when I try to setposition 100 or utilize a Google Assistant Integration, they won't open as they don't seem to like 100%. Would love any helpful tips for a Hubitat newbie
I just installed my smartwings shades this week, and have the same issue. 'Open shade' from Alexa issues the 'setPosition' command with a value of 100, which is invalid. Smartwings apparently only accepts values from 0-99 as valid. 'Set blinds to 99%' works fine from Alexa, but not exactly wife friendly... Is there a community z-wave driver that we can use, or is there a way to get the official driver to limit values to the accepted range?
I also attempted setting up a rule for this, but could not get it to trigger, since the command is rejected before processing (thus no position change) and there is no event that I can trigger on.
I haven't been able to find a proper fix so played around with a number of work arounds. While tedious to set up, I wrote one simple rule per shade. Trigger is if the position is ≥ 100, then set position to 99. The open command works perfectly.
Originally I tried a single large rule for all shades but found it killed the hub performance when you did any kind of mass shade opening (open all).
As noted in the other thread referenced above it appears that the driver issue seems to be fixed but here's a related problem that still exists.
While I can now issue an Alexa voice command to open a specific shade, it responds as expected. However if I create a group of shades in room lighting and expose it to Alexa, the open voice command will not function on the group. Close and set position commands work as expected, just not "open".
Does this sound like a room lighting issue, driver issue or some combination of the 2?
I have a C8 and I’ve been sitting on the fence for a while about trying a Smartwings shade. I have only 2 Zigbee devices and they are Hue battery operated motion detectors so they aren’t repeaters (and not close to where the shade would be even if they were). Everything else I have is Z-Wave. So I just want to be sure I’m understanding your post correctly. As I understand it, even though your shades are Z-Wave they are working fine with the community Zigbee driver, correct?
Got it. I was thinking that, but since the thread title was Zwave...
So, as is, are you happy with them?
I have a window on the far side of my room that directly faces my tv and mainly just want to close it when I'm watching tv while it is still light outside.
My experience with the zwave version (I have 25 installed) is that they generally work pretty well. There was an issue with the driver that it wouldn't respond to "open" commands (you could set the position to 99% with no problem) but that's been fixed.
I do notice when you issue a mass command (i.e. open all shades) for this many shades some of the shades don't respond. This might be a hub loading issue as I have a lot of zwave devices, so I'm planning to upgrade to a C8+. In the mean time, when I do a mass command, I just repeat it in the rule to catch the errant shades.
So other than I am in the wrong thread , yes I am happy with my blind. I only have one blind though so I am not necessarily a good use case. Zigbee paired up well to Hubitat. The built in Hubitat Zigbee driver did not work for me.
@Aussie, if you had problems with the Zigbee driver, I would recommend starting a new thread about your experience (since this is about the ZWave version). Other Zigbee friends will be able to help you and admins could also make sure the problem is resolved (either your setup or the driver itself). You should also start it in the built-in drivers section so that the devs also see it. (Built-in Drivers - Hubitat)
I'm looking at buying a few and ws thinking of getting the Zigbee version so very interested in the outcome here
, yes I am happy with my blind. I only have one blind though so I am not necessarily a good use case. Zigbee paired up well to Hubitat. The built in Hubitat Zigbee driver did not work for me.
)
and accidentally hijacked the thread!!!
