Any automations not triggered

Configuration
1

Hello everybody,
it’s the first experience for me with Rasberry Pi and Home Assistant.
I was previously operating my automations between Smart Things, Google Home and eWeLink and despite no so many options were available there, except when the WiFi was disconnecting, every system was working pretty well.
With Home Assistant on a Rasberry Pi 4 I’m experiencing “some” issue that I’m unable to understand since it is my first time using it.
Maybe I’m wrong but … Yes, I admit it, when I initially installed the Rasberry with SD card and its software and then Home Assistant, the day after I was trying to enter again my account, but … user ID or password was not recognised. I tryed thousand of times but nothing!
For this reason I had to do a reset formatting the SD card and installing again Rasberry SW and Home Assistant with new credentials. Fortunately at that time I didn’t create any automation yet, but now that I created a lot of it thinking that everything would have being working … I realise that NOTHING is working.
Is there anybody so nice to suggest me how/what to check in my configurations (maybe) if everything is setted-up well or not?

Thank you very much in advance!

2

Hi, starting up can be hard, but it is rewarding once you get the hang of it. Step one is to get backups working and syncing that off the pi to somewhere else. Better safe than sorry.

Then, everything at once is hard to tackle. Start with posting one automation here, with any automation traces of the time it was supposed to work.

3

@Edwin_D offers sound advice and posting the an example of your Automation code that isn’t working will help.

We will need a bit more information to assist you

  1. What is working or simply explain what you see?
  2. Are you logged in and have a dashboard?
4

Another thing: check the logs. It might be that something is preventing the automations from loading.

5

Hello
Welcom to the HA Forum!

If you haven’t found it already, some of us have contributed to the Home Assistant Cookbook.
There may be some stuff in that that can help you out.

6

Thanks to all of you for your answers,
I started to insert a lot of automations to take over my previous “assistants” Smart Things etc., but I see that something doesn’t work with Home Assistant.
In order to let the automation work I have to execut it manually … but in real life of course it doesn’t make sense.

This is the simpler automation I tryed and … of course it doesn’t start:

alias: prova
description: ""
triggers:
  - type: turned_off
    device_id: ac31ec94c5b79d510a7c947668a6de35
    entity_id: ec1f158ced38243afa548776abf60920
    domain: light
    trigger: device
conditions:
  - condition: time
    after: "10:05:00"
actions:
  - type: turn_on
    device_id: ac31ec94c5b79d510a7c947668a6de35
    entity_id: ec1f158ced38243afa548776abf60920
    domain: light
  - delay:
      hours: 0
      minutes: 0
      seconds: 30
      milliseconds: 0
  - type: turn_off
    device_id: ac31ec94c5b79d510a7c947668a6de35
    entity_id: ec1f158ced38243afa548776abf60920
    domain: light
mode: single

image
image442×553 18.9 KB

… so in the end at 10:05 nor at 10:06 the light didn’t switch on …

About logs … yes, I see a lot of lines there, but nothing for example regarding the trial above … maybe it was too easy for the system to be considered :sweat_smile:

What can I try?

I was also considering that (maybe) the rule from my router to switch to different IP’s users within the home network on itself whenever considered necessary (in other words the system doesn’t work based on ‘static’ IP’s) could be a (or the) problem.
From the other side I’m warried that if I remove this setting (suggested by TP-LINK) on my router I risk to lose the connection with some device.

One of the log errors I see maybe connected to some automation is this:

Registratore: pydaikin.daikin_base
Fonte: components/daikin/coordinator.py:36
Prima occorrenza: 11 aprile 2025 alle ore 00:51:09 (4912 occorrenze)
Ultimo accesso: 10:43:42

Exception in TaskGroup: Cannot connect to host 192.168.1.201:80 ssl:default [Connect call failed (‘192.168.1.201’, 80)]
Exception in TaskGroup: Cannot connect to host 192.168.1.105:80 ssl:default [Connect call failed (‘192.168.1.105’, 80)]
Exception in TaskGroup: Connection timeout to host http://192.168.1.210/aircon/get_sensor_info
Exception in TaskGroup: Cannot connect to host 192.168.1.210:80 ssl:default [Connect call failed (‘192.168.1.210’, 80)]
Exception in TaskGroup: Connection timeout to host http://192.168.1.215/aircon/get_control_info

Briefly some automation contains conditions like a temperature value from a room, coming from the air conditioner temperature sensor in that room, in order to start (or not) another heating system.
Now, the air conditioner is always on stby by night and well connected to the wifi so it can provide the temperature data, but then why Home Assistant doesn’t complete the automation?
By the way, considering I’m new on all of this system I can even be wrong and misunderstanding logs and their meanings.

I’m a bit discouraged on this stuff :sleepy:

7

You have confused triggers with conditions. That automation will only work if you switch off the light after 10:05. It will not switch on the light at 10:05 automatically because that’s not what you told it to do.

I suggest you read the docs on automations & get some basic understanding of the difference between triggers, conditions & actions, otherwise you’ll be discouraged.