Hi
Have you tried making the windows client run again? Any luck?
First of all, nice guide and idea.
Difficult to judge if usbip or the ser2net method is better to be used.
I am reading a lot and planning to have hassio instance dedicated to the wireless receiver (USB dongle)
So my setup will be similar to others.
1.) Hassio running docker on a VM installed on proxmox.
2.) Zwave dongle on a RPi in a more central place of the house.
Yesterday I was almost done with my research about usbip and ser2net and the decision has been made to use usbip.
But then I was reading some more MQTT stuff and found that Zwave to MQTT could be an alternative.
So far I understand the following us needed to use dedicated.
1.) Hassio installed with the standard MQTT in my case on Proxmox
2.) Zwave to Mqtt installed on the RPi with the zwave dongle plugged in.
As far a I understood the inclusion will be done on the RPi and pushed to Hassio automatically.
With MQTT the devices can be read and controlled.
Any thoughts about this idea?
Are you aware of any limitations?
BR Christian
Zwave2Mqtt is what I switched to. A bit more hassle to set every device up (I have several templates for my lock) but by far more stable.
Great to hear you are using it already.
But once again, this means you have Mosquitto as Broker on Hassio and Zwave2Mqtt on your RPi?
Does it mean the inclusion is done on the RPi?
What exactly is more hassle to set every device up`? Is it about the setup in Zwave2MQTT or the way the messages are sent to hass.io?
Highly appreciated if you could get me onboarded 
thx
Chris
Yes. I use the MQTT Community Add-on on my Hass.io machine. and Zwave2Mqtt on my RPi which is by my front door (also a MagicMirror2).
Yes, Zwave2Mqtt has a web interface you use to do all the setup for each device.
After you set each device up on the web interface, HA should pick most of them up with MQTT Discovery, but you may have to manually add/customize some of the MQTT entries for each device in your Hass instance, including any extra attributes you want to track (for me, lock type, user code used, etc.) ā all very doable, just not as quick and clean as adding a Z-wave device directly in HA.
Sounds promising;)
I will give this Setup a shot and hope that I am able to handle the mqtt config to hass.io.
Many thanks for your reply.
Last but not least, what do you use for your door to lock/unlock?
I have already a motor build into my doors(24Volt) and so far I plan to use this one:
https://wiki.fhem.de/wiki/DoorPi_und_FHEM
This is a doorpi with some extras originally for FHEM but at the end it would fit for hass.io
AMy main goal is to open my doors by nfc/RFID e.g. a ring on your finger. 
BR Christian
For all those planning to have a similiar setup, āzackā has documented the way towards in a nice manner.
I recently updated code for a custom component that had previously used with a local USB device. While troubleshooting the socat connection I realized that I could just simply directly configure a serial-over-ip device in python.
There are a few of these threads, and it really feels like the right solution would to be add in support directly into the zwave components. HA uses a fork of Python-Openzwave, which is actually a wrapper for a C++ library. With that in mind, it might be a bit of a push to actually a remote serial port working directly. Not being well versed in C++ I havenāt jumped down that rabbit hole.
Failing that, a device-proxy could also be a compelling feature. There are many use cases for remote placements of devices attached to raspis or other hostnodes.
P.S. My solution to this for zwave in HA is simple enough, Iāve added a PostStart command to my kubernetes deployment which just starts socat. Iāll wrap it with a watcher scrip mounted in via a ConfigMap soon enough.
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: homeassistant
labels:
app: homeassistant
spec:
replicas: 1
serviceName: homeassistant
selector:
matchLabels:
app: homeassistant
template:
metadata:
labels:
app: homeassistant
spec:
containers:
- name: homeassistant
image: homeassistant/home-assistant:latest
lifecycle:
postStart:
exec:
command: ["sh", "-c", "socat pty,link=/dev/ttyACM0,raw,user=0,group=0,mode=777 tcp:pi-1.example.com:3333 &"]
env:
- name: "TZ"
value: "America/New_York"
...
You can also just put hassio/ha on the zigbee/zwave pi and connect them via āhome assistant remoteā
All devices appear in the master instance automatically and can be used Like local devices.
Iāve been using this setup for a couple of months now and it works great.
Iām trying this approach. So far the devices are not showing up in the master instance. It isnāt a communication problem because sensors do show up. Can you share your config?
Iām looking at setting this up soon, and read in the Github readme that if the master doesnāt have any of the device type added that youāre trying to pull over form the slave, then youāll need to add the blank domain to your config. So if youāre slave instance has switches, but the master doesnāt, youāll still need to add switch: without any switches to your configuration.yaml. hope that helps.
Another option Iāve seen, and am debating about using is the usbip linux utility. It passes usb devices from host to client via IP. Iām not sure which would be more reliable.
Thanks I noted that but it wasnāt the issue. In retrospect it may have been that I didnāt do something with ZHA on the VM side.
Iām now using USBIP with my Home Assistant Supervised on a generic Linux host (HASS in Hyper-V) setup. It works! However:
The service was not initializing correctly at reboot on the home assistant side. My first thought was that the issues was it was running the service run before network connections have been established. network-online.target didnāt work but
After=hassio-supervisor.service
Wants=hassio-supervisor.service
Update Not that reliable actually, not sure why this doesnāt always work at startup
Hi my Home Assistant is installed on my ESXI using the VMDK virtual appliance, how do I install āsocatā if I make a putty I only have the Home Assistant terminal.
But, when you restart HA from the interface itself only the docker container for homeassistant restarts and not the supervisor service, right? So, socat will not restart when you use this approach and restart from the webinterface, only if you restart supervisor as well?
Assuming you use socat the way I use usbip, yes, correct.
Fortunately I donāt lose wifi connection to my PI ever so I donāt need to do this.
Unfortunately the windows 10 hyper-v host I have Homeassistant on force restarts itself every so often.
So for the last few months Iāve been successfully running home-assistant on x86 machine that was remotely connecting to a z-wave usb stick on a RPi, orchestrated on Kubernetes. (however, if you just want the socat commands, you can just extract it from the kubernetes manifests below)
The new ozw-zwave-mqtt support thatās being added will obsolete this (and Iām so excited about that!), but this recipe may still have use for folks who may want to do this for zigbee or any type of other serial interface on a remote machine.
My configuration:
- Kubernetes cluster (Iām using k3s+metallb and nfs server for persistent storage).
- VMs on ESXi running as my normal x86 workers (home-assistant will get scheduled on this)
- RPi node (with node taints
--node-taint rpi=true:NoSchedule --node-taint rpi=true:NoExecute) -
Aeotec Z-Stick 5attached to the RPi node
I have three kubernetes deployments
-
zwave-server(this will expose the Z-Stick as a tcp service) -
zwave-client(this will connect to zwave-server and expose it as a pts device on the k8s node) -
home-assistant(this will mount the /dev/pts so it can access to the client device)
Iām using nodeSelector to place zwave-server on the RPi, and then colocate zwave-client and home-assistant on the same node. (The reason the zwave-client and home-assistant are two deployments is so that I can run the zwave-client in priviledged mode, and keep home-assistant locked down)
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: hass
name: zwave-server
spec:
selector:
matchLabels:
app: zwave-server
replicas: 1
template:
metadata:
labels:
app: zwave-server
spec:
containers:
- image: paullj1/socat_static:1.7.3.3
name: socat
args:
#- -dddd
- -dd
- tcp-l:8080,reuseaddr,keepalive,nodelay
- file:$(DEVICE),nonblock,rawer
env:
- name: DEVICE
value: "/dev/ttyACM0"
ports:
- containerPort: 8080
securityContext:
privileged: true # Implied /dev access
tolerations:
- key: "rpi"
operator: Equal
value: "true"
nodeSelector:
kubernetes.io/hostname: "k3s-agent-rpi3.home"
---
apiVersion: v1
kind: Service
metadata:
namespace: hass
name: zwave-server
spec:
ports:
- port: 8080
selector:
app: zwave-server
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: hass
name: zwave-client
spec:
selector:
matchLabels:
app: zwave-client
replicas: 1
template:
metadata:
labels:
app: zwave-client
spec:
containers:
- image: paullj1/socat_static:1.7.3.3
name: socat
args:
#- -dddd
- -dd
- pty,link=/var/run/zwave/dev,ignoreof,rawer
- tcp:zwave-server:8080,forever
securityContext:
privileged: true # Implied /dev access
volumeMounts:
- name: dev-pts
mountPath: /dev/pts
- name: zwave-dir
mountPath: /var/run/zwave
resources: {}
volumes:
- name: dev-pts
hostPath:
path: /dev/pts
type: Directory
- name: zwave-dir
hostPath:
path: /var/run/zwave
type: DirectoryOrCreate
nodeSelector:
kubernetes.io/hostname: "k3s-agent-1.home"
apiVersion: apps/v1
kind: Deployment
metadata:
namespace: hass
name: hass
spec:
selector:
matchLabels:
app: hass
replicas: 1
template:
metadata:
labels:
app: hass
spec:
containers:
- name: hass
image: homeassistant/home-assistant:0.109.0
env:
- name: ZWAVE_DEVICE
value: /var/run/zwave/dev
ports:
- containerPort: 8123
name: http
protocol: TCP
volumeMounts:
- name: config-nas-volume
mountPath: /config
- name: dev-pts
mountPath: /dev/pts
- name: zwave-dir
mountPath: /var/run/zwave
livenessProbe:
initialDelaySeconds: 60
timeoutSeconds: 10
httpGet:
path: /api/
port: http
httpHeaders:
- name: Content-Type
value: application/json
- name: Authorization
value: Bearer XXXXXXXXXX
resources: {}
volumes:
- name: config-nas-volume
nfs:
server: nas.home
path: /mnt/tank/kubernetes/hass
- name: zwave-dir
hostPath:
path: /var/run/zwave
type: Directory
- name: dev-pts
hostPath:
path: /dev/pts
type: Directory
nodeSelector:
kubernetes.io/hostname: "k3s-agent-1.home"
---
apiVersion: v1
kind: Service
metadata:
namespace: hass
name: hass
spec:
ports:
- port: 8123
targetPort: 8123
name: hass-8123
- port: 80
targetPort: 8123
name: hass-80
selector:
app: hass
type: LoadBalancer
loadBalancerIP: XXXXXXXXXXXXX
So my situation is the following:
I have Home Assistant running on a Rasberry pi 4B 4GB.
And i have 2 rasberry pi zero. And i want to connect a zwave and a zigbee usb to each.
And then place the 2 pi zero inside the house. And the home assistant is in the garage 30 meter away. Whats the best way to connect these pi zeroās to my main home asisstant. Iāve read this guide but it says it needs to install some apt on the rasberry, but i am running the native iso from home assistant. Can anyone give me some insight?