Hey gang,
After the new year, I’m planning on moving my hass.io installation from a pi to a pc using these directions:
https://drive.google.com/drive/folders/1oKhnQ1rz-Yd5HheA8rNk5YNq8e67-5Kh?fbclid=IwAR2hSh-HFqK2tWDgcnh9AqCVnSi_rWP0Aoho6CqFHpoLc9NujKN5GLklP3Q
My question is, can I leave home assistant on the original pi with the z-wave stick, disable automatons, scripts, etc and utilize the pi as a z-wave hub or is this just nuts?
Thanks for any advice.
You can use the remote instance custom component (on hacs) to make your Zwave one a ‘slave’ and report/control it from the master I believe.
3 Likes
Thank you. I will give this a look.
1 Like
Or you could do USB-over-ip like this guy here RPi as Z-Wave/ZigBee-over-IP server for Hass
1 Like
Tinkerer
(aka DubhAd on GitHub)
December 12, 2019, 9:31am
5
I’ll second this one. I use it for exactly this, and it works rather well.
2 Likes
Thank you! I’ll take a look at it.
I looked at the documentation and it looks very like a very good option.
Do you see any additional latency or other oddities? How well does this scenario recover from power outages - does the order of startup make any difference?
Thank you for your advice!
Tinkerer
(aka DubhAd on GitHub)
December 13, 2019, 9:31am
8
Based on my experiences so far…
There is some increased latency, but generally not terrible
Yes, it doesn’t handle reconnection as smoothly as I’d like, so you may have to ensure that the primary instance starts after the secondary
Thank you! This is very helpful.
Last question, if you were to do it again, would you go this route or spend the resources to go another way?
Tinkerer
(aka DubhAd on GitHub)
December 13, 2019, 4:13pm
10
Right now, this is the simplest way of running a remote Z-Wave instance, other than Zwave2MQTT.
However, once the OZW 1.6 integration drops, you’ll be able to do this natively, using MQTT.
1 Like
Awesome! That’s the best news I’ve heard today!
Thanks again for the feedback. This has been very helpful!