#Zigbee2MQTT Issue After Update

1 messages · Page 1 of 1 (latest)

wispy iron
#

Hello everyone,

I'm experiencing a strange behavior with my Zigbee setup since updating Zigbee2MQTT (Z2M) and the Sonoff dongle firmware.

Increased Latency: I've noticed a slight but noticeable delay when using physical buttons.

Major Issue - Light State Lock: This is the most annoying problem:

If I quickly turn a light ON and then OFF from Home Assistant (HA), the light remains physically ON.

In both HA and the Z2M interface, the light state is reported as OFF.

To truly turn it off, I have to go into the Z2M interface, set the brightness to 0%, then 100%, and finally, I can switch it OFF.

This bug never happened before the recent updates. It's incredibly disruptive.

Has anyone encountered a similar issue or have any leads on what might be causing this? Any help would be greatly appreciated!

Thank you!

azure wagon
#

can you give us some details on the hardware, HA version and Z2M version?

wispy iron
#

Yes, for sure.
I’m using Home Assistant OS on a Raspberry Pi with the following versions:
Core: 2025.11.1
Supervisor: 2025.12.3
Operating System: 15.2

For Zigbee2MQTT, I’m running version 2.6.3.

All of my lights are Tuya devices connected via Zigbee. The issue only affects the lights, other devices such as TRVs, door sensors, and 5.8 GHz sensors don’t seem to be problematic.

modest ruin
#

would start with updating your system 😉

#

and after that z2m will update too

#

and make sure you are using an extension cable for zigbee dongle, the pi is known for interference. (wifi/usb3.0/ssd)

wispy iron
modest ruin
#

i think the updates are the solution here.

#

reboot haos afterwards

#

for future buys i would not recommend Tuya btw.. 😉 No one will i guess lol

#

BTW, do a backup first 😉

wispy iron
#

So I’ve updated everything (Core, OS, Z2M, MQTT server). I also added a USB extension cable, but I still have the issue.
When I quickly turn a light on and off, it gets stuck in a state (either ON or OFF) and I can no longer control it.
I have to go into the Zigbee2MQTT interface and set the brightness to 100%, then to 0%, to recover the state and be able to control it again from Home Assistant.

modest ruin
#

ok, check z2m config/automations for lights and disable transition time, many tuyaaah lights not happy with it. If this also does not help, post debug logs please

#

can also be power related. if you have a powered usb hub, use that for dongle

#

connect to 2.0

wispy iron
#

So I checked everything you mentioned, and I don’t have any automations on my lights except the ones linked to the buttons to turn them on/off. Just in case, I disabled those as well.

The Zigbee dongle is connected to a USB 2.0 port on the Raspberry Pi, the same port I’ve been using for over a year. I don’t have a powered USB hub available, but I really doubt this is a power issue. As I said, this Home Assistant setup has been running without any problems since November 2024. Before that, I was using the same Zigbee dongle on a Proxmox server and I never had this issue either.

After thinking about it a bit more, I remembered that a few months ago I did a large batch of updates (I’m not very disciplined with updates). I updated Home Assistant, Zigbee2MQTT, all the add-ons, and also the firmware of the Zigbee dongle. Maybe that’s related?

I’m attaching the Zigbee2MQTT logs in case that helps.
Thanks a lot.

📎 45df7312_zigbee2mqtt_2025-12-16T11-46-32.232Z.log
#

At this point, I’m honestly hesitating to wipe everything and do a clean reinstall from scratch.