I have the doubt that is not related to any automation.
Because no automation got triggered looking at logbook!
Moreover today one of my tasmotized cover started closing without any request!!! I’M PRETTY SCARED!
look at the logbook:
17:35
xiaomimi6 Screen Sensor turned off
17:35
redminote7 Screen Sensor turned off
17:35
xiaomimi6 Screen Sensor turned on
17:35
xiaomimi6 Screen Sensor turned off
17:35
redminote7 Screen Sensor turned on
17:35
redminote7 Screen Sensor turned off
17:35
redminote7 Screen Sensor turned on
17:35
Bagno Principale changed to idle
17:35
Bagno Secondario changed to idle
17:35
Google Home Mini changed to idle
17:35
Google Home Mini changed to playing
17:35
Bagno Principale changed to playing
17:35
Bagno Secondario changed to playing
17:34
xiaomimi6 Screen Sensor turned on
17:31
redminote7 Screen Sensor turned off
17:30
Tapparella Cucina Su turned off
17:30
redminote7 Screen Sensor turned on
17:30
Tapparella Cucina Su turned on
17:30
Tapparella Cucina Giù turned off
17:30
Tapparella Cucina Giù turned on
17:30
Bagno Principale changed to idle
17:30
Bagno Secondario changed to idle
17:30
Google Home Mini changed to idle
17:30
Bagno Principale changed to playing
17:30
Bagno Secondario changed to playing
17:30
Google Home Mini changed to playing
17:29
HA runtime changed to 15 hours, 29 minutes
17:29
xiaomimi6 Available Status changed to 2019-04-16 17:29:00
17:29
redminote7 Available Status changed to 2019-04-16 17:29:00
17:29
Time changed to 17:29
17:27
last motion changed to Cucina
17:27
Cucina turned on
17:27
redminote7 Screen Sensor turned off
as you may see no phone was active when the cover started closing!
it happens that when I reboot HA the tv switch off. And then I noticed that tv off scripts I don’t know why toggle also other devices than the single tv.
I doubt it’s related to the other switch. Turning off the automation was not a conclusive test if the true cause is unrelated to Home Assistant.
I believe the so-called ‘ghost triggering’ is caused by the same thing that causes all other complaints about ‘ghost triggering’, namely the incorrect use of either retain: true or incorrect configuration of the device’s startup behavior.
Did your configuration for cover.tapparella_cucinaever use retain: true? If it never did, skip to the next paragraph.
If it initially did, and then you changed it to retain: false, the broker continues to retain messages for tapparellacucina/cmnd/backlog (the command topic). To stop it from doing that, you have to purge (delete) retained messages from that topic. MQTT Explorer makes it easy to delete retained messages. You can also delete a retained message by publishing an empty string to the topic (you can use Home Assistant’s MQTT page to do that).
If it never did, check how you programmed the device’s firmware to behave when the device starts. It can be instructed to turn the load on, off, or restore to its previous state. Loss of WiFi, or connection to the MQTT broker, or a power-failure can cause the device to restart.