I updated to 2023.3.1
All of my automations stopped working (only showing the blue box that they got triggered)
Deactivated and activated all automations
Everything works again (for now), Thanks @rossk
Same here. All my automations with deConz show as triggered but action don’t run, then automations work after a disable and re-enable… Seems to have been an issue since around October like originally reported.
+1, same issue for me 
I have something similar that I have been tracking down the last week. Disable/Re-Enable gets things working again. Happened again this morning. I am wondering if it is something with the previous run never completing and so it won’t trigger another run. How many of you with this issue have the Automation “Mode” set to “single” (which is the default mode)?
If I can reproduce the issue more reliably, vs just over time, I may set it to “parallel” to see if that masks the issue, and no longer occurs, but that still isn’t a fix, since some of the things in my automation shouldn’t be used in parallel executions.
Ok, so I figured out my issue… may or may not be the same issue as others above, but wanted to share my result in hopes it may help someone else.
So I found that my automation was being triggered, but after the initial run it would never run again. (disabling and re-enabling the automation made it work again for 1 run). This was due to it being “stuck”, I could see this in the developer-tools for the state, and seeing that the automation was set to “current: 1”. So I started ripping down my automation, and eventually deleted every action, and it was still doing it. I then cloned it, thinking it was something externally tied to that automation, but the duplicated one did the same thing (super odd). I then looked at the YAML, vs the UI, and saw that there was still an action there, that didn’t show up in the UI. It was for an action below, that had been renamed, so it trying to run this action, and getting stuck because the entity that it was running the action against no longer existed. I deleted that action that was hidden to the UI, and only showed up in the raw yaml, and my problem was resolved. FWIW, this was the yaml action:
- wait_for_trigger:
- platform: state
entity_id:
- switch.av_on
to: "on"
1 Like
This sounds like one cause but it appears to me there might be more causes to similar behavior. I just realized that two out of my three sprinklers won’t turn on despite the automation being triggered. A simple restart of the home assistant solves it, all three sprinklers turn on and I do not have any remnants in the automation yaml. So still in the dark rabbit hole.
And what I found interesting is that the automation showed blue box signalling it was triggered but the “last triggered” attribute remained untouched. But, it could be related a bit to the one above described by @frozenmatt because the “last triggered” attribute was about 30mins ago, so I was successful to run the automation recently but I did touch the (turned on/off) device directly in the devices list, which could somehow intervene into the flow of the automation to make at least the timer stuck. So it still could be related to the logic of automation we simply do not observe properly (or which has remnants as in the previous case).
Thanks @Vahaldor. Indeed, and it’s rather odd.
For anyone wanting to visibly see what we mean because I wouldn’t quite believe it if someone explained…
Glad to see I’m not the only one! Sad to see there doesn’t appear to be an official bug fix yet. In the mean time, I setup a daily automation that stops/starts all my failing automations. The only automations I see failing are those triggered by an aqara zigbee button. This bug appears to happen after several days to a few weeks for me, so a daily reset should mostly resolve it. Hope to see an official fix soon.
Oh wow, I was already doubting my technical abilities…
I got the same issue (with a Tradfri switch and deConz running). The funny (or sad) thing is: It is only the switches ‘off short pressed’ that is not working, long press works and on works as well. And it’s only this particular trigger that is not working – the other switch in the automation works fine.
As for most others the ‘triggered’ banner appears on the trigger and even the dashboard shows that the light has been switched of for a few seconds.
I already tried to de- and reactivate the trigger/action/automation/device with no success. I even deleted the zigbee device in deConz and re-added it. Still not working…
I am really hoping to see a fix for this – if not I will have to visit my local IKEA store (and this always ends with a full cart 
)
I also have the same issue. My automation for a vacuum robot is triggered but nothing is happening. Manually triggering it or reactivating the automation helps. Before I saw this thread I thought it was the robot going into sleep mode but now with you guys having all the similar problems I see that it could be the automation.
Just found this thread when searching for my issue and I believe it’s the same thing:
I have a number of automations that do not fire when triggered by a sensor (switch, schedule, …). If I clone them and save the clone, that one works just fine. I hadn’t thought to try disable/enable as described in this thread but I imagine it’s resulting in a similar fix as clone.
The only thing I can think to add that is notable is that I’m quite new to things and am still only creating these in the UI. I’m not sure if this is an issue that effects things created through yaml files… anyone know?
I think I have this same issue. Have a number of Styrbar (IKEA) buttons connected to automations. However after some time it stops working. The buttons work and and events are triggered, but the automations are not started. I have not been able to consistantly reproduce the issue, it just “randomly” stops working.
As someone suggested in the thread I have tested to set the automations to parallel, but this does not help.
Currently what I do is to have a scheduled automation that turn the malfunctioning automations on and off every 15 mins. This is of course not a solution but a hack…
Same here. I have this issue happening for month (or years?) already. Sometimes automation will not run when triggered, even manually. Same as here in this video linked above (btw, thx fort that).
Ok i’m not mad.
Guys what’s happening and why is this going since 2 years with no solution?
I also have a simple automation that should turn on the privacy mode on a camera when an alarm panel is disabled. I can see that it has been triggered but not run, both because of the lack of action (privacy mode still disabled) and by the lack of trace of the automation itselt.
The automations with the trace did run, while the others did not
I can add some info (and maybe workaround) on that:
It happens when an automation is stuck in Attribute in “Current 1”. This is reset to “Current 0” once you disable and enable the automation.
It seems to happen only to automations that have been renamed. See this one that I once renamed from “bad_musik_aus” to “Bad aus”. The original name remains somewhere deep in the system.
As a possible workaround I renamed the existing automation, deativated and copied it. The copy I named like name of the one that got stuck. Until now it works but no long time approval yet.
Good luck!
Renaming an automation only changes the friendly name. It doesn’t change the entity_id. To do that, you’d have to go into the settings for the automation and rename it there.
1 Like
Maybe that’s the issue, non corresponding friendly and entity name?
In my case it happened after an update, i don’t remember if it was a camera and/or core one.
Anyway, the automation has never been renamed or something, it just started to skip some executions