Trigger automation when Hassio addon starts/ stops

[Kanishkaz (Kaz)]

Hi,

Is there a way to trigger an automation when a Hassio addon stops or starts?

I was looking for a way to check the status of installed/ running Hassio addons but couldn’t find any info or examples.

Cheers.

[Kanishkaz (Kaz)]

Found an answer on the Discord channel.

You can use the Homeassistant Rest API to check the status of a running addon.

Example:

http://hassio:8123/api/hassio/addons/addon_slug_name/info

Then you can simply extract the state attribute value from the result.

Hope this helps someone.

[silvrr]

@Kanishkaz were you able to get this into a sensor on the front end? If so can you share your config?

[Kanishkaz (Kaz)]

I ended up moving NodeRed into a separate docker container outside of Hassio, so I’m not using the sensor anymore.

But, this is what I had in my config at the time:

- platform: command_line
  name: Node-Red Status
  command: !secret node_sensor
  value_template: '{{ value_json.data.state }}'

Unfortunately, I don’t have a copy of the secret. But I believe it’s just the following url with my credentials.

http://hassio:8123/api/hassio/addons/addon_slug_name/info

You should be able to get the slug name by running the command “hassio su info” in ssh.

Hope that helps.

[DasLetzteEinhorn]

Hey there, does this method still work? I can’t get it to work…

edit: nevermind, got it to work. If anyone reading this in the future is still interested, i can clean up my config files an share them

[tomtom17 (Thomas Roche)]

Hi,
Could you share your config ?
I don’t get it to work.
THX

[Kanishkaz (Kaz)]

Hi,

Unfortunately I don’t use this automation anymore, so I don’t have it in my config.

But I think you can find the slug name by using the following command in the terminal:

ha addons

You can still use the REST API call I have included in my previous example. You just need to make sure you also pass in an Authorization header with a token.

Here’s another example I found from a different user.

Badges for addon service status

Here is how I do it. Create a sensor for the add-ons: Optionally, you can create switches to control the add-ons: https://github.com/SilvrrGIT/HomeAssistant/blob/master/switches.yaml#L124 Finally, a notification if an add-on stops

[tomtom17 (Thomas Roche)]

Thanks,
I’ll try this

[SVNKoch (Sven Koch)]

For anyone stumbling across this like me:
Nowadays there is a binary sensor which can tell you if an addon is running. You just have to enable it.
Go to Settings > Devices > Addon in question > Sensors > Running > Advanced Options > Enable.

Using the not_running trigger you can trigger on an addon stopping.

Feature was added here:

Add binary sensor to add-ons to show if they are running

[cyberscout]

I’m new to Home Assistant and came across this thread when trying to find a trigger for an addon stopping. I didn’t the find feature to enable the binary sensor for that purpose. There is only a watchdog feature but no sensor that comes with it.

I also didn’t find this:

@SVNKoch

Settings > Devices > Addon in question > Sensors > Running > Advanced Options > Enable

Has this feature been taken out of Home Assistant again or am I just not seeing where I can enable it? Under “entities” there is only a sensor for an addon update.

[Fettkeewl]

Hey, instructions above a bit unclear

Go to Settings > Devices & services > Devices > filter devices by supervisor, enter “addon device” from supervisor > enable running sensor

[quizzical]

Thanks a lot! I was struggling to find this feature.

[colinnz (Colin)]

Just seen this. Thanks for taking the time to document this.

[thargy (Craig Dean)]

Sadly this no longer works, at least for ESPHome.

The esphome_running entity remains in the running state even when stopping the addon, never mind when restarting it