MickW69,
I have am having the same problem! Did you ever find a solution? Did rebuilding solve the mystery lights.on with localtuya? From what I can tell, when my local tuya lights lose connection it seems there is a default to turn the light to 56% at a specific color.
Iâm having the same problem with lights coming on randomly. I have both the cloud Tuya integration and the new Tuya Local (please note not Local Tuya but Tuya Local) installed. I canât remove the cloud Tuya as Tuya local does not support all my devices.
Any ideas on this one?
Something like that happened to me and only recently after 6 months I found the error.
In my case it was due to an automation with a (A) long delay action, (B) running in 5x queued mode and (C) the rare case that the automation triggers several times in a short time.
Thus, actions still ran after 1.5 h and it could not be traced. Also not via the trace function.
I my case it was ok to change the mode to restart
Alexa hunches also does this, turn that off if you can
Has there been any movement on this? I am still getting random lights turning on in random patterns at random times. Could this be a network or connection issue?
These forums can be great but I wish there was someone that could give help in realtime to make sure everything is set up properly.
We canât really help with what youâve posted. Youâve provided no information.
I just had the same thing happen to me, on new years day after the wife and I got to bed at 2am, at 3:54 every light in the house switched on (and we all know how difficult it is to get your SO onboard) went through the logs this morning and it seems to be in my case at least that Alexa is turning them on, still havenât figured out what in Alexa is doing this and may just kill Alexa integration entirely but found this.
Fortunately my wife does have a button next to her bed that turns off all lights so small wins 
Here is a log entry I found,
This light randomly turned on and this is the entry associated with itâŚdoes this help? I donât understand how to troubleshoot this further.
2024-01-13 09:48:13.612 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=light, service=turn_on, service_data=entity_id=light.galley_04, transition=900.0, profile=relax>
here is a shot from the logbookâŚ
I am not sure how to identify what triggered these lights to turn on??
I have disabled the Alexa app in HA and that seems to stop my mysterious light on issue. However, I have a ceiling fan light that still continues to turn on. Below is the logbook entry for this device.
You can see that I turn it off, but WHAT is triggering it on??
Puppy palace fan Warm light turned off triggered by service Home Assistant Core Integration: Generic turn off
07:04:33 - 13 minutes ago - Jochem27
Puppy palace fan Daylight light turned on
07:01:37 - 16 minutes ago
Puppy palace fan Warm light turned on
07:01:37 - 16 minutes ago
Puppy palace fan Daylight light turned off triggered by service Home Assistant Core Integration: Generic turn off
06:39:45 - 38 minutes ago - Jochem27
Puppy palace fan Warm light turned off triggered by service Home Assistant Core Integration: Generic turn off
06:39:45 - 38 minutes ago - Jochem27
Puppy palace fan Daylight light turned on
04:18:35 - 3 hours ago
Puppy palace fan Warm light turned on
04:18:35 - 3 hours ago
you have an automation using homeassistant.turn_on or homeassistant.turn_off.
Would I look through the yaml code in each automation to find this? Or search through homeassistant.turn_on in StudioCode to see where this pops up?
I have looked in the âdevice infoâ and have no automations associated with this fixture. I searched StudioCode for homeassistant.turn_on & _off and did not find anything. I also looked the all the yaml code in my automations
How else should I search for this?
looking through each code wonât always easily find the cause if you have things like groups (do you?) or if you have a script that enumerates lights or things like that.
a couple things iâd tryâŚ
when the light turns on, check to see if any automation was triggered at that time or if any script ran at that time. remember that you can go to the automations page and script page and sort by âlast triggeredâ and find it relatively easily.
if that doesnât show a good lead, i might try disabling the the entity. if that entity was referenced directly that should trigger and error that would show up in the system logs. i believe that error is warning level so it should be there by default unless youâve changed the default logging level.
