I am struggeling with my Hue Binding since I updated to 2.5.6. It was working flawlessly for a long time but since a few days I encounter a really stange behaviour.
Every few hours (around 6-10 hours) my hue binding gets into a non-responsive state.
That means it is running normally after a fresh start of the openHAB service but later on the binding does not accept anymore commands. When pushing my light buttons (homematic) I see the button events correctly in the log viewer. But the rule commands for setting the lights ON and OFF are not issued against my hue bridge anymore.
When I stop (or restart) the openHAB service all former commands that weren’t issued correctly get then fired (during the service shutdown process) to the bridge so that the lights are getting the ON, OFF, ON, OFF etc. commands in a row. After the restart everything is running smooth again for the next couple of hours. It feels like the commands were queued but not processed before.
My openHAB is running on a PI 4 using - belong a few other bindings - the hue binding with two bridges. One is the original Phillips bridge and I run a DiyHue emulation bridge as well.
I already tried the following things without success:
- There are no errors regarding showing in the logs regarding this issue, neither on INFO nor on DEGUG level
- Reinstalling the binding
- Clean cache
- Deleting the DiyHue bridge to have only the original hardware bridge running
- The bundle shows up as ACTIVE - even in the non-responsive state
Right now the system needs at least two service restarts every day
Did someone encounter this issue, too? Any help would be highly appreciated.