I’ve installed hass.io on Ubuntu and it works great. How can I go about passing my UDEV rules for my symlink /dev/zwave stick into the homeassistant docker container?
Is there a dockerfile or something I could edit?
I see reference to adding -v /dev/zstick:/dev/zstick \, just not sure where that would go. I thought initially /usr/bin/hassio-start, but doesn’t seem that it’s applying it to the homeassistant container.
You don’t have to, just set /dev/zwave as port in the configuration of the component you need it.
The docker stuff should never be touched manually, that’s the whole point of Hass IO
Except it’s not working. Home Assistant UI shows me an Invalid zwave configuration when I try that. Why? Because the symlink in /dev isn’t copied over to the docker container. Even after a reboot of the host.
Here’s how I know that:
On the host:
obrien@hass:~$ ls -al /dev | grep zwave
lrwxrwxrwx 1 root root 7 Jan 17 11:33 zwave -> ttyACM0
This confirms it’s there and working. Now checking the docker container:
Nope, it needs to be included in the dockerfile that the hass.io devs generate. I don’t think it’s an option for right now. Maybe on HassOS it’ll be included?
Problem is still here. I noticed it after I replaced a hard-coded /dev/ACM0 with a udev generated softlink. The link is not propagated to the docker container.
Hi guys, I stuck with the same problem here: symlinks are not being passed by supervisor to HA. Is there any option to fix the name and also pass it down to the container?
No - but what I found to be the solution was to SSH to hassio, then run hassio hardware info then under the serial: section look for the named identifier of your USB stick. Mine shows my zwave stick like this: /dev/serial/by-id/usb-0658_0200-if00
Then paste that into your configuration and it should be good to go.
Hi @obrienlabs. Thanks! It worked! I figure out that myself a week ago but nice to mention to those who didn’t! Maybe it worth adding to the docs somewhere I don’t know.