Lights turning on randomly (usually at night) #85
Assignees
Labels
actionable
Can be implemented immediately
kind/bug
need/author-input
need/community-input
popularity-high
prio
Milestone
Comments
|
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. |
|
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. |
|
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 |
|
So I've had issues with the lights turning back on for two reasons (I think...):
Not sure if these situations will apply to any of you, but it's something to look out for regardless. |
|
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? |
|
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 ***@***.***>, 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.
|
|
Same issue over here. Thought it was because of zigbee2mqtt; but it's not. |
|
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!!!
|
|
Same problem here with adaptive lighting, deconz and ikea bulbs. |
|
Have the same problem, came here to look for the solution. |
|
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. |
|
The solution from soundslikeluke worked for me, Thank you ! |
|
@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?
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. |
|
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. |
|
Hey sevorl, As I understand that was what soundslikeluke meant. |
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:
|
|
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 |
|
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? |
|
Hi, 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! |
|
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. |
|
yeah, so i guess the whole idea of this integration is to have this contiuously adjustment |
|
I've started having this issue as well. It's definitely adaptive lighting as disabling it stops the behaviour. I have latest HA & AL versions, use only philips hue lights with conbee 2 & zigbee2mqtt. Almost all lights are 255 lqi and the behavior occurs semi randomly but is when AL is adjusting the light brightness per schedule. Let me know what debug you would like me to run / debug or config files. |
Configuration.yaml from zigbee2mqtt below. Includes groups/devices.
|
|
I solved this by just turning off adaptive lighting when I turn off the light. So every time I hit a switch or via the Ui it turns the light group and adaptive lighting switch off. Then it turns on when I turn it on.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: thecastle20 ***@***.***>
Sent: Friday, April 28, 2023 9:05:38 PM
To: basnijholt/adaptive-lighting ***@***.***>
Cc: johnlento ***@***.***>; Comment ***@***.***>
Subject: Re: [basnijholt/adaptive-lighting] Lights turning on randomly (usually at night) (#85)
Can anyone having this problem with zigbee2mqtt post their configuration.yaml as well as devices.yaml and groups.yaml?
I was having a similar issue until I set optimistic to true for each light. Without that, changing a light wouldn't actually reflect a state_change to home assistant.
Configuration.yaml from zigbee2mqtt below. Includes groups/devices.
homeassistant: true mqtt: server: mqtt://core-mosquitto:1883 user: addons password: <removed> keepalive: 60 reject_unauthorized: true version: 4 serial: port: /dev/ttyACM0 adapter: deconz frontend: port: 8099 permit_join: false devices: '0x00178801093ab625': friendly_name: Hallway Back Door transition: 0 '0x001788010207e7cb': friendly_name: Kitchen Dining Main transition: 0 '0x0017880110297f3d': friendly_name: Master Bedroom Main transition: 0 '0x00178801066a6af1': friendly_name: Gym Overhead transition: 1 '0x001788010207e3a8': friendly_name: Lounge Main transition: 0 '0x00178801098c8ce5': friendly_name: Lounge Speaker - Left transition: 0 '0x00178801085d322e': friendly_name: Lounge Speaker Right transition: 0 '0x001788010b44b388': friendly_name: Lounge Cabinet Accent transition: 0 '0x001788010bf2c05f': friendly_name: Lounge Couch Accent transition: 0 '0x00158d0006d6ca8e': friendly_name: Kitchen Bifold Doors '0x001788010bce21e8': friendly_name: Motion Sensor - Lounge '0x00158d000709b54e': friendly_name: Smartcube Lounge '0x0017880108bef51a': friendly_name: Lounge Lamp transition: 0 '0x54ef4410004cde77': friendly_name: Lounge - Left Window '0x54ef4410004c71f3': friendly_name: Lounge - Right Window '0x0017880108af35ff': friendly_name: Hallway Front Door transition: 0 '0x001788010c572782': friendly_name: Lounge Audio Accents transition: 0 '0x001788010bf652e5': friendly_name: Lounge - Green Lamp '0x001788010c50a406': friendly_name: Kitchen Bench - Cooktop - B '0x001788010c50aaa8': friendly_name: Kitchen Bench - Cooktop - A '0x001788010c509fc1': friendly_name: Kitchen Bench - Prep - C '0x001788010c50944c': friendly_name: Kitchen Bench - Prep - A '0x001788010c509908': friendly_name: Kitchen Bench - Prep - B '0x001788010c571650': friendly_name: Master Bedroom - Accents '0x001788010c830213': friendly_name: Office Main groups: '1': friendly_name: Lounge_Accents devices: - 0x001788010b44b388/11 - 0x001788010bf2c05f/11 - 0x00178801098c8ce5/11 - 0x00178801085d322e/11 '2': friendly_name: Hallway_Lights devices: - 0x00178801093ab625/11 - 0x0017880108af35ff/11 '3': friendly_name: Lounge_All_Lights devices: - 0x001788010207e3a8/11 - 0x001788010b44b388/11 - 0x001788010c572782/11 '4': friendly_name: Kitchen_Main_Lights devices: - 0x001788010c50aaa8/11 - 0x001788010c50a406/11 - 0x001788010c50944c/11 - 0x001788010c509908/11 - 0x001788010c509fc1/11 '5': friendly_name: Master_Bedroom_All devices: - 0x0017880110297f3d/11 - 0x001788010c571650/11 advanced: log_level: info
—
Reply to this email directly, view it on GitHub<#85 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGHSRT4PK7VMNF5Z7LWYSADXDRSOFANCNFSM4XGMR2PA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Neat workaround - with bad limitations. I don't have an AL instance for all my single lights or groups of lights turned on/off together. And the need for adjusting all automations, scripts etc. is another downside. In fact I'm doing this already for one AL instance, but I'm not willing to extend this to all my other AL instances. Nice approach but... hopefully the integration manages to fix this some day so it actually adds a benefit (again) next to bothering because of these significant issues. |
Good tip. I don't have a huge amount of lights so I guess this will have to be the work around. It seems to show up/become obvious once I add more than three instances of the addon for different light groups. |
|
I've been experiencing the same, especially when HA restarts where my Ikea kitchen cabinet lights and the light that usually comes on via a motion sensor turns on automatically usually in the mornings. I had been looking all over the place for some rogue automation that I might have set up somewhere or something buggy, but turning off AL seemed to stop the issue. I've basically set up the affected lights exactly as @johnlento has, but as mentioned, it's not ideal. I'm surprised there is still no official fix. I would need to look if another issue exists, but I've also noticed that Ikea's Tradfri bulbs generally don't actually turn off sometimes (even though they appear to be off in HA). I am assuming that this is also related and may be an Ikea issue because none of my non-Ikea lights have been affected. |
|
🥳 🎉 I believe this issue is fixed by #663. The main reason for lights turning on is because for some reason: the light will incorrectly report its state as on! Because AL then notices a state change, and this state is likely not precisely what it should be according to AL, it will adapt it to the correct state, inadvertently turning the lights on. In PR #663, I have made some changes. With that code when |
|
This is great news 😄. I will turn on the adaptive lighting for the bedroom lights back on. Will test and report back. |
|
That's reaaaaaaaally great and convincing news 👌🏼 Will wait for the PR being tested and merged and hopefully test the new release once available. Oh that would be awesome, waiting so long for this 😃 |
|
Hi folks! I have merged #663 and released v1.18.0. Set I will close this issue and would really appreciate folks reporting back on whether the issue is fixed. ⚙️ Thanks everyone for your support and patience in getting this issue fixed! 🙌❤️ |
|
BTW if you have debugging logging enabled you'll see messages like these:
This would previously have turned on the light 💡 |
|
I upgraded to v1.18.0, made sure Will turn back in a few days, hopefully without observations of randomly turned on lights. |
|
I'm testing with now with 1.18 as well. |
|
Initial report out, Bas... So far, no issues with phantom lights turning on in the middle of the night :) 💤 |
|
Didn't see phantom turned on lights in the middle of the night either the last days. Just not sure yet if #44 is okay now too, will need to test a bit longer. |
|
OK that is great to hear! I fixed a couple of other bugs in 1.18.3. I hope I didn't introduce any new bugs though 😅 |
|
I've Just moved house and set up a new HA using Adaptive lighting for the first time, so have no history at all. I'm using 1.18.3, and IKEA bulbs. I'm afraid after turning off the 8 bulbs 2-3 will always turn straight back on, albeit dimmed. I've not experienced them turning on at any other time, just straight after turning off. |
|
@robmarshall2, I’d really appreciate it if you could enable debug logging and share your logs. The README shows how to do that. |
|
@basnijholt here you go, hopefully this comes out a suitable format, apologies if not. |
|
Thanks @robmarshall2! I have opened #726 to keep track of it. I am not reopening this issue because it has a different cause. Your problem is that lights immediately turn on after turning off (or not turn off at all). And this issue has been about lights turning on at random moments. |
|
🎉 I have fixed that problem too of lights turning on immediately after turning off (#727). This was a rare condition that showed up when the update that happens at
|
|
Unfortunately recently (since yesterday, roughly) I experience this issue again. Light turns on, but never off. To be precise: afaics, specifically one light turns on within 1 to 2 minutes after it has been turned off - for no obvious reason. There was a change yesterday (updated deCONZ from 2.22.2 to 2.25.3), which is next to a HA OS update the only change.
So I think it's neither really randomly nor immediately after turning it off, but within a "random timeframe within a few minutes after being turned off". Does that make sense? Not sure how to debug that behaviour... I suspect the deCONZ (ZigBee) update as this really just started since then. |
|
Hey @bcutter, this could be either a Bug in AL or a communication error in the Zigbee network. Zigbee works like this: You send a turn-off command to Zigbee and it starts to transmit it. But in the meantime it will already report back, that the light is now off. Once the light has received, processed and acted on this command, the light will send a status update back through the Zigbee network confirming that it's off. If this status update is not received by the network as expected the bulb will show for a while as off, but than flip to "on" again, as the confirmation was never received that it turned off. So HA now shows the bulb back on again, but the bulb is off. A command to change the color temperature is not a "change color if you're on"-command, but always a "turn-on" command. So AL sees the bulb online and will issue a color change command, which then is received by the bulb as "turn on to this color". Easiest way (if you're using Z2M) is to turn off this short term interpolation of the status of the device by going in the settings of the light which is called "optimistic":
If you're using some other plugin to speak to Zigbee, there might be a similar setting. The turn on the debug log for AL and let's see if it still appears. If so attach the debug log. |
|
Interesting, but what you described is definitely not the case...
...as the light is really on, so the HA state and ZigBee state are in sync with the actual physical state of the light. I use deCONZ, not ZHA or ZB2MQTT. As this was the only change I suspect this might have introduced this behavior. I'll
But generally: what I see might really not be related to this issue, as it does not happen randomly. So depending on what I discover I tend to create a separate issue instead of hijacking this one. Edit: @RubenKelevra I created separate #920 also containing a debug log, as requested. |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
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.
The text was updated successfully, but these errors were encountered: