(Resolved) Moving from Wink - Bali/Somfy Shade Woes in Hubitat. Help!

@yashvind and @ZebraBlinds,

My Graber shades have firmware version 11.2

Is it possible to get and apply the updated firmware?

I am experiencing all of the behaviors you have described. Random positions, red light, ignoring commands, etc. Somewhere along the way we figured out reversing the requested direction and letting the shade open or close would reset its ability to accept commands.

I've wasted many hours in the Rules Engine and groovy trying to figure out why my shades and virtual shade group driver were not working.

I don't recall ever having issues when they were on the Wink Hub, and the Graber remote works flawlessly, so I assumed the issue I've been having over the past couple of months was related to my code.

Thanks

I just updated my original post with details. Please give it a read.

3 Likes

Where did you find firmware code for your shades? I too have Bali/Somfy shades with these exact same problems. Complete hit or miss where it stops and then I get the red light. Other times it works.

The first post above said to contact the Zebra Blinds rep. That rep is just a couple posts above...

2 Likes

Thank you, seems like I need to wait to PM a user here as I just signed up today. I recently installed this Hubitat as part of a total renovation and I've got a lot to learn programming. I installed that custom z-wave driver mentioned and confirmed my roller shade firmware is 11.2

I got a few (30-ish) fairly new bali z-wave blinds that I'm moving from a flaky c-4 to a new c-7. Had all sorts of flaky open/close/partial/nothing happens/etc. issues on the c-4 which I attributed to it having some sort of fundamental problem (every device having problems, not just blinds)...scrambled db likely. Rather than mess with it forever I bought a C-7 and am in the process of transfering things over slowly.

So on the new C-7, I've moved over 6 blinds last week and have had hit or miss issues. I wonder if anyone here has suggestions? Firmware of the blinds is 12.1. I've tried both the community driver from @ericvitale and the generic zwave blinds driver but still get missed close/open calls (i.e. nothing happens), very slow to start to respond, etc random fun. I have noticed the on/off seems to work better/faster than the open/close calls from the device page. RM4.0 rules don't seem to work well regardless of which call I make. This seems true for both drivers. I've done nothing to group them either with the multi-remote from bali or HE, just list them all in RM as on/off as approp.

Thanks in advance for any insights!

My understanding is that the issue is with 11.2 or lower firmware versions. So if your are on 12.1, not sure what could be the root cause! @ZebraBlinds any insight?

I have about 25 Bali blinds at the moment and I have similar problems. They were bought in two separate purchases a year apart. Because of the timing, I got two different revisions of their blinds with different firmware. 85% of them work great and consistent but there are several that are flaky and it is almost always the same ones. The odd thing is the problems occur on both revisions of the blinds. Its not distance or other basic things as far as I can tell. I have PM @ZebraBlinds numerous times but I had no luck in getting a response for the new firmware. I want to purchase more but I do not want to add to the mix if the issues can not be resolved. When I use the Somfy ZRTSI driver, I get the best results.

What is your firmware version?

is that for the zwave enabled blinds or the 'gotta have the special hub deal thing'? Also, I don't see a 'current' version of that, got a link you can share?

11.2 is the firmware on the first batch and from the newer batch 12.1

Try this, its a forward of another members...

[RELEASE] Somfy ZRTSI Code Share, post:1, topic:40998"]
A driver for the Somfy ZRTSI [s-l640] Code hubitat/somfy-zrtsi.driver.groovy at master ยท augoisms/hubitat ยท GitHub Also available on Hubitat Package Manager. Features Supports My Position. Has the option to use a value of 50% as a My Position command. This is handy for allowing voice assistants to issues the command. Tracks state internally. The ZRTSI is already a one-way communication device, but it has been reported that it does not accurately report the "state" of each channel, so thi....

Can you exclude you blinds on 11.2 from the hub and run automation on 12.1 for few days to see if you continue to see issue just on 12.1's as well?

Cheers. Appreciate the link. Not getting goodness to flow tho. I get this in the logs and the device page never updates so it just shows opening/closing... I'm getting much quicker runs using the generic blinds, which saddens me as dat'ain't good.

dev:492020-10-03 01:13:19.627 pm errorjava.lang.NullPointerException: Cannot invoke method intValue() on null object on line 133 (off)

dev:492020-10-03 01:12:06.602 pm errorjava.lang.NullPointerException: Cannot invoke method intValue() on null object on line 126 (open)

Did you create the new driver by copying and pasting the entire code that I listed? I double checked the code and it is exactly what I am running.

It does seem to be a little more stable with all the new firmware shades active and the older firmware ones inactive. It sure would be nice to get them all on the same firmware to isolate if there are any other problems.

Apeciate your double checking. Haven't had time to look at the error yet. But I will check on my copy/paste skills in the next day or two.. Been busy adding zwave repeaters to try and help... which it doesnt. However using the generic driver, one of the blinds is consistantly misbehaving. Even with more repeaters. Oddly it misbehaves in rules, and when I hit "close" on the device page. If I hit "off" after that it does close right away. I've done this test 5 times. Wont respond to the rule, wont respond to a close, but off works right away. But then occasionally it will work from the rule. I have run a version report on that blind:Version Report - FirmwareVersion: 12.1, ProtocolVersion: 6.04, HardwareVersion: 255

Yeah, it would. See if you could call Zebra blinds (google it and site will come up) to see if they could help you.

For me this is resolved... with a caveat. Going thru some testing I did have the right code.
When changing to the Somfy driver I did have to change the travel time on most, which I did when changing the driver (before any testing) One I didn't have to change the default from 6sec as it was about right.... testing that one I got the null errors again. Went to the travel time, typed 6 and save preferences. No longer got the error. Can't replicate it by moving it back to another driver and then back again, it just works so I'm not sure, but that's the news from here. I'm guessing the code doesn't 'stuff' preferences till you hit save preferences resulting in the null?. So saving prefs. is a necessary step for any new blind using this driver.

@soundmanmike thanks for the suggestion, seems to be working for my 12.1 blinds nicely... (for now.... :pray:)

I should be getting to PM's in a bit. Didn't realize I wasn't getting notifications on here.

1 Like