Page 1 of 1

Widget state change delay

Posted: Tuesday 19 August 2025 9:49
by Dave21w
I have this issue randomly, I'm running the latests beta but it's happened many times before. System is Rpi3b+ with latest 64bit os, Z2M and mqtt.
Clicking the widget for turning on (for example) the fan causes the fan to come on straight away, so message from domoticz to mqtt to z2m is working pretty much instantly but the widget does not change state, the time it takes to reflect the current device state seems to change, for instance while typing this I timed it and it took 1 min 10 sec for the widget to update. Refreshing the browser or even opening the Domoticz UI on another PC still shows the widget to be showing the incorrect state. This only seems to relate to zigbee devices, I have never seen the issue with anything running Tasmota. If you have switched something on and the widget is stuck in off you then cannot switch it off becuse every press of the widget says switching on.

Any ideas clever people as it's driving me nuts :twisted:

Re: Widget state change delay

Posted: Tuesday 02 September 2025 20:17
by waltervl
I think this could be related to feedback from Zigbee2MQTT?
So when you switch the fan on, the command is sent to Z2M but it takes some time for Z2M to send the confirmation back to Domoticz?
I am not sure about how Z2M handles feedback though as I do not use Z2M.

Re: Widget state change delay

Posted: Wednesday 03 September 2025 9:52
by jvdz
I would start with monitoring the mqtt messages going between domoticz and zigbee2mqtt to see if the reply from z2m takes this long.

Re: Widget state change delay

Posted: Friday 05 September 2025 17:46
by FlyingDomotic
For me, for 140+ ZigBee devices, it immediate ...

You may have a look to Z2M logs to see if something is wrong.