so I have had this exact config working on 85.1 for 2 weeks, tonight, my hall automation stopped working, then after a reboot it started working again and now the landing one stopped working …
code: https://pastebin.com/Y7EL7HXG
same behaviour after upgrade to latest version
entity_id’s are correct and I can see the state change in the motion sensor but it just doesn’t seem to run the automation
Your times for before and after are formatted incorrectly, should be "HH:MM:SS". Yours are just "HH:MM". Not sure how they were working in the past.
I’ll give that a try but that doesn’t explain why hall automation works fine and landing one doesn’t.
Will let you know if it resolves the issue!
It does if for some reason the condition in the one automation passes where the other fails. It’s hard to tell because those conditions are looking for a specific time format. So it could be treating those numbers as HH:MM or MM:SS or as the first supplied number.
Still the same issue after changing time to HH:MM:SS
Hall downstairs works perfect, landing automation doesn’t work. Sensor is triggered fine in HA and mi home app.
Well, you are only using 1 timer for both. That will cause problems if one automation starts and uses the timer and then you try to trigger the other automation. Make a timer per automation and that might solve your problems.
so I’ve created separate timers for hall and landing now (even though it used to work perfectly with 1 timer)
and now … the landing automation works, but the hall one no longer works …
the code for the timers in my configuration.yaml is as follows:
timer:
timer_hall:
duration: ‘00:03:00’
timer_landing:
duration: ‘00:03:00’
gotta post your whole yaml for the automations