In 15 minutes of HA restart some switches have been turned off , I can see this in logbook. But I do not see what triggered them. for instance 3 shutters out of 7 were closed. at the same time the rest of them are still open. How can I check why those 3 switches were turned off?

Just to close this ghost automation trigger case. After a number of experiments the solution I found working to me is using condition as below. Also, in the automation I cannot use sun.sun attribute ‘elevation’ from trigger.from_state because it returns a data structure. As such I need to use a sen…

“Template result” - do you mean status of automation? is it stored somewhere?

After a restart the value of these trigger templates: value_template: '{{ state_attr(''sun.sun'', ''elevation'') }}' Will be ‘unknown’ until the sun.sun integration updates. As soon as sun.sun updates they will become some value. In this case -32°, triggering the automations. I think the way aro…

I have such sensors for my sonoff POW R2 values (current, energy etc) . Right after HA restart they all are set to ‘unknown’ . Then first MQTT msg arrives from the device to HA the sensors are updated with real values…

Yep. MQTT is a different kettle of fish. You can set the retain flag on those sensors (on the device that sends them) to fix that.

“Retain” is not a flag for sensor config but it should arrive as part of State msg. no? [image] MQTT Sensor Instructions on how to integrate MQTT sensors within Home Assistant.

Correct which is why I said: [image] tom_l: on the device that sends them You have to be careful what you set to retain though. See: [Fix Random Switching in Tasmota by Adjusting Retain Settings]

Just a related FYI: [image] WTH: Can't we see which trigger fired an automation? Month of "What the heck?!" (2020) I have many automatons with multiple triggers. It would help greatly to be able to see which trigger fired an automation when an automation triggers unexpect…

Phil, any comment on the likely effectiveness of this? [image] Event triggering tracking in logs Configuration After a restart the value of these trigger templates: value_template: '{{ state_attr(''sun.sun'', ''elevation'') }}' Will be ‘unknown’ until the sun.sun integr…

First, template sensors are not restored after a restart. They only update when the referenced entity or entities update(s.) Regarding the template trigger, it would act the same was as a numeric_state trigger. The first update of the reference entity will cause it to evaluate, If true it will fire…

Thanks. The only issue with that solution would be if there was a restart just before the trigger is due (less likely than the previous issue of restarting after sunset) which would cause a valid trigger to be missed.

Event triggering tracking in logs

Configuration

pnbruckner (Phil) August 27, 2020, 2:57pm 20

Just a related FYI: