Lights turning on for unknown reason

Multiple lights around my house turn on all at the same instant, multiple times a day, and last night they did it at 10 pm - 11 pm, wife NOT happy. Some of these lights do not have any automation or script to turn them on (only off) so I can’t figure out what is happening.
EG logbook:

The logbook doesn’t help me very much, I don’t know where to go from that minimal info.

I thought it might be the adaptive lighting integration, so disabled that, still happens, the only thing I can say is that it does seems to be HA related, as it never happens when I shut down HA.

Edit: All lights are tuya based, setup via local Tuya, I do have the new official Tuya integration setup as well so I can access scenes and such from it. There are no automations within Tuya to turn on those lights either.
Thanks for any help.

1 Like

It doesn’t happen at night? Do these lights have a ‘go to’ state on when those lights recover from power or connectivity loss? Also you could look at every individual lights history to check if they have been available, or if there are issues there.

Maybe you could try and get the ligths to trigger on by messing around with the connection to them to learn what is really going on

So far I have been unable to figure out why they trigger, so turning the power switch off to that light seems to work :rofl:.
Except last night was hot and we needed fans, so the ceiling fan light combo kinda needed to stay on. So shut down HA to stop the lights.

1 Like

If I recall correctly, if you rename an entity you will get the option/question to make the automations follow the new entity name.
Try this but decline the offer. If there is some automation that triggers the lights then it should error in the logs.

4 Likes

Thanks for the idea, will try it out. It seems especially odd that some of the lights turn on when there is no automation to do it, also if your idea works and the error shows in the log, then why doesn’t the current trigger show up?
Asking hypothetically not actually expecting you to be able to answer :wink:

1 Like

I don’t know.
Perhaps you have automations in Node red or somewhere else?

And if it still “works” after the name change then we know it’s nothing in HA that is doing it.

That leaves cloud if that is a factor, like IFTTT, native app(s), Google Assistant/Alexa and so on.

Or hardware

Do you use adaptive lighting or circadian lighting?

1 Like

Yes, I do use the adaptive lighting, I thought I had eliminated it by disabling the integration for a while and still observing the same behaviour, however, I think I might try that again for a longer time period.

1 Like

So far I have not observed the lights coming on when HA is shut down, leading me to the conclusion that it “must” somehow be HA related.

Don’t have any Node red automation, the native app does not have any automation for turning the lights on.

Thanks for all the suggestions, I really do appreciate it!

1 Like

Do you have any automations that turn on areas though?

That’s a good thought, I will check, once again I am confused as to why the logbook does not show this happening.

So I have completely isolated some lights: no automations, no scripts, not part of any area, adaptive lighting integration is completely removed. With HA turned off nothing turns on, with HA running I get lights turning on.
The latest idea is I just noticed a logbook entry of nmap ‘finding’ a device on the wifi, just as all the lights turn on. Maybe the network scan is trigging the lights to turn on.

1 Like

What about any Template Light or Template Switch that include the lights?

Thank you, but I don’t use templates (had to actually look them up to see what they were and make sure).

So got a new/odd entry in the logs, light got turned off by service light.on.

This has happened since removing the nmap integration, so it wasn’t that.

Just for kicks and crazy ideas…

Run tcpdump and make sure a remote API call isn’t calling light.turn_on?

[edit] spelling

Sounds like a good idea, but a little over my current skill level. hitting up google to see how :wink:

With my “old” z-wave standard dimmer switches that don’t send their status to HA (I forget the right word), if I turn them off with their dimmer switch itself, adaptive lighting will turn the light on during the next brightness adjustment, as HA thinks that the light is still on. I had to tweak some settings and setup some gentle polling of some lights to make it work.

Does this problem occur if you turn off the light from HA? If I do that, the “unknown” turn on doesn’t happen. If you see the same behavior it’s probably adaptive lighting and I can give you a few pointers on how to reduce or eliminate the issue.

1 Like

Thanks, this may indeed be helpful, perhaps not the exact cause this time. Lights are still turning on when I removed the adaptive lighting integration, and I nearly always use HA to turn the lights off. Although it got me thinking, and I realised I may have caused a similar problem by having the local Tuya config of the lights as well as the HA Tuya integration, thus creating the issue where HA still thinks the light is on, as it may be looking at the other version of the light.
So I disabled the device of each of the lights on the Tuya integration, leaving only the local version (I hope :wink: )
Sadly so far this does not seem to have worked, although my lights did not auto turn on overnight, only during the day.

1 Like

Hey Michael,

did you find a solution so far ?
I’ve got the same mysterious turn on on lights …

2 Likes

Never found a solution, I ended up doing a complete rebuild from scratch of the whole system.

2 Likes