My setup:
Home Assistant core 108 running on an Openmediavault 4 NAS via OMV’s Docker addon.
I have an Aeotech Zwave stick and a Schlage Connect Zwave lock. I also have an unsed Pi 3b. Has anyone used a Pi as a remote zwave controller only that connects easily to a running Home Assistant instance? I would really like to get my door lock connected to HomeAssistant.
I had considered running Hass.io on the Pi with the Zwave Addon alone and “slaving” it to my primary HomeAssistant instance, but from my understanding of Hass as it stands now, it no longer supports multiple Home Assistant instances running as Master & Slave configurations.
Any ideas?
All you need is this custom component on the “master” node, connecting to the Z-Wave node.
This is exactly what I do, it works pretty well.
OK.
So I burn a Hass.io SD card, spin up a Hass instance, set it to different port: eg:8124, like the config example.
Any quirks to be aware of during initial boot/set-up stage…ie. What name should I set it up under (same as Master system, different?), do I need duplicate users, etc?
You can use the same port, no need to give yourself trouble by having to remember to use a different port. I’d give it a different hostname name from homeassistant, but otherwise it doesn’t matter.
Yeah, yeah, yeah…it’ll have a different IP anyway, so default port is fine…OK I got ya.
I would assume that I can turn off Discovery on the slave and just hard-config the few things I want running on the slave (Zwave support and my Schlage lock) since everything else runs through HA Core on my Master.
Yup. Just configure it to pass the entities you want, and the services. This is my setup to give you a starting point.
I pass through sun.sun and sensor.date_time so that I can confirm that they’re still in sync. I found a bug in the early days where reloading automations on the Z-Wave install would cause the connection to fail. I think that’s fixed, but I’ve never changed the settings.