Hi all, i’m back with a strange problem.
Since yesterday all automations on my HA does’n fire.
I have time trigger and Sun trigger.
It seems nothing changed, but does not run more.
Until yesterday all works fine
Where can i understand ?
Thanks ciao.
Are the automations turned on?
I had the exact same issue after upgrading to 0.85.1. Downgrading to 0.84.6 solved the issue.
Same issue with 0.85.1
No it didn’t. It just saved you reading and finding a solution.
Hi Nick, how i turn on the automation?
Yesterday It worked well, what Is changed?
Not long term no, if you want to use all the.cool new stuff (which Il like to do). But something is fishy with the automations in 0.85+
All my automations were active and could be triggered from the dev console but they simply did not run when the triggers fired.
I spent a couple of days restarting and manually activating automations without any success whatsoever.
Keeping the same configuration but restoring 0.84.6 from snapshot (I’m on hass.io) instantly made all the triggers work.
Even with debug logging there is nothing useful in the logs so it’s a bit hard to produce supporting docs for filing a bug report.
go into the dev-state page.
Look at the automation enities, ie those called automation.whatever.
Is their state on or off?
If they are on and still not working, post the definition of one of the automations that is not working.
Make you use the markup as set out at the top of the page
My version with the issues was the 0.84.6.
Caught by hungry i m restoring.
WTF does that even mean?
Thanks nickrout!
Probably the recent update, put my working automation on state OFF.
I have turned the automation ON from dev page and it’s working again!
You can set your initial_state for your automation with this line:
initial_state: 'off'
or ‘on’ of course. Or if you do not specify initial_state the state will remain the same across restarts of HA.
@nickrout, as I wrote they are all activated, i.e. on in dev-state.
Below is one example of non-firing automations, this one is intended to catch state changes of my Nexa 433-remotes and control all my lights. (i have a firly complex mix of Zigbee, Z-wave and 433 Mhz devices)
As you can see it is a very simple trigger and there is no reason for it not to fire (as long as the automation is active)
# Generic script to handle Nexa remote events
# Remotes are represented as switches with one switch per button
# Each button needs to have a group with the same name as the switch, i.e. switch.remote1 and group.remote1
# NOTE: "Global" buttons only functions as button nr 1 as the "group" attribute is not available in HA.
- id: 'Nexa remotes'
alias: Nexa fjärrkontroller
trigger:
- platform: state
entity_id:
- switch.remote_carl1
- switch.remote_carl2
- switch.remote_carl3
- switch.remote_ellinor1
- switch.remote_ellinor2
- switch.remote_ellinor3
- switch.remote_kontor1
- switch.remote_kontor2
- switch.remote_kontor3
- switch.remote_nils1
- switch.remote_nils2
- switch.remote_nils3
- switch.remote_ovrehall1
- switch.remote_ovrehall2
- switch.remote_ovrehall3
- switch.remote_sovrum1
- switch.remote_sovrum2
- switch.remote_sovrum3
- switch.remote_test1
- switch.remote_test2
- switch.remote_test3
- switch.remote_vardagsrum1
- switch.remote_vardagsrum2
- switch.remote_vardagsrum3
- switch.remoteknapp_carl1
- switch.remoteknapp_carl2
- switch.remoteknapp_nils1
- switch.remoteknapp_nils2
- switch.remoteknapp_vardagsrum1
- switch.remoteknapp_vardagsrum2
action:
service_template: >
{% if trigger.to_state.state == "on" %}
homeassistant.turn_on
{% else %}
homeassistant.turn_off
{% endif %}
data_template:
entity_id: >
group.{{ trigger.to_state.object_id }}I suggest posting an issue on github. I can’t see anything in the changelog that affects it, needs more experienced eyes than mine!
I’ll post an issue.
I just tried upgrading to 0.85.1 and, sure enough, the automation triggers stop working.
Downgrading to 0.84.6 makes triggers fire again.
Exactly the same configuration and automation states!
Have you posted a github issue?
Yes, It’s issue #20162.