Help ! How to trace ghost automation?

Configuration
1

I have recently been dealing with switches being triggered by ghost automations on three Meross and one Tuya switches. at various times. All appear to be triggered evening and mornings. See log.
My question is there any good tips how to find out what is the cause?
I assume the “Supervisor” is HA itself via automation of some integration.
THanks in advance

I have been using Node-Red for some of the identities.
A common threat of the items is that the devices were replaced at one time due to defects. and replaced with new hardware and added back into mix of the automation by reselecting.

Should I delete the entire flow and rebuild ? ANy internal tracing thoughts to activate in make it easier to confirm the culprit?

All Switch turned off triggered by action Switch: Turn off

6:09:21 AM - 4 hours ago - Supervisor

Switch 2 turned off triggered by action Switch: Turn off

6:09:21 AM - 4 hours ago - Supervisor

Switch 1 turned off triggered by action Switch: Turn off

6:09:21 AM - 4 hours ago - Supervisor

Switch 3 turned off triggered by action Switch: Turn off

6:09:21 AM - 4 hours ago - Supervisor

2

You have a switch group somewhere named “All Switch”. Start by looking where that is defined and what might be using it.

My best guess is Node-Red, since if this was a HA automation the log would clearly say something like All Switch turned off triggered by automation...

1 Like