Some Hue 210 bulbs are discolored

Add-ons Bindings
, ,
1

Hey guys,

Summary:
I believe I am having issues with the different “modes” on the Hue 0210 bulbs. Some of the bulbs are discolored after being turned off/on (not the actual power, just via hue) - the OH2 binding misreports their color, or at least that color (HSBType) doesn’t make it to the actual bulbs.

Details:
I have set up OpenHAB2 and am using a simple rule that runs every 10 seconds and updates, for example, 3 bulbs above my fireplace.

For some of the bulbs (right now, 1 out of 3 bulbs above my fireplace), the bulb color does not reflect the OH2 state. All 3 bulbs’ color items show the same state in PaperUI + my jython script, which is the HSB value I set to them. However, the bulbs themselves look different:

20190621_084545
20190621_084545.jpg2015×1511 531 KB

Notice the bulb on the right is significantly more yellow.

Yet when I log the state of these 3 bulbs’ Color items, I get:

2019-06-21 09:09:20.073 [INFO ] [clipse.smarthome.automation.examples] - Fireplace 1: 26,10,100
2019-06-21 09:09:20.076 [INFO ] [clipse.smarthome.automation.examples] - Fireplace 2: 26,10,100
2019-06-21 09:09:20.080 [INFO ] [clipse.smarthome.automation.examples] - Fireplace 3: 26,10,100

Indeed the PaperUI is of the same opinion. It shows all 3 color (and temperature) items for those bulbs as identical. (I can’t attach more than 1 image)

Some notes:

  • The hue app controls all these lights just fine. I can set them all to the same color using the color picker. When the OH2 script runs after turning on the lights and sets them all to their 2 different colors (as pictured), the Hue sees the colors as actually different (unlike OH2) and shows them as such.

  • I have read these bulbs can be in either color or temperature “modes”, and although I believe this should be handled by the OH2 binding, it seems I can very-temporarily fix by picking a color on the bulbs, and then my script’s HSBType will be honored.

  • Which bulbs are stuck like this - very white, or slightly warmer - seems to change if I turn the lights off & on again, though not consistently. In fact, while I was writing this post, it changed to the middle bulb. :frowning:

Question
Is there some way I should be setting the “mode” on these bulbs, either in a permanent way, or on startup of the bulbs? I am not aware of anything in OH2 to do this, if my commands to the Color item is ignored… but I am a beginner.

Thanks for any help!

2

I’m not 100% positive as I don’t use Hue, but I’ve seen mention of a color temperature channel on Hue bulbs. Do you see a color temperature Channel on the Thing? If so you might compare those channels across the three bulbs (you probably need to link them to Items) and see if they are the same.

3

Thanks, yeah I have seen that as well- unfortunately, the ColorTemperature state for all 3 bulbs is consistent (“NULL”), just like the Color state is the same… despite one of them being more yellow. Just re-tested this now :frowning:

Also, since I can upload a pic, this was the PaperUI for those 3 bulbs at the time I took the picture…

Capture
Capture.PNG1702×840 64.9 KB

Either way, I think the UI (and item state in jython) should reflect the physical bulbs, barring some connectivity problem (which I haven’t seen anything of in the logs?)… so this seems wrong to me

4

I see the same issue with a hue LCT015 bulb.

I figured out how to reproduce it and how to fix it, but unfortunately no solution or workaround for fixing it in openhab.

The issue can be triggered by setting the color temperature channel. E.g. via paper UI or rule. When done in a rule, you need to wait a bit before setting a color for the same light. If it is done immediately (in the next line of code), the issue might not trigger.

An example.

  1. I tell Alexa to turn on the light
2019-07-10 18:40:08.665 [ome.event.ItemCommandEvent] - Item 'DeckenlichtSchlafzimmer_Color' received command ON
2019-07-10 18:40:08.676 [nt.ItemStatePredictedEvent] - DeckenlichtSchlafzimmer_Color predicted to become ON
2019-07-10 18:40:08.679 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 29,63,0 to 29,63,100
  1. A rule I have kicks in that switches the light to the color 30,64,100 (warm white), whenever the light is turned on. Not relevant for the issue - it happens with or without this rule.
2019-07-10 18:40:08.680 [ome.event.ItemCommandEvent] - Item 'DeckenlichtSchlafzimmer_Color' received command 30,64,100
2019-07-10 18:40:08.684 [nt.ItemStatePredictedEvent] - DeckenlichtSchlafzimmer_Color predicted to become 30,64,100
2019-07-10 18:40:08.687 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 29,63,100 to 30,64,100
  1. The hue bulb decides to change it´s color on it´s own. This is something that happens often but not always: The hue reduces H and S by 1. But I think I saw it once adding 7 to H as well, when I set the light to blue, so the reduction by 1 is maybe only the most common case with the light colors I use.
2019-07-10 18:40:16.894 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 30,64,100 to 29,63,100

  1. Anyway, the light is on with a warm white, now.

  2. Let´s trigger the problem by setting the color temperature to 51 using Paper UI

2019-07-10 18:40:42.118 [ome.event.ItemCommandEvent] - Item 'DeckenlichtSchlafzimmer_ColorTemperature' received command 51
2019-07-10 18:40:42.124 [nt.ItemStatePredictedEvent] - DeckenlichtSchlafzimmer_ColorTemperature predicted to become 51
2019-07-10 18:40:42.126 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_ColorTemperature changed from NULL to 51
2019-07-10 18:40:46.953 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 29,63,100 to 48,41,100
  1. Now I tell Alexa to turn off the light.
2019-07-10 18:40:53.144 [ome.event.ItemCommandEvent] - Item 'DeckenlichtSchlafzimmer_Color' received command OFF
2019-07-10 18:40:53.151 [nt.ItemStatePredictedEvent] - DeckenlichtSchlafzimmer_Color predicted to become OFF
2019-07-10 18:40:53.154 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 48,41,100 to 48,41,0
  1. I tell Alexa to turn the light on again.
2019-07-10 18:41:04.392 [ome.event.ItemCommandEvent] - Item 'DeckenlichtSchlafzimmer_Color' received command ON
2019-07-10 18:41:04.409 [nt.ItemStatePredictedEvent] - DeckenlichtSchlafzimmer_Color predicted to become ON
2019-07-10 18:41:04.411 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 48,41,0 to 48,41,100
  1. Again, my rule kicks in to set the color to 30,64,100
2019-07-10 18:41:04.411 [ome.event.ItemCommandEvent] - Item 'DeckenlichtSchlafzimmer_Color' received command 30,64,100
2019-07-10 18:41:04.417 [nt.ItemStatePredictedEvent] - DeckenlichtSchlafzimmer_Color predicted to become 30,64,100
2019-07-10 18:41:04.421 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_Color changed from 48,41,100 to 30,64,100
2019-07-10 18:41:06.984 [vent.ItemStateChangedEvent] - DeckenlichtSchlafzimmer_ColorTemperature changed from 51 to NULL
  1. The light is on again, but instead of a warm white, it is pink.
  • In both cases, openhab says, it set the light to 30,64,100.
  • The Hue app (on iOS) shows it clearly as a different color, matching the actual color of the light.
    So the hue bridge definitely knows what color we actually have
  • A side note: It seems the hue bulb (or the bridge) sets the color temperature channel to NULL, whenever you set a color directly. So the issue does not seem to be that the color temperature channel has a value that interferes.

The only fix I found so far is to use the Hue app (on iOS).
If I set a color using the Hue app (any color is fine), the problem goes away and openhab can set the proper color again.

Things I tried:

  • Just to be sure the color temperature channel is not involved, I also set the color temperature value in my rule every time before I set the color. I tried 0 and 100. But all it did, was to cause the problem to appear, never to fix it.
  • I restarted openhab while the problem appeared. No effect. The problem remained.
  • I checked if other colors are off as well, not only 30,64,100. And yes, they are.

So far I ran out of ideas, except for implementing a dirty workaround, which is to force the problem and to adjust my color values to correct for the error.

1 Like
5

I have this exact issue for a couple of months and I am just now getting around trying to diagnose it. It started with one bulb, but now I have four that do it periodically. Would love to help figure this problem out but not sure where to start!

Bulbs are sent 30,64,100 but they have a pink tint. The color temperature items (which I never use) show null.