Hello,
i recently started playing with ZWaveJS and noticed that my dimmers are very slow to report the correct state to the UI when turning on the light. I switched my ZWaveJS to use MQTT instead of web sockets and the issue goes away.
The logs show a 5 second delay when using web sockets, and the value is reported as 255 not 99.
When using MQTT the state is reflected instantly and the value is set to 99.
I did not find those differences discussed in the forums yet, and was wondering why web sockets is using 255 instead of 99. Could that cause the delay?
Web Sockets:
2022-04-15 20:53:33.504 INFO ZWAVE: Node 8: value updated: 38-0-targetValue 0 => 255
2022-04-15 20:53:38.660 INFO ZWAVE: Node 8: value updated: 38-0-targetValue 255 => 99
2022-04-15 20:53:38.665 INFO ZWAVE: Node 8: value updated: 38-0-duration 0s => 0s
2022-04-15 20:53:38.668 INFO ZWAVE: Node 8: value updated: 38-0-currentValue 0 => 99
MQTT:
2022-04-15 20:57:34.176 INFO MQTT: Message received on zwave/Office_Main_Light/38/0/targetValue/set: '99'
2022-04-15 20:57:34.178 INFO ZWAVE: Writing 99 to 8-38-0-targetValue
2022-04-15 20:57:34.368 INFO ZWAVE: Node 8: value updated: 38-0-currentValue 0 => 99
2022-04-15 20:57:34.373 INFO ZWAVE: Node 8: value updated: 38-0-targetValue 0 => 99
1 post - 1 participant