ZwaveJS UI central scene sensors not reverting to unknown after button press

[auto.neub]

I use Z-waveJS UI with MQTT. Recently a handful of my zwave buttons and switches are having a weird issue.
For example: My zooz 5 button scene controller hard wired switch shows up in MQTT as a switch for the relay and 5 sensors (one for each button). When pressing a button once, the corresponding sensor should show ’0’ as the state and then after a second go back to ‘unknown.’ That way when you press it again, it will change state to 0 again and trigger the automation.

What started happening recently is that it just stays at the ‘0’ state indefinitely. So if i press it again, there is no state change and the automation doesn’t fire.

When i go to the node in zwavejs ui, the central scene shows the ‘KeyPessed’ event and reverts to ‘unknown’ as it should.

Anyone know why this isn’t happening over MQTT properly?

Thanks in advance for any help.

[freshcoast (Z-Wave AI Bot)]

Z-Wave JS UI + Zooz ZEN34 - retained sensor values

I have an issue after some recent Z-Wave JS UI updates or Home Assistant updates. Here is how it worked before: ZEN34 button has 2 sensors, for the lower and for the upper paddle. Upon pressing any of them, the sensor value briefly changes to a number, from 0 to 5 (0 = single press, 1 = button held, 2 = button released, 3 = double press, 4 = triple, etc). Between the presses the sensor was back in the Unknown state (or N/A, I don’t remember, but the fact is it wasn’t within the 0…5 digit range)…

[auto.neub]

Thanks @freshcoast
I’ll have to look into this. I’m not sure if I have a ZUI backup that old to revert to.
I’m currently in the middle of migrating z-wave sticks as well so I have two networks going. Ugh. Once the migration is complete, I think I’ll disable the MQTT part and use the Z-Wave JS addon. Based on that post, that may do the trick…

[auto.neub]

So I was able to migrate the rest of my zwave devices today to the ZUI addon. Once I got it off the MQTT gateway and into the zwave integration, this issue has been solved. Thanks again.