I have noticed the same thing today with completely unrelated automations.
I to have the same problem. Automations with a wait loop get cancelled because of this issue!
I’m getting this too. What power supply are you guys using? My Rpi3 officially needs a 2.5a charger and I’m just using an old iPhone 5v2A charger. My RPi Power Status Integration displays ‘Problem’ and I wonder whether this has anything to do with it. Will buy a 5v3A capable QC charger later today and update you guys.
(personally, this hasn’t really caused any issues for me because I’ve implemented a 2second delay in all my triggers, and these phantom turning on/off problems only last fractions of a second)
update: okay, so after getting a better power adapter & cable, my RPI Status is now OK, but the ‘became unavailable’ still continues occasionally, so it’s not a power / under voltage issue. Perhaps it’s a network thing? mine is wired ethernet.
Came to the forums today to research and post this issue. Yes I am using an automation, but the issue also presents if on the device page I toggle to turn on. If I toggle or trigger the device to turn on it turns of instantly. The device in question is a ZEN30, I’m trying to look through the logs to see when it stopped functioning. It’s been working fine for a year or more.
Anybody has ideas on how to debug or what information to provide for debugging?
Same problem here.
An automation became unavailable in the middle of actions execution so did not complete.
Having a similar issue here. First time user trying to set up a light=on based on calendar event triggers. My Meeting Start automation keeps flipping to unavailable every time I update it, which I do every time it fails and I try to test again. However, my Meeting End automation that toggles the light OFF has had 0 issues.
Correction: My Meeting End automation is doing the same. Very Frustrating.
EDIT: Turns out the 15 minute refresh interval was the main source of my confusion. You may see the calendar refreshed in the UI, but the entity state is stuck on that interval. I don’t know that the “Became unavailable” log is really any harm.
Are people still seeing this issue? I have automations that run actions X minutes after sunset and they are constantly being cancelled. When I look at the logs I see all automations became unavailable and then turned on again but that’s enough to cancel automations in progress.
First post in this community, but I tink I have found the reason.
I have the same thing. Multiple log entries with turned ON and unavailable.
It appears that every time you save ANY automation setup, they all go unavailable and instantly turnes ON again.
Very easy to replicate. Go into any automation. Even a disabled one. Change a name or something, and hit save. Go back to log, and you will see an entry on automations going unavailable and turning ON within the same second.
Edit: It’s supposed to work this way. Whenever you save an automation, the automation YAML file needs to be run again.
1 Like
First of all thanks for this hint. now I at least dont need to debug by my self for half day to figure out this 
Does anyone “more experienced” know any way how and if the re-load can be prevented ? I mean, I definitely understand that if I adjust automation A ,then the automation A needs to be reloaded / restarted.
However to reload (therefore restart) all the automation is for my case inconvenient - long story short from time to time i need to disable one automation + i have always running automation for my heater to turn on in the night, if some condition was fulfilled in the evening before.
If there is not a way now to prevent complete reload, is there a possibility to vote for a feature request? (yes I understand that somebody needs to design / code it in their free time basically, but maybe if we get enough attention…who knows )
PS: I know there have been lately some updates into automation - does anyone know if i can “manually” tell to automation that it is already in, for example , step 3 of 5? so it continues only with the steps 4,5 and does not need to first wait for 1,2 and 3 to be true.
Thanks for answers anybody
Not possible. The only way automations get updated without an HA restart is by calling the automation.reload service (bottom of the page). That’s what actually happens if you save an automation to make your changes take effect, it calls that service. Same if you click “automations” in this page.
This is why if you search the forum there are many, many, many posts where the “more experienced” users tell people why they need to avoid long delay steps, wait steps or for times in triggers/conditions. If you save any automation in the UI all currently running automations will be simply stopped and any waiting in any of those steps will be killed without completing.
The only thing you can do is vote for this post (or this one, or this one, or this one, …)
One of those posts on the WTH for this is mine. I should mention that I personally try to avoid any (long) delays in my automations (once I realized how HA handled automations). I think it’s good practice to be more resilient, but also that HA shouldn’t reload all automations the way it does now.
I had this issue and wound up here, I then determined my target device to turn off was no longer valid, i must have deleted it then re-added it with a new name. When I updated the automation with the new valid device name, the autmation became valid.
1 Like
I had same issue. Some of my automations after update to version 2023.11.0 have become unavailable. In my case I found solution. I opened automation which was wrong. I modified something easy and tried to save. When I pushed save button, for few seconds error message appeared where was described what is wrong. In my case error message wrote me that some id is missing. I found in my automation that some devices have disappeared. I have added missing devices back and everything is now ok. I don’t know why it happened. Maybe something has changed in the HA update, but in any case, all the automation is right now.
4 Likes
Same thing happened to me on automation with multiple devices few entities just blanked out, re added them and all works finer
Automations using device_ids report as unavailable if they depend on missing devices. You can avoid this by using states and entity ids instead.
1 Like
I got this issue after hitting the upgrade button for 2023.11.
I suspect a couple of my shelly devices got upset by the behaviour of my wifi router and dropped off, so all automations that were referring to their device id’s became unavailable.
Switching to entity_id’s solved the issue for me.
2 Likes
I’ve lost several automations after one of the last updates… Cannot tell exactly which one but definitely need to get back to a previous configuration/backup since many of them are just sensors defined in configuration.yaml and depending on inputs to the RFbridge
1 Like
I found MY problem. I had a duplicate device in my list. It was listed but had no action, etc. linked to it. I deleted, saved and IMMEDIATELY I was good to go!
I had the same problem, 2 automations (Sunrise and Sunset) and 2 scripts were disabled. For me I think it happened because I had some issues with a device.
Reading trough some posts ! decided to rename the automation by just adding the number 2 at the end. Saved it and it worked again.
After that I removed the 2 in the name, saved it again and the automations and scripts kept working.
I had a similar issue with the recent update 2023.11.2.
All of my Shelly 2.5 devices’ automations suddenly became unavailable.
I discovered that the device IDs in the automations were no longer valid, resulting in a message error stating “Unknown device ‘382baec20779020af156586832d89cee’”. To resolve this problem, I had to reselect again the appropriate Shelly device in the automation settings.