[Zigbee] Command latency "burst" after extended runtime; resolved by toggling Thing status #921
Description
Description:
Running openHAB 5.1 in a Docker environment, I am experiencing a significant communication delay with Zigbee devices (primarily Philips Hue bulbs) after the system has been running for some time.
The symptoms are as follows:
- A command sent to a bulb results in no immediate action.
- Repeatedly sending commands (e.g., toggling a switch) results in no reaction for approximately 2–3 minutes.
- After this delay, all queued commands execute simultaneously within one second (the "burst" effect).
ScreenRecording_01-05-2026.18-54-38_1.mp4
Key Discovery:
If the Thing is manually Disabled and then Enabled again in the openHAB UI, the bulb reacts immediately to commands. This "reset" of the Thing temporarily fixes the latency issue without requiring a restart of the binding or the Docker container.
Initial Assumptions:
I previously suspected hardware incompatibility with Philips Hue bulbs. However, since the hardware responds immediately after a Thing-level reset, it appears the issue is related to the Thing Handler or the management of the command queue within the binding software.
Environment:
- openHAB Version: 5.1 (Official Docker Image)
- Binding: Zigbee Binding
- Coordinator: EFR32MG21
- End Devices: Philips Hue Bulbs