Well, I’m afraid I’ve passed the Wife Tolerance Threshold, and the Inovelli switch is going to have to come out. Just ordered a GE that hopefully will not require me to pull the airgap once a week in order to use my lights. If it helps anyone with debugging, it seems like it tends to freeze more often right after I control the switch from the SmartThings app or via another wireless switch. I’d love to see this SmartThings incompatibility get fixed so I can use the Inovelli switches I own, but for now, they’ll stay on the shelf.
Been there many times with my smart home projects
My switch has locked up as well. I can pull the air gap and my load light turns off I push the gap back in and the load light comes on but the led indicator does not go through the normal boot up color cycle sequence. Not sure what to do at this point. Any suggestions on what to do.
I’ve had two of my Red Series switches freeze up in the past few weeks - pulling air gap seems to fix them. Would be nice to hear whether Inovelli has acknowledged the issue and is investigating a fix. @Eric_Inovelli
Update: For clarity, my issue isn’t related to SmartThings. I’m running on HomeAssistant, without secure inclusion.
I’m having this same issue with a brand new switch. Funny thing is when it hard freezes, it seems to mess up my mesh and many rules on Hubitat don’t work properly, The rules run, but it doesn’t seem to connect to the devices to run. One thing I found strange, I was pairing a new Red series Dimmer and it wouldn’t pair and would tell me that it was too far away. My hub was 4 feet from it. Once I figured out the other Black series was hard frozen and pulled the airgap to reset it, everything worked time and the dimmer paired normally. Very strange. I hope it something that can be fixed quickly.
I’ll post this again here. I’ve seen two other threads might might also be relevant so see my post for more info:
Edit: using Hubitat
@Eric_Inovelli Anyone ever get to bottom of this issue. I still have my Dimmer freeze about twice a week. I’m on Hubitat and the switch is controlling Inovelli bulbs/. Local control turned off. You can tell real quick when it freezes as the LED turns off. I found the easiest way to fix is do the 8 button push on the config button click the up button and the LED and light turns on, then 8 click the configure button to turn local control off again.
No we haven’t unfortunately, but are you by chance using a neutral or non-neutral setup?
Also, one of our former reps noticed that with the firmware update this seemed to go away. Would you mind trying to update the firmware via Hubitat and let me know if that fixes it?
Hey @Eric_Inovelli. I am using a neutral set up for a bedroom. The light has 2 inovelli RGBW bulbs. I never had an issue with them light with a GE dimmer.
I did update the firmware on Monday and still have the same issue. Let me know if there is anything else I can share or test for you to try and get this fixed.
I will say since the firmware update this has only happened once the day after. Nothing since. Before it would happen about every other day. I’ll keep testing it and let you know if it happens again.
Ok, please do – we can also look at swapping out the switch completely as I’d like to take a look at it and send it to the manufacturer for further analysis.
I have 4 Red series (LZW30) switches connected to a ST gen 2 hub and planned to add more switches but unlike GE and other switches of different brands connected to the ST system, only the IN switches freezes frequently,. Every week or so at least one of the switches freezes and can no longer be controlled. Nothing short of switching of the breaker helps to reset. I have original FW on the Switch, and have installed (no changes) the two original handleson on ST. Question ( since I an an old HW engineer). Does the switches have a HW watchdog? Anyhow, how can we best deal with the freezes?
Hey, @KuLe. Did you ever get an answer on this? I’m having a similar problem but with an ST v3 hub. Hoping someone has / can provide the answer.
I too am having these problems and have found that pulling the air gap fixes the problem every time. I have 30+ of the red series on/off switches and it only seems to happen to some of them. I have many that have never had this issue ever. I’m sure they are working to determine the problem, but it’s going to be hard because as far as I can tell nobody has been able to actually isolate a specific thing that is causing this to happen. If they are unable to create the problem on a testbench it is going to be extremely difficult to fix fast. I read that some people are experiencing it almost daily. I had it happen fairly often (once a week) at first. Now it really rarely ever happens. I did run the zwave utility in smartthings when I was having this issue. I have no idea if that actually did anything, but it gave me the impression of helping lol. One big thing I have noticed is that the issue tends to happen with my switches that are on the edges of my house. I’m wondering if it has to do with # of hop points along the mesh network. Something like the switch is trying to communicate but not receiving responses, which eventually causes it to lock-up. 100% conjecture just thinking.
@Eric_Inovelli
Would it be helpful to make a doc where information can be compiled about this issue. Something where if people are comfortable doing so can mark down instances of the issue with information like switch series/device handler version/time of last 3 commands/what those commands were/etc. Obviously if people aren’t comfortable sharing the information they don’t need to, but maybe it would help.
Yeah – this would be helpful for sure. Let me set something up that maybe we can collaborate directly with the manufacturer to streamline this. We’ve been running stress tests on switches sent back to us as well as the manufacturer and we can’t seem to replicate this issue.
If anyone is open to it, we can send what’s called a Zniffer that will monitor your Z-Wave network (commands sent to/from the hub) and we can try to capture any data to see if it’s a Z-Wave thing.
We were able to replicate this on our Fan/Light switch and it was determined to be the SDK – when we switched to a different SDK, the freezing went away. The difference with the fan/light switch is that it’s 700 Series (whereas the On/Off & Dimmers are 500 Series) so the SDK fix will not apply.
I’m going to update this thread shortly to seek any volunteers as well as setup a possibly a Microsoft Teams thread where we can all chat directly to try to figure this out.
I have about 5 LZW31-SN dimmers, and this has happened once so far. On the one that froze, it controls ~5 LEDs.
It had been working the previous day, turned the lights off at night, and in the morning it did not come on. I had to airgap it.
I don’t remember if the LEDs were dimmed at night, when power use can drop tp about 10W.
According to Vera the version is
3,6,4,1,43
Adding my LZW30, purchased in January, to the list of frozen switches. Mine is connected with Smartthings V2 hub. Use automation with humidity sensor to turn on bathroom fan. Has been working flawlessly manually (with 45 min turn-off timer set for the device in smartthings) and automatically with the humidity sensor. Last week, froze up in “on” mode, and only reset via cutting power. When frozen, no communications with smartthings, buttons didn’t work.
Thanks for the posters who mentioned the air gap switch. Glad Inovelli added it–easier than the breaker method I used!
Are we expecting any fix? For me, my Red series switches in the house work fine. Only this one, once, so far.
My LZW30-SN (purchased thru Amazon in Jan) has locked up and been unresponsive occasionally and an air gap fixes it. My issue now is the LED is frozen. No matter what I do I can only get an LED upon initial setting, air gap and reset, after that the LED freezes and doesn’t respond. See post below for info
LZW30 -SN No LED Control
Complete newbie but I have a locally unresponsive dimmer with smart things hub. I’ve read the thread and it seems like this is a communication security issue - since I get the following diagnostic in IDE:
- networkSecurityLevel: ZWAVE_S2_FAILED
So dear wise ones … is there a workaround? I’ve disabled security in my smart things app but no dice. Do I have to remove the switch then re-add with security disabled? Or what? Any suggestions appreciated.
Hmmm. There is trickery afoot. After I posted, and after more alcohol, I explicitly set some parameters rather than relying on defaults (for example setting disable local and disable remote to zero, and installing the device handler from GitHub rather than using the default.
This enabled the switch but disabled control via Z-Wave grrr. Went to bed, got up, and all is working perfectly. WTF? Let’s see what happens next.