strange issues with zigbee2mqtt Topic is solved

[Eugene]

Hi Guys,

I had everything working well for some time but I just got very weird issues between domoticz and zigbee2mqtt. It appears some messages are always lost between Zigtbee2MQTT and Domoticz but some are always delivered. Sadly, i can't find out where is it happening and where/why those are lost.

For example i have 3 Loginovo ZG-101ZL buttons which behave exactly in the same way - single press or long press (on/hold) events are never delivered to domoticz and not seen in logs but triple press (Operation Mode) events are always delivered and seen in the domoticz logs. While connecting with MQTT explorer to Mosquitto broker i see all messgages landing into MQTT as they should.

Also i got a problem other way around - i can always switch off ZM-105B-M dimmer from domoticz (OFF message lands into MQTT explorer & reflected/actioned in zigbee2mqtt) but ON message seems never leaving domoticz (not seen in MQTT explorer even).

any thoughts on what got wrong with my config are appreciated.

Domoticz version 2024.4
Zigbee2mqtt version 2.2.0

[heggink]

Are you just observing behaviour or did you check the actual messages with mqtt Explorer?

[Eugene]

Are you just observing behaviour or did you check the actual messages with mqtt Explorer?

i had a look into actual messages in MQTT explorer. Here is for example i noticed same issue with TuyaKnob - some events are seen in domoticz and some are not. Rotated and clicked the Knob - MQTT explorer shows action:toggle for click but this click event is not seen in domoticz log.

At the same time other messages before button click have reached domoticz

Thanks

domoticz-log.png (72.79 KiB) Viewed 167 times

mqtt-tuya.png (148.96 KiB) Viewed 167 times

[Eugene]

btw, here is the Loginovo button related devices in domoticz, if you look into "last seen" on the right you can see that only one device (Operation mode) event is reaching domoticz. Actions (single/on/off) are not seen by domoticz despite i see those in MQTT explorer

thanks

loginovo.jpg (392.74 KiB) Viewed 165 times

[Eugene]

loginovo.jpg

I deleted the button from the above screenshot from zigbee2mqtt, cleaned its messages in MQTT explorer, deleted devices from domoticz and paired the button again.

the only discovered device is operation_mode, the _action_ are not discovered, it seems not reaching domoticz at all despite i can see those in MQTT explorer.

2025-06-04 14:18:41.301 Status: mqtt: discovered: 0xa4c13889957501f6/0xa4c13889957501f6 (unique_id: 0xa4c13889957501f6_battery_zigbee2mqtt)
2025-06-04 14:48:11.603 Status: mqtt: discovered: 0xa4c13889957501f6/0xa4c13889957501f6 (unique_id: 0xa4c13889957501f6_battery_zigbee2mqtt)
2025-06-04 14:48:11.704 Status: mqtt: discovered: 0xa4c13889957501f6 (Operation mode)/0xa4c13889957501f6 (Operation mode) (unique_id: 0xa4c13889957501f6_operation_mode_zigbee2mqtt)
2025-06-04 14:48:13.211 mqtt: Light/Switch/Switch (0xa4c13889957501f6 (Operation mode))

[gizmocuz]

Could you create a github issue and follow the below guide/steps:

https://wiki.domoticz.com/MQTT_AD_Report_Problems

We need the config topics/payload of the switches as well as complete state topics/payload to replicate the issue

[Eugene]

Could you create a github issue and follow the below guide/steps:

https://wiki.domoticz.com/MQTT_AD_Report_Problems

We need the config topics/payload of the switches as well as complete state topics/payload to replicate the issue

Thank you, gizmocuz! I created an issue on github, i hope i collected all the data expected from me.

https://github.com/domoticz/domoticz/issues/6349

[Eugene]

Gizmocuz, thanks for advice on GitHub, the upgrade solved the issue!
Is there a bug details for the issue i was facing? I wonder what was wrong.
Btw, i see now the device names changing comparing to what they were named before but i can live with that.