Hi,
I have the following (simple) setup at home:
When an AeonLabs motion sensor detects some movement in my corridor, it turns on a Hue Lux light bulb.
This works in 95% of the cases, but sometimes the light is turned on only very dim (brightness=1), even though it should be much brighter. The log files reveal the following:
2015-09-15 22:48:56.426 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:48:58.265 [INFO ] [runtime.busevents ] - Aeon_CO_Motion state updated to ON
2015-09-15 22:48:58.294 [INFO ] [.o.model.script.Lighting.rules] - Motion in corridor detected
2015-09-15 22:48:58.398 [DEBUG] [inding.hue.internal.HueBinding] - Hue binding received command '60' for item 'Light_CO_Main'
2015-09-15 22:48:58.424 [DEBUG] [.hue.internal.hardware.HueBulb] - Sent message: '{"bri":152,"on":true}' to http://<hueip>/api/xyz/lights/1/state
2015-09-15 22:48:58.426 [INFO ] [runtime.busevents ] - Light_CO_Main received command 60
2015-09-15 22:49:06.428 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:49:06.843 [INFO ] [runtime.busevents ] - Light_CO_Main state updated to ON
2015-09-15 22:49:06.850 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:49:06.864 [INFO ] [runtime.busevents ] - Light_CO_Main state updated to 60
2015-09-15 22:49:16.852 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:49:17.099 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:49:17.134 [INFO ] [runtime.busevents ] - Light_CO_Main state updated to OFF
2015-09-15 22:49:27.101 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:49:27.328 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:49:37.330 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:49:37.571 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:49:47.573 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:49:47.709 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:49:57.711 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:49:58.063 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:50:08.064 [DEBUG] [inding.hue.internal.HueBinding] - Start Hue data refresh
2015-09-15 22:50:08.375 [DEBUG] [inding.hue.internal.HueBinding] - Done Hue data refresh.
2015-09-15 22:50:08.414 [INFO ] [runtime.busevents ] - Light_CO_Main state updated to ON
2015-09-15 22:50:08.441 [INFO ] [runtime.busevents ] - Light_CO_Main state updated to 1
Looking and this log file and the actual behaviour, I would say: OpenHAB sends a brightness of 152. When the HUE bridge switches on the light, something goes wrong: The light is only turned on with brightness 1 and the bridge looses the connection to the light (this is why Light_CO_Main state is updated to OFF by the hue binding refresh service). I can also verify this when I try to access the status of the light via HTTP GET request: reachable=false. Several seconds later, the bridge reestablishes the connection to the bridge, and the hue binding refresh service detects that Light_CO_Main is at brightness=1.
Has anybody similar experience with the Hue Lux?
The binding seems to work perfectly fine. Also, the distance between the light bulb and the Hue Bridge is not really big. I even could understand if the light doesn’t turn on at all, but that it turns on with a brightness of 1 and then the bridge looses the connection? This almost looks like some kind of firmware bug to me.