Automations scripts are not being triggered

Lately, I have noticed that some of my automation scripts are not being triggered under the specified conditions but after debugging the code, I did not find anything wrong. Has anyone here noticed similar issues recently?

One hundred percent of my scripts were created via the UI and they run smoothly when triggered manually. If I hit “execute”, they run without problems.

Most of the problems I have noticed occur with triggers programmed to run at a specific time or those based on the change of state. For example, when I get close to my home, in theory, my garage door should open automatically, but this automation never worked. Another example is with my exterior lights, which should turn on automatically at sunset.

Is there a limit to how many active automation scripts we can have at a certain point in time? The CPU of my HA barely crosses the 20% mark and the CPU of my server is at 5%.

1 Like

This skips all conditions and triggers and goes straight to the action part.

The limit is your hardware, but shouldn’t matter unless you have thousands of automations.

Why do you assume that there is a general problem and then list an example of an automation that never worked anyway?

Show your code for the non-working automations.

Yea, I have 10s of thousands of lines of automation code and have never had a problem.

@hugo.raposo - posting some code will help us help you… I, too, think you’re looking in the wrong spot. Many of us have tons of complicated automations, so I doubt the number of automations is your problem. For example, when you get close to home, does the tracker you are using show you are close to home (and close enough to trigger the garage door)? How is the tracker defined? And then how is your automation defined?

1 Like