I have three brand new LZW42 bulbs, connected to Home Assistant and paired to an USB Z-Wave controller via Z-Wave JS. They came already on firmware 2.31 that as far as I can see is still in beta, but whatever - they are working perfectly. However it seems like they do not remember the last state after a power outage.
I have verified in Home Assistant that the setting “State after Power Loss (2)” is set to “(0) Previous state” for all three devices, but after cutting back and restoring power, they turn back on. Also, after they turn on, HA still sees them as off, so I have no way except visual confirmation to know that they are actually on.
Am I missing something? I thought this was the major feature differentiating those bulbs from the cheaper ones. Maybe it’s an error within HA?
I just saw the same behavior on my three LZW42s running firmware 2.31. We had a power flicker overnight and I awoke to find the lights on even though they were off before and they’re set to resume the previous state. HA did see mine come on, though.
Maybe I’ll try downgrading the firmware next week to see what happens.
<Description>Remembers Last State</Description>
<Description>Bulb turns ON after power outage</Description>
<Description>Bulb turns OFF after power outage</Description>
I’m going to make these fixes and submit a pull request to zwavejs. @EricM_Inovelli , is this a firmware generation thing, or does 0 == “On” and 1 == “Previous State” for all firmware versions? Also, is there a setting for “Off”?
Sorry for the delay, I too can confirm that the “1” value persists the last power state. Thanks for the help!
@krisk, the pull request should be enough as far as HA/Z-Wave JS are concerned, but I still think that the proper future-proof fix should be applied to the main Z-Wave device database. Maybe that’s something @EricM_Inovelli can do?
This was a mistake by the manufacturer during their part in the certification process and we were never able to get it fixed in the device DB. I believe that we had it fixed in all of our drivers / device handlers / documentation / etc. for some time. I can see if I can hear back from some one over at the alliance about it.