My hub is locking up every night. If not every night it's every other night. This seems to start after installing a inovelli black switch and rgbw bulb. The only way I can get it working again is to power cycle the hub. Any ideas on what I can look for to find the problem.
pull the air gap on the inovelli switch and leave it powered off (unless you really need that light). See if that switch being powered off helps with the lock ups.
1 Like
Hi @natebradley
Welcome to Hubitat! And I'm sorry you're experiencing this.
Can I ask you this? Did you have any issues joining these two z-wave devices to the hub? Or any other z-wave devices added recently? Were there multiple attempts that seemingly didn't go through? Before the device(s) finally paired?
Alternatively, did you force remove any zwave devices when you added the two new devices?
I had a similar experience about 1.5 months ago, and Hubitat Support (tagging @bobbyD) traced the issue to my having accidentally "stranded" z-wave devices.
2 Likes
I would add:
You don't need polling, if you have that turned on, turn it off.
You don't want or need these securely paired, only Locks and Garage Doors. (Settings> Zwave Details> Secure Join)
1 Like
I don't remember having any problems during setup or force removing any devices. I check and it looks like it's set to locks and Garage door only. I did add a second inovelli black switch but removed it from the wall but I didn't remove from the hub. My wife wanted somewhere else and I haven't installed it in its new location yet. Could that cause the lock up?
Thanks
Yes, it is possible. Temporarily power that switch up and exclude it from the hub. Don't force remove it.
Possible... but one device being offline causing the entire hub to lockup? This is equivalent of the vacuum effect of someone unplugging a wall plug. Will it break routes and cause devices to not respond...yeah. But lock up the entire hub? That's really not acceptable if this turns out to be the culprit.
I'm suspecting the other switch might be spamming the hub causing lockups or the bulb as those are the newest devices before the problem started.
You really think a offline device could be causing a hub lockup?
1 Like
Between those two possibilities - I'd say the former is more likely for sure.
This one will be interesting to watch.... yeah that bored 
3 Likes
I will hook that switch up tomorrow. Is there anything in logs that would tell me why it's locking up?
What errors do you see in the logs now?
Update. I open a ticket with HE support. They couldn't find a reason why it was locking up. They suggested that I remove the inovelli bulb temporary. I removed the bulb and it never locked up for over a week. I ordered two more inovelli rgbw bulbs on their memorial day sale. They came in yesterday and I set them up today and the hub locks up in less an hour. I am using the inovelli driver. I switched to the aeotec zwave rgbw build in driver. It only been a few hours but it hasn't locked up yet. Has anyone had a problem with the inovelli rgbw bulbs locking the hub? Thanks
Which driver were you using with the iNovelli rgbw bulb?
I was using the one from inovelli
Inovelli Bulb Multi-Color LZW42
Last updated on 4/9/20
I would recommend trying @bcopeland’s driver:
I'm not aware of anything in their driver that would cause the hub to lock up.. The bulb can be a bit on the chatty side so if you are sending a bunch of color changes to it, the commands can get backed up if you don't have a really good z-wave mesh... In my driver, I have a low bandwidth mode that can help with the messages getting backed up, if that is your issue..
3 Likes
I changed the driver to the one @aaiyar recommend. It's been about 4 days and the hub locked up again tonight. Should I remove the inovelli bulbs again? Is there anything in the logs that I can look for that will show why it's locked? Thanks
My Hub locked up again today. What is my next option to figure this out. Thanks
Have you tried low bandwidth mode in @bcopeland's driver?
Curious, I have a inovelli RGBW bulb using the inovelli driver. I don't use much so I'm not a good example of function.
However I just tested it and noticed two things looking at the Events Log:
-
when I change the color, the resulting events are the color #, a color name then nine more color numbers each within 100 milliseconds of the previous.
-
When I set color temperature to 4000 then 4011 gets reported. When I set color temperature to 5000 then 5009 gets reported (in the events).
