Help Determining Why Automation is Not Triggering

Configuration
,
1

I have created an automation that should trigger when the “Last Boot” entity from the ASUSWRT integration is Unavailable or Unknown for 5 minutes, but is does not.

Below is the automation:

alias: ASUS Integration Reload
description: ""
triggers:
  - trigger: state
    entity_id:
      - sensor.192_168_1_1_last_boot
    to:
      - unavailable
      - unknown
    for:
      hours: 0
      minutes: 5
      seconds: 0
conditions: []
actions:
  - action: homeassistant.reload_config_entry
    data: {}
    target:
      device_id: 35b7a8532028ebfa9cad26453f0e3d20
mode: single

The Last Boot sensor had a status of Unavailable for greater than 5 minutes earlier today, but the automation did not trigger, why?

image
image1638×227 21.3 KB

2

Can you verify that it did not trigger? Is there a trace?

3

Yes, I verified that it had never triggered, it has no traces.

4

Can you share the logbook for that time period, there’s nothing wrong with your yaml so it should trigger. Only explanation would be that the state is not unavailable.

5

This?

image
image408×709 31.8 KB

6

That only shows 3 seconds of unavailable

image
image360×103 8.72 KB

7

That does not match the history which shows Unavailable for about 30 minutes:

image
image1093×269 23.2 KB

The logbook has nothing for this time period.

8

Logbook holds all state changes, this is a separate table than history. You should look in your logs and see which one is wrong.

9

The logbook is wrong.

The integration and all of it’s entities were unavailable from 9:46 - 10:12 am. The integration failed to load after a reboot.

How do I determine why the logbook did not pick up these state changes?

10

That would be in your logs, typically with an error.

11

Found this is the logs, but still unsure why the Unavailable state was recorded in the History and not the Logbook. How do I catch this situation and use it to trigger my automation?

2026-07-31 09:46:30.240 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 192.168.1.1 for asuswrt
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 798, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/asuswrt/__init__.py", line 18, in async_setup_entry
    await router.setup()
  File "/usr/src/homeassistant/homeassistant/components/asuswrt/router.py", line 270, in setup
    await self.update_devices()
  File "/usr/src/homeassistant/homeassistant/components/asuswrt/router.py", line 288, in update_devices
    wrt_devices = await self._api.async_get_connected_devices()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/asuswrt/bridge.py", line 460, in async_get_connected_devices
    for mac, dev in api_devices.items()
                    ^^^^^^^^^^^^^^^^^
12

Well that would be why, the system restarted. The initial trigger was never registered to start waiting the 5 minutes.

FYI, I know the system restarted because of the log lines that you removed from your previous message. Those log lines mentioning custom integrations only appear at startup.

image
image618×401 28.9 KB

13

I restarted the system while the Last Boot entity was still available. After the restart the ASUSWRT integration failed to load and the Last Boot entity became unavailable until I manually restarted it.

I restarted the system at 9:45 am and the Last Boot entity became Unavailable at 9:46:43 am after the system restarted.

14

Right, so automations need a state change in order to trigger. During a restart, triggers can only be captured if the automation engine is running. The integration failed before the automation was running (and before recorder was able to record it).

15

I get it now! Thanks for the help and sorry for being slow to catch on!

16

It’s all good, this is complicated stuff

17

I created this new automation:

alias: ASUS Integration Reload
description: ""
triggers:
  - trigger: homeassistant
    event: start
conditions: []
actions:
  - delay:
      hours: 0
      minutes: 2
      seconds: 0
      milliseconds: 0
  - if:
      - condition: state
        entity_id: sensor.192_168_1_1_last_boot
        state:
          - unavailable
          - unknown
    then:
      - action: homeassistant.reload_config_entry
        data: {}
        target:
          device_id: 35b7a8532028ebfa9cad26453f0e3d20
mode: single
18

That will only catch the case where your router is offline after a Home Assistant restart. If you also want to catch the issue when home assistant is running add your original trigger too.

triggers:
  - trigger: homeassistant
    event: start
  - trigger: state
    entity_id:
      - sensor.192_168_1_1_last_boot
    to:
      - unavailable
      - unknown
    for:
      hours: 0
      minutes: 3 # (there is the 2 minute delay in your actions giving 5 minutes total).
      seconds: 0