Is there a way to restart an add-on in HAAS from MSR?
-
-
I may have to try this at home. I'm going through Cloudflare to access my HA instance. Maybe it's interfering with what I'm trying to find.
-
That's the one.
-
ok, easier. Go to your homeassistant installation directory, look for an hidden .storage folder, and then core.config_entries.
entry_id
is the key you'll need. -
Revisiting. I never got this working. I think the issue is that the link provided talks about integrations, not add-ons.
I actually was able to create an automation through HAAS to do what I want to do through reactor. It looks like there is a addon_restart action in HAAS.
If this is an action, there should be in theory the same action in MSR.
@toggledbits, is there a way to call this action?
-
toggledbitsreplied to tamorgen on Oct 13, 2024, 7:02 PM last edited by toggledbits Oct 13, 2024, 3:03 PM
@tamorgen said in Is there a way to restart an add-on in HAAS from MSR?:
@toggledbits, is there a way to call this action?
Using Hass OS I assume? There's a command line tool you can use, described here. You would have to use that with a Shell action. If Reactor is running on the Hass OS system, that's probably easiest. Otherwise, you're going to have to write a script for the Shell action to execute that
ssh
's into your HassOS system to run their command line tool. -
@toggledbits said in Is there a way to restart an add-on in HAAS from MSR?:
Using Hass OS I assume?
Yes, I posted that on the first post of the thread.
I think I may have figured out how to do it. I just need to see if it works when the add-on goes unresponsive.
-
If it doesn't work, be sure to check the logs for how HASS responded (it will be logged). My guess that
data:
line in the service data is redundant, and it's going to complain about it, but let's see. -
@toggledbits said in Is there a way to restart an add-on in HAAS from MSR?:
If it doesn't work, be sure to check the logs for how HASS responded (it will be logged). My guess that
data:
line in the service data is redundant, and it's going to complain about it, but let's see.I thought it might be as well, but I figured I'd start with the way it was in the YAML code. If it doesn't work, I'll remove that line. The add-on hasn't gone unresponsive since I implemented this, so I can't say if it works or not.
-
-
-