Deconz-rest-plugin: Phoscon: Scene that turns off lights does nothing

[criemen]

For one of my groups I have several scenes, all of them except one have the lights turned off.
Recalling these scenes works fine.
However, when recalling the scene that turns off all the lights nothing happens, and the lights stay at whatever state they were.
Manually turning on and off the lights via the on/off switch in the GUI works, though.

[JoelKlint]

I have this issue aswell. Turning off lights in scenes does not work. I cannot seem to find the version number I am running.

Is there a way to set values for lights in scenes programmatically?

[criemen]

Addition: Switches (Ikea Tradfri plugs) are turned on/off by the scene recall, just not dimmable lightbulbs (in my case Ikea Tradfri bulbs).

[JoelKlint]

I too am using Ikea Trådfri bulbs

[thomasloven]

I have the same problem, but noticed that groups containing the same lights report as turned off.

I.e. the behavior of the lights on the left in the following screenshot is correct, but the actual lights don't turn off.

Deleting all lights from the group and re-adding them made it work sometimes rather than never.
Turning lights ON via a scene never fails.

Further and possibly related - the saved states are not displayed in the scenes editor.

[f0086]

+1

Same configuration (IKEA dimmable light bulbs) as discusses in Discord.

Logs shown after changing to a scene (5 light bulbs, 3 of them should turn off):

deconz    | 23:26:15:775 0x680AE2FFFEB80972 level 25 --> 80
deconz    | 23:26:15:776 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:15:862 ZCL attribute report 0x588E81FFFE4FC8D6 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:15:867 ZCL attribute report 0xEC1BBDFFFEAF95AA for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:15:871 ZCL attribute report 0x588E81FFFE4FC8D6 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:15:875 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:15:894 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:007 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:078 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:182 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:287 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:340 ZCL attribute report 0x588E81FFFE212BE2 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:358 ZCL attribute report 0x588E81FFFE212BE2 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:362 ZCL attribute report 0x588E81FFFE212BE2 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:395 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:490 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:595 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:698 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0300, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:16:774 0x680AE2FFFEB80972 level 80 --> 25
deconz    | 23:26:16:775 ZCL attribute report 0x680AE2FFFEB80972 for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
deconz    | 23:26:17:440 Current channel 15
deconz    | 23:26:17:448 Device TTL 1137 s flags: 0x7

Gateway:

• Vendor: dresden elektronik
• Product: ConBee II
• Version: 2.05.77 / 5/22/2020
• Firmware: 264A0700

[bourskov83]

I have now encountered the described issue... Running deCONZ in a docker container everything was fine for months using scenes to turn off my IKEA Trådfri lights of various kinds...

Then I added additional lights to deCONZ, same type and firmware as the existing lights. These newly added lights cannot be turned off by a scene, but existing lights (pre addition) does work fine... Upgraded lights firmware to latest and greatest for both the working and non-working lights and have the same result - existing lights work, new doesn't...

In the deCONZ GUI I can see the Level Control Cluster reads 0x0000 Current Value at 1, when using brightness to 0 method... using off methon in the scene does not change the light level, but sets the OnOff state in On/Off Cluster to 'false'... I both cases both from Phoscon og deCONZ the light should be off - however, the light is still on with no changes at all to either brightness, color or state.

I then tried to take a working light, reset it, delete it from deconz and re-discover it, and now that light does not work either... I have both E14 and E27 color temperature lights behaving like this.

@Mimiix - as requested I'm tagging you in this issue...

[Mimiix]

Thanks for pinging me(as i requested 😄), i'll forwarded it to @YKO-de and @manup ;)

[ebaauw]

If I may cut in, I doubt that this is a Phoscon issue. In my experience, this is more likely an issue with the API plugin and/or the light firmware. Zigbee scenes are challenging at best and flawed for _Color Temperature_. IKEA made some changes to the _Scenes_ implementation in their ZB3 firmware.

In my experience, scenes tend to work well when created/updated through the _Store Scene_ command. This includes turning lights off on _Recall Scene_. Of course, I haven’t tested all lights, but it works for my Hue lights. The obvious limitation is that _Store Scenes_ copies the entire current light state, so it’s not possible e.g. to create a scene that changes only the colour and leave the brightness unaffected.

While _Add Scene_, at least in theory, could create a scene with only some attributes, I find this command to be erratic for a lot of lights. The Zigbee standard doesn’t cater for _Color Temperature_ in _Add Scene_ and different lights cope with this differently. I haven’t looked into this in detail, but I wouldn’t be surprised if the API plugin doesn’t send the correct _Add Scene_ command for turning the light off. Of course, it could also be an issue with (some versions of) the Trådfri firmware.

To debug these kind of issues, you need a Zigbee sniffer to check the parameters to the _Add Scene_ command and the response to the _Get Scene_ command. Still, I’ve seen lights that don’t report the scene correctly through _Get Scene_.

[YKO-de]

The Phoscon App has nothing to do with this problem. Please ask in deconz-rest-plugin. But I'm not sure if it's not really the FW of the lights.

[criemen]

@YKO-de Can you please move this issue back then?
I opened it in deconz-rest-plugin and you moved this over here.

[Mimiix]

I'll move it back @Cornelius-Riemenschneider :)

[ChrisPrefect]

Is there any update available on this? Will it be fixed some day? Scenes are only about 30% useful if lights can't be turned off. I really hope this gets solved soon. Thanks!

[f0086]

Any update on this? It is very annoying that I can't use the scenes at all. It is pretty useless for me if I can't turn off lights.
Is there any further data/test/log I can provide to help debug (and finally fix) this issue?

[Mimiix]

Forwarded it.

[f0086]

Any insights so far @Mimiix ?

[espen4001]

Have same issue. When versting a scene in phoscon webapp, not all lights are turned off Even if set to minimum in scene.
Wanted to figure out why, and did an API-call to get the scene data from DeConz. Turned out that some lights in my scenes are set to brightness=1 and on=true. And some others are set to brightness= and on=false.
Those who are set to on=false, are always turned off when recalling the scene. Those with brightness=1 and on=true are randomly on or off.
Did an API PUT to modify scene and changed those with brightness=1 and on=true to on=false.
So far my testing shows that this solved the issue.
So my conclusion is that the webgui for creating scenes in phoscon is not always able to set the correct value of lights. Maybe there should be a separate option to select to switch light off, instead of just setting brightness to 0%?

[Mimiix]

@f0086 This one somehow fell trough my net. Sorry! I monitor all issues, this one slipped :(

I pmed @manup again.

[mmaraa]

Same problem here 😔 Wondered, should I move scenes away from deconz to home assistant itself, but perhaps I'll wait a moment before doing the migration.

[manup]

For the on=true issue, can you please check that the sliders are really on the bottom, the icons on the main page should indicate that the lights are indeed off=false.

Related: https://github.com/dresden-elektronik/deconz-rest-plugin-v2/issues/5

[ChrisPrefect]

Yes, the sliders really are at 0%. And the scenes have been saved multiple times after pulling each light to 0% again.

But please: Add "real" switches to the On/Off state and not rely on the sliders in Phoscon. I often am not able to reach 0% or 100%, due to resolution limits of the browser window I guess. There should be a off/on (100%) switch for each light and each group. Or how do you turn on or off groups in the mobile version of Phoscon?

[manup]

Have you tried to use the light symbols, they act as on/off switches?

[sorenjacobi]

I have the same problem. If I turn off the lights with the symbol and saves the scene, the same thing happens: I can turn all lights on to 100% with "turn on" scene, but when I try the "turn off" scene, IKEA colour bulbs stay lit. If I look into deconz, the IKEA bulbs are shown as turned off.

If I then try to turn the entire group on, by clicking on the group bulb icon, all lights will turn on but at the minimum light level. The "turn on" scene still works to get them to 100%.