Hi, when will the fix be available in openhab?
Thanks
I think it should already be in the Milestones of 2.5. But I can’t tell for sure since I’m on 2.4 stable…
Hi @Coder89,
Welcome to the community. The fix should be available in snapshot builds and the latest milestone build (OH2.5.M3).
ok, thank you
Hi,
I just installed openhab 2.5.0 stable and hue binding 2.5.0. However, I’m still seeing the issue described in this thread. When reading the color of a bulb (it’s a hue go) and then immediately setting the same exact value, the color is washed out:
var colorString = Simon_TV_Color.state.toString
Simon_TV_Color.sendCommand(colorString)
Shouldn’t that be fixed in the current build? Am I mising something? I’m happy to provide more info/ color readings if needed. Thanks in advance!
Regards,
Simon
Yes, please provide your findings. Thanks.
1 Like
Well, I just did some testing, but was not able to pinpoint the issue. However, I collected some test cases that may be helpful to you. If not please let me know.
What I did:
- Set the color via hue app
- Read the state via REST- API out of the bridge
- Read the HSB value with openhab
- Write the same value to the bulb via openhab
- Read the state via REST- API out of the bridge
- Read the HSB value with openhab
Here are some test cases:
Case 1:
BEFORE setting via openhab:
"state": {
"on": true,
"bri": 144,
"hue": 31773,
"sat": 223,
"effect": "none",
"xy": [
0.1923,
0.5271
],
"ct": 153,
"alert": "select",
"colormode": "xy",
"mode": "homeautomation",
"reachable": true
}
152,100,57
AFTER setting via openhab:
"state": {
"on": true,
"bri": 144,
"hue": 28884,
"sat": 131,
"effect": "none",
"xy": [
0.2706,
0.4921
],
"ct": 153,
"alert": "select",
"colormode": "xy",
"mode": "homeautomation",
"reachable": true
}
150,96,57
The difference between the two colors is huge in this case
Case 2:
BEFORE setting via openhab:
"state": {
"on": true,
"bri": 132,
"hue": 14154,
"sat": 27,
"effect": "none",
"xy": [
0.3687,
0.3816
],
"ct": 250,
"alert": "select",
"colormode": "xy",
"mode": "homeautomation",
"reachable": true
}
37,30,52
AFTER setting via openhab:
"state": {
"on": true,
"bri": 132,
"hue": 34359,
"sat": 15,
"effect": "none",
"xy": [
0.3676,
0.3802
],
"ct": 230,
"alert": "select",
"colormode": "xy",
"mode": "homeautomation",
"reachable": true
}
37,30,52
Difference is not noticeable in this case
Case 3:
BEFORE setting via openhab:
"state": {
"on": true,
"bri": 67,
"hue": 34359,
"sat": 15,
"effect": "none",
"xy": [
0.1469,
0.1474
],
"ct": 230,
"alert": "select",
"colormode": "xy",
"mode": "homeautomation",
"reachable": true
}
209,100,27
AFTER setting via openhab:
"state": {
"on": true,
"bri": 68,
"hue": 43821,
"sat": 254,
"effect": "none",
"xy": [
0.1778,
0.1601
],
"ct": 153,
"alert": "select",
"colormode": "xy",
"mode": "homeautomation",
"reachable": true
}
208,100,27
No big, but noticable difference in this case.
Those are the cases I tested, is there any more info I could provide you with?
Thanks in advance,
Simon
May I ask some of the experts of this post if they have any idea how to resolve my HSBType issue: HSBType automatically resets to 0
Hi,
I’m currently running OpenHAB 2.5.11 and have recently added a Hue Bridge with actually just one Osram Smart+ Color Bulb for testing.
I have the same Color Bulb connected to a zigbee2mqtt instance which is running with a Conbee II Zigbee Stick.
When I set the color of the two bulbs in OpenHAB to 0,100,100, I can clearly see a difference in the saturation of the two bulbs.
It seems that this issue with the Hue Bridge is still open…
@cweitkamp: has there been any progress on this issue? I just came upon the same problem, since moving all my Hue lights to Openhab 3.0 a few weeks ago. Even my family noticed, that when they say “Alexa, turn lamp to red” the red is now no more a vivid red but more a rosé or light red.
I have the same issue here. Especially as I want to animate the colors via OH it’s pretty annoying.