Trigger restart of Z-Wave JS to MQTT add on

Third party integrations Node-RED
,
1

Hi,

My setup on a RPi 3B+
Home Assistant OS 7.0, core-2021.12.3, Z-Wave JS to MQTT (0.32.1) and node-red ( 10.2.0 )

I have an issue where z-wave published states are lost since Z-Wave JS to MQTT add-on starts up before HA core. It also happens when HA core is restarted but not followed by a Z-wave add-on restart.

I’m really happy with the node-red and Z-Wave addon and I’ve configured the Z-Wave add-on to Publish Node Details, it works really great if the Z-wave add-on is restarted after everything else is up.

What I’m looking for is a way to have node-red to listen to events and trigger a add-on restart based on a HA reboot with a delay or a Core reload. This way I could remove the manual step I have to remember right now.

I have multiple HA instances with their own Z-Wave to MQTT add-on and one central Lovelace-UI configured with mqtt entities. Perhaps node-red could listen to events from a second HA instance and restart the add-on on the instance as well.

Would this be possible to achieve or is there any better way to do it?
Retained messages is not a option for me as all lights, dimmers etc, doesn’t have the correct retained message for this to work.

Thanks in advance,
Roger

2

Use the stdin service:

service: hassio.addon_stdin
data:
  addon: core_ssh (make sure this add-on is installed)
  input: "ha addons restart a0d7b954_zwavejs2mqtt"

Use ha addons | grep zwavejs2mqtt in the ssh addon to check the a0d7b954 is the same for you.

3

Thanks Andrew,

If I would need to call this service from node-red could that be done? I read this as it would be an action from within hassio, right?