@Eric.C.Miller I'm still having issues. I'm using the generic zwave driver but still experience issues where the Blinds partially respond and then stop when automating multiple blinds at the same time.
Controlling the Blinds directly from their physical remotes work great, even in groups. It really feels like a hubitat or driver issue.
I've reached out to support a couple of times but no response. Is there anyone who can help debug this issue please? I really want to be able to automate open and close of these blinds and have a huge investment in the through my house so any help would be appreciated.
How about changing the driver to generic z-wave dimmer and try to command multiple roller shades with dimming instead of shade open/close. Do they have the same issue? I have 2 shades out of 10 that have these weird issues you described and they have nothing that do with the the driver. These 2 roller shades have firmware issue. The 8 working shades are from zebrablinds.com and work perfectly fine.
The way I have mine set up, the command that I send when I push the button (on the Pico remote) is a either a Raise Shades (open), Lower Shades (close), or Position Shades with a value that represents the percentage. Using that kind of command, I would think the shade would either receive it or not. If it receives it, I would think it would then be up to the shade to properly execute it without further input. Of course we have no way of knowing how similar my shades are to yours . . .
As I recall, before I unassociated the remote that came with the shades (the two-button Graber), it acted totally differently - it was like a wired remote - as long as you held the UP button the shade would move up. As I mentioned to you in the earlier post, I was not able to pair the shade with the hub until I unassociated the original two-button remote from the shade.
I reached out to Zebra blinds and let them know my issue. They requested some logs that showed the firmware version (11.2). After researching how to get the firmware version using the Zwave Basic Tool I sent them along.
They confirmed this morning that I may be on a firmware version that has Zwave group messaging issues that might be causing this. They requested I purchase the HomeSeer Zwave OTA firmware update kit and will send me an updated firmware to try out. Fingers crossed.
After engaging with ZebraBlinds.com support they informed me I was on an older firmware version for my blinds (v11.2) and there were some improvements to Z-Wave group messaging in their 11.3 version.
I was able to confirm I was on firmware V11.2 using the basic Z-wave Tool.
Zebrablinds recommended I get the Homeseer zwave flashing tool and then provided updated firmware. The upgrade process went seamlessly and all my blinds are now on the new firmware.
After the firmware my issues have been resolved. I'm using the generic Zwave shade driver and all blinds are responding to automation and grouping. Very happy after months of frustration.
I wish I'd seen this earlier. @bcopeland has written a z-wave firmware updater tool for Hubitat. And several of us have used it successfully to update multiple z-wave devices.
@darron the errors are due to a parsing error in the Zwave shade driver. The pointer to trim the payload value for "hexVal" in the String description is off by 21 characters and is grabbing the "t:" from the last part of "isMultiCast:" The code should be something like:
Hello, apologies for resurrecting a thread, but I read something in here that I'm interested in finding out more about. @darron, you had mentioned that you were using your shades in groups.
I was just wondering what advantage this brings you? I also use Zebra Blinds (just set them up), and have a few automatons plugged into them.
Are the groups just for ease of programming, or are their other benefits?