Event homeassistant_started doesn't work

Configuration
1

I need a trigger for an automation that fires when Home Assistant (HA) has fully started.

According to the documentation, there’s an event called homeassistant_started for this purpose.

Unfortunately, this event seems to be incorrect or isn’t triggering.

I have this test automation:

  • id: ‘test_ha_started_event’
    alias: “TEST: HA Started Event Listener”
    mode: single
    trigger:
    • platform: event
      event_type: homeassistant_started
      condition:
      action:
    • service: persistent_notification.create
      data:
      title: “Home Assistant started”
      message: “homeassistant_started Event received.”

Can someone tell me where the error lies?
Thanks

2

Use the Home Assistant Trigger, which can be found in Automation Trigger - Home Assistant … as recommended in the Events docs:

image
image739×341 26.6 KB

3

I read this, but it seems that Home Assistant trigger only supports event start and event shutdown.
How is the event for “HA is started”?

automation:
triggers:
- trigger: homeassistant
# Event can also be ‘shutdown’
event: start

Remember, I need a trigger when HA is started completely.

4

Use manual event as trigger…

3001
30011080×2546 181 KB

5

I tried this Test-Automation, but it seems that no event was fired:

- id: 'test_ha_started_event'
  alias: "TEST: HA Started Event Listener"
  mode: single
  trigger:
    - platform: event
      event_type: homeassistant_started
  condition: []
  action:
    - service: persistent_notification.create
      data:
        title: "Home Assistant started"
        message: "homeassistant_started Event received."
6

I’m pretty sure this works. I use it in a current automation.

trigger:
  - platform: homeassistant
    event: start
7

It doesn’t work when used in automations.

I encountered the same issue in 2024 and reported it. Turns out that it won’t work in an automation (but will work in a Trigger-based Template Sensor).

2 Likes
8

Replace

trigger:
    - platform: event
      event_type: homeassistant_started
  condition: []

with

triggers:
  - trigger: homeassistant
    event: start
conditions: []
9

According to this:

especially see screenshot above from Didgeridrew

there are 2 events:
homeassistant_start and homeassistant_started

according to this, homeassistant_start is fired the HA starts, and homeassistant_started should be fired when HA is started completely.

I need the event when HA is started completely in an automation.

10

Did you try this syntax?

triggers:
  - trigger: homeassistant
    event: started
conditions: []
11

yes, for this trigger is start and shutdown the only allowed event.

12

That’s what I had insinuated in my first answer with ‘start’.

Can you elaborate a little bit why start is not working for you?

13

Because, according the description here

event “start” is firering at the beginning of the start from HA, and “started” when finished starting.

14

The doc seems outdated. Is anything not working when you use ‘start’?

For the event ton fire HA needs to be operational - and is when the event gets triggered.

15

Please use code tags in your posts.
I log my Home Assistant starts with an automation. Maybe this might help you:

- id: '1729005744617'
  alias: Log Home Assistant Start
  description: Logs every HA start to www/home_assistant_log.txt
  triggers:
  - trigger: homeassistant
    event: start
  conditions: []
  actions:
  - action: shell_command.log_home_assistant_start
    metadata: {}
    data: {}
  mode: single
16

I can confirm that the ‘start’ doesn’t trigger until HA is completely up and operational. I have an automation to send me a notification on shutdown and start. It’s not uncommon that I’m watching it startup and it always triggers right when it finishes starting.

17

After testing with Trigger-based template sensors…

Sensor Config 
template:
  - trigger:
      - trigger: homeassistant
        event: start
    sensor:
      name: HA Trigger Start
      state: "{{ now() }}"
  - triggers:
      - trigger: event
        event_type: homeassistant_started
    sensor:
      name: Started Event
      state: "{{ now() }}"
  - triggers:
      - trigger: event
        event_type: homeassistant_start
    sensor:
      name: Start Event
      state: "{{ now() }}"

… the Home Assistant trigger is consistently posting earlier values for now() than using the Event trigger with the homeassistant_started event type. On my system, running 2026.2.0b3 which seems slower to start than normal, the difference was about 15 secs.

@blacksun

If you really need a trigger based on the homeassistant_started event, and the Home Assistant trigger will not work for your needs, your best bet currently is to set up a Trigger based template sensor using the Event trigger, then fire your automation of that sensor’s state change.

Another option would be to use the config above to run your own tests, then trigger your automation using the Home Assistant trigger but add a delay at the start of the automation.

Just keep in mind that even the homeassistant_started event isn’t a guarantee that all custom integrations are fully up and running or have completed all their required handshakes/data transfer if they are cloud-dependent.

18

Lacking alternatives, I’ve been using the Home Assistant trigger with the start event.

In my tests so far, the trigger only fired once Home Assistant was fully loaded.
Since the documentation says otherwise, I’m unsure if this will remain the case.

19

I’ve been using it for years and it’s always triggered AFTER startup finished.

20

I use it to load an input_select from a folder sensor (file list) at startup and never had a problem