-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scene won't set ct
for Color temperature light
#53
Comments
I added the Ikea Trådfri to the group and scene, and the Here's the scene with the Trådfri added:
The database now contains: [
{
"bri": 254,
"cl": false,
"clTime": 0,
"cm": "ct",
"ct": 370,
"lid": "244",
"on": true,
"tt": 4,
"x": 30091,
"y": 26912
},
{
"bri": 254,
"cm": "none",
"lid": "241",
"on": true,
"tt": 4
},
{
"bri": 254,
"cm": "none",
"lid": "242",
"on": true,
"tt": 4
},
{
"bri": 254,
"cl": false,
"clTime": 0,
"cm": "ct",
"ct": 370,
"lid": "243",
"on": true,
"tt": 4,
"x": 30091,
"y": 26912
},
{
"bri": 254,
"cl": false,
"clTime": 25,
"cm": "ct",
"ct": 454,
"lid": "101",
"on": true,
"tt": 4,
"x": 33112,
"y": 27216
}
] Here's the lights (after reading the attributes of the 0x0300 clusters in de deCONZ GUI):
|
Indeed. Here's what happens with the Hue Extended color lights.
|
Or the OSRAMs simply don't accept a change to |
I saw that the OSRAM lights do support attribute reporting in commit 887e6b1. I'm still on 2.04.57, but I managed to configure attribute reporting manually for the 0x0300 cluster. I now receive multiple websocket notifications when recalling the scene:
The scene actually contains |
We have seen various problems with OSRAM scenes and ct, also when switching between xy and ct. Maybe the reporting can help here to reduce the issues. |
These are colour temperature lights, which don't support The issue isn't with recalling the scene, though; it's with storing it. When I store the scene per light from the deCONZ GUI, the correct |
This also happens with the IKEA GU 10 Color Temperature lights.
Recalling a saved scene doesn't restore the color temperature. Probably because the color temperature isn't stored. When I set the light to state:
only 4 of the leds in the bulb are on. After that I store the light state in a scene. After changing the light color and recalling the stored scene all leds in the bulb are on and the REST API shows the following state:
|
Odd, I wouldn’t expect different IKEA lights to behave differently, but maybe it’s the newer firmware. I’ll retest my E27 white spectrum. |
I can verify this exact same behaviour for "TRADFRI bulb E27 WS opal 980lm" (Version 1.2.217) bulbs, meaning that I cannot use scenes with deconz if I ever want to have different color than ct 370. What is the current state on this? Is it a bug on IKEAs side or can this be fixed in deconz? |
It’s a combination of a weird interpretation of the ZigBee standard on the IKEA side, and poor handling by deCONZ. I have good hopes it can be fixed at the deCONZ side, but it will take some time. I’m not too familiar with the code supporting lights and Manuel is traveling and will want to work on the stability issues first. |
I'm seeing the opposite behavior with the TRADFRI bulb E27 WS opal 980lm bulbs. If I change color temperature and brightness in the same REST API call, then only the color temperature changes (querying state over the REST API indicates that deCONZ believes the brightness did change though). Changing the parameters separately works. I'm not familiar with the Zigbee protocol but the intuition I get is that one of the two updates is being lost before it is sent across the Zigbee network. I don't see why deCONZ would need to query the bulb state between setting the two parameters. Edit: It seems the rabbit hole goes a bit deeper than just being a deCONZ issue? https://community.home-assistant.io/t/ikea-light-on-hue-hub-scene-doesnt-change-brightness/32755 |
Scenes in the IKEA bulbs have indeed a bug for some reason the color temperature is not restored to the value stored in the scene. I'm not sure if the issue can be fixed on deCONZ side, needs more testing. Scenes can be created and stored in various ways maybe IKEA does support one of them. |
I have been able to setup the scenes for me and they are working as intended as far as I can tell. Edit: I'm referring to the IKEA E27 WS opal 980lm bulbs |
I can confirm the observation of @tpetri for the IKEA TRADFRI bulb GU10 WS 400lm lights. See my comment in December: e0513b1#commitcomment-26187674 |
Good find, we can build a workaround on top of that. |
I apologize if I'm simply being ignorant of how the protocol works, but I don't have any issues setting the color temperature of the Tradfri bulb — as long as I don't set the brightness in the same API call. I.e. sending:
to the state endpoint works just fine. But if I send
then it misbehaves. |
If I click on my ikea remote group via the web interface and change temperature not with the temperature slide but with the color slide then I get the temperature stored in the scene with my ikea bulbs |
@mattiasflodin that is correct, setting the temperature with ct works, but if you want to store it as a scene, this will fail. Maybe the same reason why setting ct and bri at once does not work, I haven't actually tried setting xy together with bri, if that works, this would be the solution for a workaround indeed. |
* use move to color x,y instead of move to color temperature (unicast only) * fix color mode always reported as "ct" for color temperature only lights * check ct min/max bounds * store color capabilities, ctmin, ctmax in database * in order for scenes to work lights ct must be configured unicast before storing scenes (groups still broken) Issues #629 #53
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This topic actually diverted into two issues, neither of which as been solved:
|
In my case the issue with IKEA bulbs was that when storing a scene, the bulbs would store the color if and only if it was set with xy. If the ct value was used the temperature was not (or wrongly) stored. No connection to transition times, at least for me and as far as I understand/see. I haven't been checking if something has changed to this end (never touch a running system ;)). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I have two OSRAM E14 Colour temperature lights (from the time before Philips released their E14 bulbs). I cannot set their colour temperature using a scene.
Here's the transcript of what I do (using my
ph.sh
bash script, which is just a wrapper aroundcurl
):The scene seems to contain the correct light states. When recalling the scene, the API reports the issued values (from the scene). However, the OSRAM bulbs actually have a
ct
value of 153. After having polled the lights, deCONZ reflects this:Oddly this works, when using a similar setup for my Hue extended color lights. I'm not sure if this is caused by the OSRAM bulbs, or whether it's deCONZ issue with colour temperature lights. It might be related to issue #30 point 3: I see
colorloop
andxy
are specified in the scenes table in the database (my formatting):The text was updated successfully, but these errors were encountered: