Automations All Stopped Working

Configuration
1

So late last night I decided to work on getting encryption working with letsencrypt and while rebooting, I decided to go ahead and install the latest OSX update. When I restarted I noticed none of my automations work. There’s no errors in the log and all automations show as they load properly so it must have been something other than my config file. I tried using an older config backup where I know it was 100% working and same result.

Could it be something OS X messed up with Python or some other dependency?

I then tried uninstalling homeassistant and reinstalling and the problem continues. Any ideas what else I could check? It’s so frustrating to just one day lose all the hard work just short of reinstalling my entire OS X I don’t know what else to do.

2

We have little information to go on. Can you trigger your automations manually from the GUI?

3

No, they won’t trigger

4

Check if the state is set to “off”. If they are “off” you can set initial_state = true

Link

5

Change the Directory to your /home/homeassistant/.homeassistant directory.

Type “tail -f OZW_Log.txt”.

While you are looking at the output of that, click on the Automation to trigger it, to see if any zwave commands are being sent out…

6

Did you update home assistant in the process? All my automations stopped working in 0.45.

Pretty annoying.

7

I tried going back to 0.44.1 hoping maybe that was it but automations are still broken so there’s something else going on.

To add to the mystery, I added a new automation and it works. So maybe something in my yaml got messed up. But it doesn’t make sense that my yaml validates and there’s no errors in the log

@RitteT I tried your suggestion and it didn’t trigger. I have a feeling this will waste many hours for me in the next few days. I think I’m going to delete all my automations and add one at a time to see if I can get them working. I have about 50 so it’s not going to be fun.

Thanks for everyone’s help and suggestions!! I appreciate it.

8

So after downgrading to 44.1 most of my automations began working again. So it definitely seems like something changed in 0.45 that makes it unstable. Wonder if it’s the introduction of the automation maker?

9

I think so.

Did you move rename your current automation section to “automation old:”, as the docs say to do? I did that, and after rebooting numerous times and futzing with other stuff, creating a new automations file for the new stuff, trying to add one then removing it, some old automations suddenly work again.

10

I cleaned up my automations as it needed a good cleaning and everything works again. I think I will have to stay at 44.1 for awhile until the automations get fixed. It’s weird because they did all work for a bit on 45.0 but gradually started giving me problems which led me to believe I messed something up, but that wasn’t really the case.

11

When updating HA, naming conventions can change. Probably thats the case in one of your automations, and when you start HA it can not load the automation or the component.

One solution is to change to appdaemon. This needs a “little” rework of your automations, but if you manage then all your automations will be outside of HA and probably not affected by the upgrades

Or if your are not that into python coding then set the logger verbosity to info restart HA, and then search for the log file with finder (mine is named home-assistant.log) and look for errors.
Eg.:

configuration.yaml

logger:
  default: info

home-assistant.log
2017-05-27 18:01:19 ERROR (Thread-5) [homeassistant.components.media_player.mpd] Unable to connect to MPD

So this means that MPD is not running, so no automations regarding MPD will work. Naturally.

good luck
tom

12

So I was having the same problems mentioned by by @Jer78. The update to 0.45 went smooth for the first week and then my automations slowly stopped working. I downgraded to 44.1 and everything was fixed. But then today I updated to 0.46 to see if the problem had been fixed. Unfortunately I was getting the same problems as 0.45. After taking the following steps I was bale to get my automations working on 0.46.

  1. Remove the automation old: !include automations_old.yaml.
  2. Add automation: !include automations.yaml to get the automation editor.
  3. Restart Home Assistant ( you should now have no automations in Home Assistant)
  4. Add your old automations back to Home Assistant automation old: !include automations_old.yaml.
  5. The automations should now be loaded into Home Assistant and working properly.

Hope this helps someone upgrade to the newer version that is still stuck at 0.44.

2 Likes
13

I had the same issue after some reboots, and found out that somehow they where turned off.

14

This worked for me as well. Thanks @333ryan18