Eric
Eric
Weird, I have these loggings only for automations triggered by time, date or sun triggers, where I call a script. But you are using device - power triggers, and you...
Automations are not the only source. I.e template sensors with time triggers, where the action calls a script will cause these warnings as well. I have over hundred automations that...
Example of a template binary sensor that causes these warnings: ``` - trigger: - platform: time at: "00:00:05" action: - service: pyscript.check_maintenance_actions data: dashboardUrl: dashboard-kiosk viewTitle: status response_variable: response binary_sensor:...
@hpoperator86 The warnings Are for calling a script without a context. Your automations don't call a script. So I really doubth they cause the warnings.
@TheFes I have my doubts if @hpoperator86 took the right conclusion as he assumed the loggings where the result of automations. As @Mariusthvdb mentioned, I also do see the loggings...
Hi all Accidentally I found out the "action" clause seems crucial (as suggested by @TheFes), when I refactored this sensor (no loggings): ```yaml # Template NOT causing missing context loggings:...
Still hoping this gets resolved
> template binary sensors going to unknown/unavailable briefly at reload makes using alerts suboptimal That is why I believe alerts should ignore 'unavailable/unknown ' and only act on 'on/off' changes
@stugr Hmm that should not make a difference, will check that when I have some time. Thanks