ZEN30 no longer turns light on after firmware upgrade to 4.50

After upgrading my ZEN30 Double Switch to firmware version 4.50, the light controlled by the dimmer no longer turns on. Z-Wave On/Off/Dim commands and physically pushing the switch paddle both make the LEDs change, but the light itself never turns on. The fan controlled by the relay is working fine, both via Z-Wave and manually.

I tried downgrading the firmware back to 4.40, with no luck. I also tried resetting the configuration, but that did not help either.

(I did check that the bulbs in the fixture are not dead. :smiley: )

How can I get my lights working again?

I’m having the same issue with one of my ZEN30. The other one works perfectly fine.

I assume you were originally on 4.40? Meaning you were on a revision 4 hardware?

For what it’s worth I did my first 4.50 firmware update just a moment ago, and my Zen30 is fully functional.

1 Like

I was previously on 4.40, but I think it originally came with 4.10, and I’ve already upgraded at least once or twice before.

So the switch shows it is a ZEN30 4.0 800LR hardware version on the front metal plate right above the top paddle? I see there have been four different hardware versions over the life of the product, so just double-checking. If you were originally on 4.40 that should be the case…

My ZEN30 switches (the one that is having this problem and another that is still in the box that I have not installed yet) do not have a hardware version on the metal plate above the paddle. However, they do say “Firmware version 4.10” on the back, which fits with my recollection above.

1 Like

It almost seems like Parameter 19 somehow got set to 2?

Can/Did you verify the setting of Parameter 19? Maybe try re-sending that parameter as 1 to see if that resolves the issue?

Just a stab in the dark…

OR - if Parameter 15 (max brightness) somehow got set very low (like to 2 or 3, etc) it would also look like this behavior.

Which hub are you on?

My wife said “have you tried turning the circuit breaker off and on again?”

… of course, that appears to have helped.

But I’m still on 4.40 that I had downgraded to, so I’m going to try the upgrade again in a day or two.


Both of these looked like they were set to the proper values, but I did not try toggling them to something else and then back again.

If I have this problem a second time after trying the upgrade again, I will try that.

Home Assistant (on Raspberry Pi 5 with the Aeotec Z-Stick 7 Plus).

2 Likes

I upgraded to 4.50 again, and had no trouble with it this time.

It’s been a few years since I’ve worked on embedded system development, but I’d have to guess there was some kind of internal state corruption that was resolved by turning off the power.

1 Like