I’ve had a simple automation set up that turned a light off at a particular time (Kasa KP405 Dimmer Switch). I later decided to disable the automation, but the light still turned off at that time. So then I deleted the automation, made sure it wasn’t in the YAML, it is still is turning off at that time. I’ve rebooted the device and my HAOS machine, and it’s still doing it. Though I have not factory reset the device.
The log only says the light turned off. Doesn’t say what triggered it. Nothing obvious in the logs.
Any ideas on how I can hunt and kill this ghost automation?
At any stage in setting up that light, getting it onto your network, importing whatever it is to get a CompanyName supplier listed like >Settings >Devices & services> Integrations > Kasa
did you use a kasa app on a smart phone, and might that have left some automations lying about on the cloud?
I ask because I was poking around with a P110 switch from tapo, and to get the wifi-only older tapo device integration, I had linked that device to my network from an android phone with a tapo app, and tested it with an automation entered from the Android app before proceeding further. Another test by switching off that phone for the second night, confirmed that it had got tapo (the brand name) to store some night time switching automations on a tapo cloud. That is, I got ghost automation 24h later from a test switching event which I had entered on the Android in the brand name app.
The solution to remove that ghost-switching, which home assistant can see in its history but not in any .yaml schedule, was to go back to the brand name android app which had been used to link the switch to the home network, to find and remove any switching automations. (yep. it was the same test switching as 24h previously).
Note that both Home Assistant and the android app can control that switch and while switched on record its history, but neither can see the scheduling on the other.
This can only mean that the light was toggled outside of HA.
If you have a separate manufacturer app, start by checking there.
If you don’t, but have Alexa, check if hunches are enabled in its app & switch them off.
Thank you both for your response. I didn’t mention, but I did check both Alexa and the Kasa app, and didn’t see anything. It sounds like my easiest option will be to factory reset the switch and reattached it to home assistant, and see if that solves it.
Edit: Turns out I checked the wrong place on the Kasa app. The automation had been duplicated under the device schedule, and was running from there.