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 creating 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%.

[f0086]

@manup I don't think this is a user problem (sliders not dragged to the bottom, not tried to turn the bulb completely off by hitting the bulb symbol, etc.) as proved by a lot of people here. When I set up the scene with lights off, the lights turn off as it should and the bulb turned gray. When I save the scene, switch all lights on and recall the scene, the lights do not turn off.

This is a very annoying bug and makes the scenes unusable :cry: PLEASE give us some instructions how to debug this further. What information do you need to reveal the root cause?

I will do the same as @mmaraa if this bug is not taken seriously.

[gongevangen]

I have the same problem, 3 out of 10 Ikea bulb's I cannot turn off. Really make scenes useless

[FreshJonte]

I am having a simular issue with the ikea color bulbs as well. When toggling the light off through my dashboard sometimes the state changes to off but the light is still on - Deconz also shows off. Super anoying when lights are not turning off reliably.

[JurjenBraam]

I too face the same issue where my lights do turn on correctly with a scene but only one of the lights won't turn off with a scene.

Work correctly: 6x TRADFRI bulb GU10 WW 400lm 1x TRÅDFRI bulb E27 CWS opal 600lm 2x TRÅDFRI control outlet

Won't work correctly: 1x TRADFRI bulb E27 WS opal 1000lm

The Phoscon and Homekit state is that the light is off however it's still turned on..

[Drumdevil]

Just got the Conbee II stick and have the same problem with my IKEA bulbs.

[tjfoth]

Have to agree... this is broken for me. I'm using Ikea switches, too, with gledopto LED strip controllers. Note that if I use the old web app and press the Off button for the LED strips, the lights actually go completely off.

In the pwa, if you set the brightness to 0 (and the lights go out) and then save the scene, the brightness pops up to 1.

[espen4001]

I want to point out the need for a change in the scene settings page to be able to select if a light should be on or off, in addition to set the brightness to any value between 1 and 255. As the scene report from DeConz is inconsistent in the light state report on="true" or on="false" when setting the brightness slider to a minimum. Would recommend a switch to be able to set the light to be on or off, and this switch should override the brightness slider setting if set to "off".

[eSoares]

I'm having the same issue.

I have in scenes two lightbulbs from IKEA TRÅDFRI:

• TRÅDFRI bulb E27 CWS opal 600lm (version 1.3.002) : works correctly with scenes to turn on or off
• TRADFRI bulb E27 WS opal 1000lm (version 2.0.022) : unable to turn off

My version of deconz is 2.10.00 (12/23/2020) and gateway firmware 26660700.

After clicking in a scene to turn light off the light stays on but says is off in the UI. Turning light on and then off in the UI changes the light state to off.

Maybe the problem is with the fade out to off? If more logs are needed, feel free to ask.

[keks]

BTW I have the same issue with the official IKEA gateway and app, so it might not be your fault (not asking you to fix my situation, just a heads up that you are not alone and it sounds like an upstream issue)

[falkenbt]

Same issue here with some Ikea bulbs, would really appreciate any hints or workarounds that could apply.

[erik3rik]

I have the same issue. I have both IKEA TRÅDFRI and Philips Hue lights. It works fine to have the Philips Hue lights off in a scene (and recalling that scene will turn the light gray in the Phoscon app and the light will physically turn off as expected).

However, for the IKEA lights, the Phoscon app will also display them as gray and turned off but in reality the lights are actually on. It happens EVERY time for the IKEA lights, it never happens with the Philips Hue lights.

If I connect the IKEA lights to the IKEA TRÅDFRI GATEWAY, and create scenes in the IKEA app that includes lights that are off, it works as expected to recall the scenes.

To summarize:

• It is not really the Phoscon GUI that is problematic. It displays the (wanted) state correctly; with the lights that are supposed to be turned off as grayed out.
• It is not really the GUI or any general property of the ConBee II, as it works every time for the Philips Hue lights.
• It is not really the IKEA lights, as they do turn off when included with an "off state" in the scene as expected when connected to the IKEA GATEWAY.
• But it never works with the IKEA lights if they are connected to the ConBee II / is configured to be off in a scene in the Phoscon app.

So there must be something different that the Phoscon app / ConBee II does when interacting with the IKEA lights compared to what the native IKEA TRÅDFRI GATEWAY does. I have no idea if that difference is IKEA not following the standards, or have glitchy firmware, or if it is the deconz / ConBee / Phoscon app that does not do things right. However, since a lot of people obviously has serous issues with this, perhaps a compensation or workaround for this glitchyness could be added to the deconz / ConBee / Phoscon thingy as IKEA will probably not fix anything. They are good at making cheap furniture, but not at making good software.

[MagnusKazen]

Hi. Got similar problems that appeared quite recently after using Deconz to upgrade the firmware OTA of my Tradfri lightbulbs. Started with just one light in one room but then spread. Found this thread searching for answers. So I did some digging. I'm no programmer but work as a technician finding and solving hardware problems in cameras and lenses etc. I use a Conbee stick in my Home Assistant setup connected to Coogle Assistant through HA cloud (Nabu Casa). Hope my findings can be of some use for someone to dig further.

The problems emerged when my tradfri lights were updated to latest FW through Deconz OTAU. Two lamps with the same model, TRÅDFRI bulb E14 opal 400lm, one with FW 1.2.221 and one with 2.3.050, the old FW worked, the new FW didn't. While testing, the old FW was updated and stopped working.

With Google Assistant I command to set a light at a specific percentage, (Set readinglamp to 30%), and it also works to set the lamp to 0%, that will turn the light off. I can also increase a light with a percentage or to a percentage. These commands seem to be handled differently. When i Increase reading light to 30% it will stay on 30% as expected, while increase with 30% will do just that. The opposite, decrease to 0% will turn the light off while decrease with 100%, or whatever percentage it was lit with, will decrease the light to 1% but not turn it off. However, this goes for any light, even non-Tradfri and also Tradfri with old FW,

If I do the same from Home Assistant it will result in a turned off light, but there the command for brightness and the command for color is sent separately, thus the color is changed and then the brightness is adjusted. If I add a transition time of one second, this will change only the color, the brightness will never change. Seems the command for changing the color is blocking the command for brighness. (Actually one reason to keept the scenes withing the conbee bridge.)

So far there is nothing really peculiar here, apart from the decreace with 100% that will leave the light at 1%.

Moving to the Phoscon app and scene settings, the results are a bit different. Sending a scene command changing both brightness and color will do that, both, so that command is not sent the same way as from HA. Also the transition is smooth for both color and brightness. I've tested this with another lamp, a TRADFRI Bulb E27 WS Clear 950lm. The only issue is that the slider for the color temperature is not always going to the preset position but really close. I tested sliding it to a warm white as possible but when recalling that scene, the slider was about 10% from the end.

Now sending a scene command where the brighness is 0 and the color is the same will result in nothing. The qustion is what actually is sent, and why the new FW can't interprate it correctly while the old could. One possibility is that the newer FW regards a command containing both a color and a 0 brightness as invalid since the reaction is nothing, which acutally ought to be correct, A no-light at all can't really have a color.

The solution in my humble opinion should be to correct the scenes to not send a color when the brightness is set to 0. Actually, when wishing for changes, it should be possible to choose if both color and brightnes or only one of those parameters should be changed by the scene. And a possibility to enter a value for those settings to make it easier to set to lamps beside each other to the same values in a scene.

[espen4001]

Hi.

Got similar problems that appeared quite recently after using Deconz to upgrade the firmware OTA of my Tradfri lightbulbs.

Started with just one light in one room but then spread. Found this thread searching for answers.

So I did some digging.

I'm no programmer but work as a technician finding and solving hardware problems in cameras and lenses etc.

I use a Conbee stick in my Home Assistant setup connected to Coogle Assistant through HA cloud (Nabu Casa).

Hope my findings can be of some use for someone to dig further.

The problems emerged when my tradfri lights were updated to latest FW through Deconz OTAU.

Two lamps with the same model, TRÅDFRI bulb E14 opal 400lm, one with FW 1.2.221 and one with 2.3.050, the old FW worked, the new FW didn't. While testing, the old FW was updated and stopped working.

With Google Assistant I command to set a light at a specific percentage, (Set readinglamp to 30%), and it also works to set the lamp to 0%, that will turn the light off.

I can also increase a light with a percentage or to a percentage. These commands seem to be handled differently.

When i Increase reading light to 30% it will stay on 30% as expected, while increase with 30% will do just that.

The opposite, decrease to 0% will turn the light off while decrease with 100%, or whatever percentage it was lit with, will decrease the light to 1% but not turn it off. However, this goes for any light, even non-Tradfri and also Tradfri with old FW,

If I do the same from Home Assistant it will result in a turned off light, but there the command for brightness and the command for color is sent separately, thus the color is changed and then the brightness is adjusted. If I add a transition time of one second, this will change only the color, the brightness will never change. Seems the command for changing the color is blocking the command for brighness. (Actually one reason to keept the scenes withing the conbee bridge.)

So far there is nothing really peculiar here, apart from the decreace with 100% that will leave the light at 1%.

Moving to the Phoscon app and scene settings, the results are a bit different.

Sending a scene command changing both brightness and color will do that, both, so that command is not sent the same way as from HA. Also the transition is smooth for both color and brightness.

I've tested this with another lamp, a TRADFRI Bulb E27 WS Clear 950lm.

The only issue is that the slider for the color temperature is not always going to the preset position but really close. I tested sliding it to a warm white as possible but when recalling that scene, the slider was about 10% from the end.

Now sending a scene command where the brighness is 0 and the color is the same will result in nothing.

The qustion is what actually is sent, and why the new FW can't interprate it correctly while the old could.

One possibility is that the newer FW regards a command containing both a color and a 0 brightness as invalid since the reaction is nothing, which acutally ought to be correct, A no-light at all can't really have a color.

The solution in my humble opinion should be to correct the scenes to not send a color when the brightness is set to 0.

Actually, when wishing for changes, it should be possible to choose if both color and brightnes or only one of those parameters should be changed by the scene. And a possibility to enter a value for those settings to make it easier to set to lamps beside each other to the same values in a scene.

I have similar issues after performing OTA updates to my IKEA lights. Upgraded to FW 2.0.029. Scene recalls does not work at all. But individual control of each light works fine. I have created my scenes by manually creating them through API-POST commands, to make sure the states are correct. As I have mentioned earlier in this thread, creating them through the Phoscon GUI doesnt always set the states correctly when wanted state is "off".

[MagnusKazen]

I have similar issues after performing OTA updates to my IKEA lights. Upgraded to FW 2.0.029. Scene recalls does not work at all. But individual control of each light works fine. I have created my scenes by manually creating them through API-POST commands, to make sure the states are correct. As I have mentioned earlier in this thread, creating them through the Phoscon GUI doesnt always set the states correctly when wanted state is "off".

Using API-POST commands sounds as nice way to go, is there some information available on how to do that for a total rookie?

[woutput]

FYI: I use Tradfri GU10 spots with IKEA's Home smart app, also in this "normal" case the default "All off" scene doesn't work correctly: it only turns off 2 of my 14 lights. Also removing & re-adding the lights doesn't solve this. So I think there is a big chance that the cause is in the IKEA FW/SW itself.

[nicobuelk]

Hi,

I have similar problems but after updating the ConBee II firmware to 266B0700 and deconz to 2.12.03 the behaviour changed. My TRADFRI light bulbs also received an firmware update. I am only listing the bulbs that are causing problems after the update:

• 1000lm WS E27 -> 0x20029623
• GU10 W -> 0x23050631
• Driver for built in lights (hp and lp) -> 0x23068631

Now activating a scene does not turn the light ON. Turning the light off by activating a scene works fine. Also the color temperature of the 1000lm WS E27 bulbs does not change with a scene change.

Both the 1000lm and the GU10 bulb can be controlled individually. The driver for built in lights does nothing even when controlled individually.

[woutput]

FYI: I use Tradfri GU10 spots with IKEA's Home smart app, also in this "normal" case the default "All off" scene doesn't work correctly: it only turns off 2 of my 14 lights. Also removing & re-adding the lights doesn't solve this. So I think there is a big chance that the cause is in the IKEA FW/SW itself.

A firmware update (released somewhere during the last two weeks) by IKEA solved the problem for my configuration.

[fillilutten]

I still have this problem with my "TRÅDFRI bulb E27 CWS opal 600lm". Running fw version 1.3.013.

[nicobuelk]

For me nothing changed. I am checking for firmware updates almost every day. Is there a way of downloading older firmware?

[wischnu]

As I still have this issue, I downgraded my TRADFRI lamps to the original firmware. Here is a link to older firmwares. https://github.com/basilfx/TRADFRI-Hacking/tree/master/firmwares/ikea/otau

Now I have the issue that some lamps are not turning on with the scenes... Still better like this.

[wischnu]

I have similar issues after performing OTA updates to my IKEA lights. Upgraded to FW 2.0.029. Scene recalls does not work at all. But individual control of each light works fine. I have created my scenes by manually creating them through API-POST commands, to make sure the states are correct. As I have mentioned earlier in this thread, creating them through the Phoscon GUI doesnt always set the states correctly when wanted state is "off".

Using API-POST commands sounds as nice way to go, is there some information available on how to do that for a total rookie?

If someone is interested I could post some python lines on how I automated it using the REST Websocket interface. In the scenes all lamps with brightness of 1 will be turned off automatically by the script. It is a workaround, but it works quite well.

[falkenbt]

I would be interested! When / how is the script called?

[wischnu]

Condition: Scenes that call a TRADFRI lamp to turn off do not run correctly. All other scenes where the lamps stay "on" at whatever brightness work perfectly.

Solution: I have put together a simple script that checks if a lamp has been switched to brightness 1 (lowest possible brightness). If yes, then the script turns off the lamp(s). By this, you can create working scenes with the tradfri lamps where a brightness of 1 equal to an "off" state.

For the script to run, you need to have python available. Then install the deconzpy library (sudo pip3 install deconzpy) that handles the websocket interface with the Deconz server.

The config is a config.json file at the location with the script with the following content: {"gatewayIP": "1.1.1.1", "username": "user"}

The user is the API Access token that you can get from the Phoscon help page under API Information.

When switching the scene, the deconzpy library throws an exception, but it still works.

The best is to let this script run in the background directly where Deconz is installed.

from deconzpy import Router
import time

router = Router() # Router is a singelton, can be called in multiple places and will return the same Router Object
router.startAndRunThread() # subscribe to websocket (for updates)

def onChange_Light(light, key_that_changed, old_bri, new_bri): # Acts if brightness of light changes
    print("Brightness switched from: " + str(old_bri) + " to: " + str(new_bri))
    if new_bri == 1: #if brightness is switched to 1 turn off light
        time.sleep(1)
        light.actionOff()

Light1=router.getLightByName("IKEA Tradfri Lamp 1") # subscribe to brightness changes of the defined light
Light1.subscribeToAttribute("state_bri", onChange_Light)

while True: # run main thread in a loop
    time.sleep(5)

[manup]

Side note: Since a while deCONZ contains a small workaround to send unicast "Off with effect" commands in addition to the group scene command to lights which are "off" in the scene, in my tests this was the only way to turn the damn lights off, since they wouldn't even react to normal "off" commands.

https://github.com/dresden-elektronik/deconz-rest-plugin/blob/4209428e9c428271ca0ddc1175ef5469b4be7470/rest_groups.cpp#L2704-L2717

I have this scenario in my bathroom with 4 Ikea GU10 where in one scene 2 lights are off, without the workaround the 2 off lights won't turn off (which used to work in older Ikea firmware versions). Usually the workaround is applied automatically as long as the light state in the REST API scene is false.

[easybeat]

Was this bug ever fixed?

I have a similar problem with new lights added to my system that I just can't setup them in new scenes. It looks like the scene is just not stored into the light at all. Any hints on this?