Unreliable Philips Hue Dimmer Switch Events with current 2.5 Milestone M4 Build

Parallel to my “production” setup i got a docker container with the current 2.5 Milestone Build M4.

I found out that lights that i control with the Philips Hue Dimmer Switch via the Milestone Build i got unreliable events from the button.

Here is the events.log port of the M4 Build:

2019-11-01 13:47:00.658 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:04.833 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:07.944 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:18.320 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:24.549 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 1000.0
2019-11-01 13:47:42.181 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4000.0
2019-11-01 13:47:42.700 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4002.0
2019-11-01 13:48:34.549 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4000.0
2019-11-01 13:48:42.847 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4002.0
2019-11-01 13:48:49.577 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4000.0
2019-11-01 13:49:58.571 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4002.0
2019-11-01 13:53:16.717 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 1002.0
2019-11-01 13:53:25.545 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:Zigbee_Kueche_Fernbedienung:dimmer_switch_event triggered 4000.0

As you can see the Short Release events is triggered 10 seconds after the initial pressed events. sometimes i got a lot of 4000.0 events and NO 4002.0 event.

In my production setup based on the 2.4 stable version that same event from the same bridge looks like this:

2019-11-01 13:47:00.496 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1000.0
2019-11-01 13:47:01.225 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:04.707 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:07.827 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:15.110 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:18.254 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:24.483 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1000.0
2019-11-01 13:47:25.005 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:47:37.986 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:47:42.161 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4000.0
2019-11-01 13:47:42.722 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:48:12.883 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4000.0
2019-11-01 13:48:13.405 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:48:34.722 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:48:42.519 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4000.0
2019-11-01 13:48:43.043 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:48:49.817 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:49:58.554 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0
2019-11-01 13:53:16.897 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 1002.0
2019-11-01 13:53:25.755 [vent.ChannelTriggeredEvent] - hue:0820:00178827902c:kitchen:dimmer_switch_event triggered 4002.0

Basically i am missing a lot of *002.0 events or they got send much too late.

Should i open an issue on github for this?

The openhab.log file looks clean during this time period.

According to Jenkins, Milestone 5 does not yet exist.



Hi Bruce,

thanks for pointing that out. Thats my bad. Of course i am using the 2.5 Milestone M4 Build.

I will edit my first post.


1 Like


A lot of people having the same problem, including me. It was mentioned long ago. Since 2.5.0-M1. See also here:

1 Like

@cweitkamp Are there any news?

Are you sure that this is related to your issue. I understand that the event is not received by the rule. However i am missing events directly in the events.log.

I`m also missing triggered events in events.log (or better: events bus). A rule should catch an event and do something. If event is missing, rule is not fired.

Wow, ok. I wouldn’t expect that something big like this issue would exist for such a long time.

Ok Thank you very much. I will have a look at these github issues.


Here is a further hint for you.

I am on Snapshot 1731 and had the same problem. So wanted to exclude, that it’s an issue due to the new OH-CORE or rules DSL, so I kept all of 1731 but did a downgrade of Hue Binding to 1486 (this is 2 weeks before 2.5.0-M1 was released) and NOW it is running again very reliable.

Tghere were so man y mahor changes between M2 & M2 I would not expect any binding before M2 to work well with current snapshots. There have been too many architectural changes.


All I can tell to you:

ZWave and Hue are running without any problems so far (both from 1486), together with the 1731 OH-CORE (released about 7 hours after 2.5.0-M4).

In contrast, they are not running since 2.5.0-M1 or 2.5.0-M2.

So I’m satisfied now. :slight_smile:

If you do not have any of these problems, then congratulations to a lucky guy.

1 Like

At the moment i am running mainly Z-Wave devices but no Hue. I have recently done some testing with the ZigBee binding though.

AFAIK you have disabled “nightly heal”? This is usually not the default setting. This can be called a workaround, and so is mine by downgrading to something working.

I actually have it enabled right now but plan on disabling it when my network settles down physically. I have moved some devices around and actually rebuilt the network on a different controller.
For now, I have a controller & system I can use for testing & experimentation.

1 Like

I would like to try that version as well for the time being as I still have some dimmers connected to the Hue bridge (for redundancy reasons), but it looks like I cannot download anything before snapshot build 1730… Any place I can get my hands on this 1486 .jar file?


You can use this: org.eclipse.smarthome.binding.hue-0.11.0-SNAPSHOT.pdf (136.9 KB) Please rename ending to .jar and copy it to addons folder.

1 Like

Thanks! :grin:

1 Like


Unreliable Philips Hue Dimmer Switch Events with current 2.5 Milestone M4 Build

Could you please share any information about the state or if there are plans to fix this in near future? Thanks a lot.

@Celaeno1 I appreciate your eagerness to find a solution for this problem. But I am afraid I do not have the time to investigate much on it at the moment. In general I guess that we are facing two different problems here. First one is the Philips Hue Event issue. This is probably cause by the polling strategy implemented in the binding - it polls the Hue Bridge in a fixed time interval. For this issue I have to admit that I am not very motivated to do research as I get rid of sensor / remote control usages via Hue binding in my environment and thus I do not have the possibility to test it anymore. The second one is the - lets call it - “getEvent()” issue in DSL rules. I tried to investigate on that but did not find a solution for it yet.

1 Like

Thank you very much for your detailed explanations. If I can support or help you in any way, I am always ready for testing. Please contact me if you have some time left.