Lights turning on randomly (usually at night)

[Just-Insane]

Hello,

I’m having an issue where the lights in some of my rooms are turning on all at the same time every night, and turning them off manually results in them turning back on after a few seconds to a few minutes.

turning off the adaptive-lighting control switch for those rooms results in the lights staying off, however this is not ideal due to having to manually turn the switch back on in the morning.

The lights turning on does not seem to be activated by my motion sensors as I would expect the lights to turn off after the specified time in those automations.

I haven’t found anything in the log book or history in home assistant that would point at the problem.

[soundslikeluke]

I have had the exact same issue it was driving me crazy trying to figure out what was causing the issues after a close examination of the log viewer I found it was caused by Adaptive Lighting.

The way I was triggering the lights was through motion Sensors. They were changing perfectly and adapting that why It took so long to work out this was the cause. It happened when the lights would turn off through automation. The lights were getting the signal to turn off and that was successful but there something would trigger the lights to turn back on but the issue would be they will stay on until manual intervention.

After removing adaptive lighting from having control of the lights they stay off now and have been working Perfectly. I love this feature so hopefully, this can get resolved.

[Just-Insane]

Agreed, it’s very odd.

Right now I have my Hue motion sensors setup to turn on my lights via a call to adaptive lighting on a motion event via Node-Red. As part of that automation, a timer is started for each motion sensor for 10 minutes, after which the lights turn off via a regular call to HA (outside of adaptive lighting).

I would expect this to work correctly with the function that tracks outside light adjustment and overrides adaptive lighting.

I have noticed times where the lights won’t turn off during the day, and also times where lights turn on randomly when I know there isn’t a motion event.

[soundslikeluke]

I'm doing a very similar thing. I tried triggering them via the hue app and node red with a similar automation that starts a timer to turn off the light. I was just turning the light on an off and adaptive lighting would change it.

I'm using the hue sensors via the hue hub. I was thinking it was the hub and was about to buy a con bee II. I'm not sure if there is a way to make it work maybe only adapt the light once when it turns on not continuously

[trevorbenyack]

So I've had issues with the lights turning back on for two reasons (I think...):

1. Misalignment of groups between deCONZ and HA. In other words, using light groups in deCONZ and then selecting individual lights in AL (and vice versa). e.g. I had a total of 8 lights in the living room grouped together in deCONZ and had my motion sensors, remote control, and AL control that group. When watching TV I only wanted the lights behind me to turn off, so I would turn them off individually but they would pop back on since the group command kept getting sent from AL. Once I used the same light entity IDs between the motion sensors/remote and AL, the problem was vastly reduced. The reason being that AL is only scanning for the entity IDs that were selected. So if you're turning the light on/off individually and AL is set to only look for the group entity, it won't see it as an internal HA command. It may pick up the change, but it will be because it's detected a change that was made outside of HA and that feature is pretty unreliable imho. This kinda sucks because you can't get all your lights to turn on at exactly the same time (they go one-by-one) using a deCONZ group, but it's better than them turning on randomly. -- Side note, you can use deCONZ groups, you just need to make sure they are what you've selected in AL. For example, I have a lamp with three bulbs in it that are never turned off individually, so I grouped those and then used that deCONZ group in HA.

2. I had separate commands turned on for my IKEA lights... Ikea lights will ignore a second immediate command if the first had a transition time specified, so to get around this you can either set a transition time of 0 or send the commands separately. I had no luck sending the command separately in AL with a transition time of 1, so I set it to 0 and still kept the commands being sent separately. That was unnecessary and I believe was resulting in them being turned back on by the second light.turn_on service call.

Not sure if these situations will apply to any of you, but it's something to look out for regardless.

[soundslikeluke]

I wasn't using deCONZ groups but I am using the IKEA lights and I am pretty sure they had a transition time on them. And they were the main culprit of turning back on. Did making these changes result in the lights staying off or were they still turning back on?

[trevorbenyack]

I couldn't get the lights to come on properly without the transition=0, and yeah, turning off separate commands seems to have helped as well.

-Trevor Benyack On Feb 13, 2021, 14:44 -0500, soundslikeluke [email protected], wrote:

I wasn't using deCONZ groups but I am using the IKEA lights and I am pretty sure they had a transition time on them. And they were the main culprit of turning back on. Did making these changes result in the lights staying off or were they still turning back on? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[ceesvanegmond]

Same issue over here. Thought it was because of zigbee2mqtt; but it's not.

https://github.com/Koenkk/zigbee2mqtt/issues/6239

[bcutter]

Happy to find this issue as I‘m seeing the same crazy behavior too. It’s really driving me crazy as I don’t can track down a pattern or trigger for lights being turned on automatically.

How to debug and finally fix this?!?

As logbook doesn’t provide detailed information (trigger for light being turned on - usually it would specify user name when switched on via Home Assistant GUI or Service/Switch name when physical switch is used) the only remaining suspect is Adaptive Lighting. Using deCONZ by the way.

Especially annoying when outside lights being turned on randomly during the night, neighbors love that for sure!!!

[sevorl]

Same problem here with adaptive lighting, deconz and ikea bulbs. A few seconds I turn off a group of lights using the ikea 5way button, one or two random lights turn back on again. This does not make it easy to convince my wife that homeassistant is great😊

[alexvdleek]

Have the same problem, came here to look for the solution. Sometimes a light turns on within a few seconds after automation or by 'hand' turns light off. Ikea lights, LIDL motion sensor and a ikea 5 button switch. Happens any time of the day. After disabling adaptive lighting no more issues. A pity, i love adaptive lighting.

[soundslikeluke]

For me the solution was the latest updates and only have the first 2 options selected when setting up the lights. I have never had any issues since

[bcutter]

For me the solution was the latest updates and only have the first 2 options selected when setting up the lights. I have never had any issues since

Can you specify this please? Which "two options" exactly?

Updates didn't fix this so far (for me + others) unfortunately.

[alexvdleek]

The solution from soundslikeluke worked for me, Thank you ! I had the latest update. But deselecting one of the bottom options in adaptive lighting settings made the difference. Lights activated by a button reacted instantly, no more lag or (one) coming back on after a few seconds. I have an ikea motion sensor which i thought was broken ( light on worked but never switches light off) works again.

[sevorl]

@alexvdleek , @soundslikeluke , could you get more specific about what "the first 2 options" mean?

Are you talking about the checkboxes at the bottom of the configuration screen? There are four checkboxes:

• only_once
• take_over_control
• detect_non-ha-changes
• separate_turn_on_commands

Are these the options you are refering to?

This is still a problem for me, and I would really love to understand how you fixed it.

[soundslikeluke]

Hello @sevorl

Yes, those are the options I am referring to just tick the first two and leave the rest, That's what fixed my issues and it has been rock solid ever since.

[alexvdleek]

Hey sevorl,

As I understand that was what soundslikeluke meant. So I unchecked one of the lower boxes and only have 'Take over control' checked, one of the first two. That worked for me.

[bcutter]

For me the solution was the latest updates and only have the first 2 options selected when setting up the lights. I have never had any issues since

I bet the "only once" option (1st of 4 in the config option list at the bottom) "fixed" it for you. If this option does what I think and description says, once you turned on a light it won't get adjusted until it's being turned off and on again.

That means you loose a huge argument for using AL at all (in some rooms my lights are on for a long time so I want and need the color and brightness auto adjustments).

So finally:

1. "only once" option is not a fix. This issue is still an issue.
2. But the "only once" option and what it does could be a first "hot hint" for devs when researching/investigating this issue.

[bcutter]

Sometimes I really wonder what is going on with some lights. Is it the automation? Or is it Adaptive Lighting? One is being turned on and off heavily and I can´t find any pattern.

I use automations based on this blueprint, basically it just works with timers: https://community.home-assistant.io/t/execute-any-service-turn-on-switch-light-scene-scripts-etc-even-run-another-automation-based-on-any-entitys-state-change-motion-sensor-illuminance-sun-rise-set/268132

[LeChuck2909]

Hi, im so glad to find this issue, i have also noticed ghost switches, which seems to be not present, when adaptive light brightness is turned off. also i have this generic logbook entries, where its not clear what acutally turned on the light.

[bcutter]

Hi, im so glad to find this issue, i have also noticed ghost switches, which seems to be not present, when adaptive light brightness is turned off. also i have this generic logbook entries, where its not clear what acutally turned on the light.

Glad to see you're not alone, right. But as you can see here's not really progress, this issue exists for months.

To add something constructive: I set the "only pass once" option some weeks ago, which improves things - but lights are still turned on and off completely randomly. ONLY lights which are controlled by AL. Proof enough this integration does crazy things for no obvious reason.

Feels almost like a "presence faking feature" (holiday mode). It's not a feature but a bug, right?

[LeChuck2909]

Hi, with the release of 1.0.15 i was looking forward, if any of the complains of this issue have been resloved. Sadly this is not the case. I want to use this opprtunity to emphasize, that in my case this is not a minor bug, but is almost as predominant as the features itself. I know this is far off, from a usable bug report, but comparing the magnitude of presence of the bug compared to featureset, i ask you to please take a look at this. As time goes by, and also HA versions get released, im can not exclude, that even the behavior of "this bug" evolves ....

right now the situation is as follows, there is at least 1 lamp (which is cotrolled by this integration) which turn it self on again, quite afer i turend it on.

so i can trigger it. maybe we can use this condition to trace the isse down ?

thx!

[bcutter]

Since enabling the "only pass once" setting I never experienced this issue again. That came with the trade-off of neutering AL down to a static light management unfortunately. No dynamic ("adapting") changes of light anymore.

Wish we could have both. AL feature without this extremely annoying bug.

[LeChuck2909]

yeah, so i guess the whole idea of this integration is to have this contiuously adjustment

[RubenKelevra]

I'm currently in the process of doing version 2. This will be added/fixed.

Keep this ticket open until you can verify that it's properly working in the upcoming version 2.

[kingnlfung]

Hi All, I too have experienced this problem.

New fresh install of adaptive lighting since a week. Lamps goes on randomly. I had to fix it by assigning only_once in the settings.

Looking forward to the fix in version 2.

[TobiasBales]

@kingnlfung what exactly do you mean with

I had to fix it by assigning only_once in the settings.

so that I can replicate it in the mean time :D

[bcutter]

@kingnlfung what exactly do you mean with

I had to fix it by assigning only_once in the settings.

so that I can replicate it in the mean time :D

In the integration configuration options there's this option (I have to use it at almost all my AL integrations - usually whenever I can not enable/disable AL switch): Otherwise lights will randomly turn on. This is the only workaround unfortunately. Really hope this will be solved as noted by the AL king (maintainer) so I (we) can finally benefit from the core usage of AL again.

[LeChuck2909]

so I (we) can finally benefit from the core usage of AL again

I am also so looking forward to this.

[basnijholt]

In this thread on Reddit someone mentions that's this problem happens with Zigbee groups.

https://www.reddit.com/r/homeassistant/comments/s6t7iv/adaptive_lighting_keeps_turning_my_lights_back_on/ht5qr2t/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

Can folks confirm or deny this?

[cdemi]

Yes mine happens with Zigbee groups