zwave-js / zwave-js-ui

Full featured Z-Wave Control Panel UI and MQTT gateway. Built using Nodejs, and Vue/Vuetify
https://zwave-js.github.io/zwave-js-ui
MIT License
944 stars 203 forks source link

Some messages not updating MQTT values. #3227

Closed cinadr closed 1 year ago

cinadr commented 1 year ago

Checklist

Deploy method

Docker

Z-Wave JS UI version

8.22.3.8607bd8

ZwaveJS version

11.9.2

Describe the bug

Some of my topics on MQTT server are not updating. My motion sensor (48/0/Motion) and my Danalock V3 98/0/targetMode and 98/0/currentMode are refreshing as expected but my DoorSensor sensor status 48/0/Any is always true. Also my Danalock 98/0/boltStatus is sticking to "locked" just as latchStatus and doorStatus not changing. The log shows a DEBUG message that these MQTT messages are sent but along this there is no update in MQTT topics (openhab not receiving values and MQTT explorer shows no update and the History list missing these updates).

To Reproduce

I've tried to stop/start my stack of mqtt zwavejs2mqtt containers but keeps the same.

Expected behavior

All values should update as before. This is apearing with the latest update (docker HUB says 3 hours ago).

Additional context

No response

Logs

zwave-js-ui-store.zip

robertsLando commented 1 year ago

@cinadr is storage enabled on MQTT settings? If so could you try by disabling it?

cinadr commented 1 year ago

I've tried to disable storage but still no luck. currentMode/targetMode of the lock is refreshing and the lock can be controlled via MQTT but the MQTT values of bolt/lock/latchStatuses are not updated despite the logs.

Screencapture image

This might be outside of ZWAVEJS2MQTT but I cannot figure it out. All of my apps working as expected (openhab, zigbee2mqtt, etc.) I've restarted all of them. The issue arrived with the yesterday zwavejs docker update.

JGtHb commented 1 year ago

Are you using Mosquitto as your MQTT broker using the latest eclipse-mosquitto Docker image? I had the same symptoms with a different door sensor and eventually narrowed it down to the new 2.0.16 Mosquitto release. Rolling back to version 2.0.15 resolved the issue for me.

cinadr commented 1 year ago

Are you using Mosquitto as your MQTT broker using the latest eclipse-mosquitto Docker image? I had the same symptoms with a different door sensor and eventually narrowed it down to the new 2.0.16 Mosquitto release. Rolling back to version 2.0.15 resolved the issue for me.

Yes. That solved my issue. Thank you for your help.

Might be related to this: https://github.com/eclipse/mosquitto/issues/2876

robertsLando commented 1 year ago

Thanks @JGtHb for the help