Z-Wave on UnRaid Docker

Hi,

I am running Home Assistant on a UnRaid Docker since 1 week.

Today I got my Aeotec Z-Stick Gen5 and one MultiSensor and Plug.

I connected the Stick on my UnRaid server and then I was running the following command:

root@UnRaid:/mnt/user/appdata/home-assistant# ls -ltr /dev/tty*|tail -n 1
crw-rw---- 1 root dialout 166,  0 May 12 14:38 /dev/ttyACM0

I added then the following code to the configuration.yaml:

zwave:
  usb_path: /dev/ttyACM0
  debug: true

I also added the following extra-parameter to the docker:

--device=/dev/ttyACM0

After that I restarted HomeAssistant, but unfortunatley nothing happened…

What I am doing wrong?

Br,
Johannes

1 Like

I have a similar setup.

I used the UnRaid UI to edit the container and selected “add another Device” then set the value to be /dev/ttyACM0:/dev/ttyACM0. This maps the device on the host (UnRaid) to a device with the same name in the container (HA).That seems to work for me.

Using --device=/dev/ttyACM0:/dev/ttyACM0 may also work.

3 Likes

I have tried both options.

If I access the docker CLI I can see the /dev/ttyACM0

Btw.: I added already the motion sensor and the plug to the stick via the stick-Button.
So I asume that I should see the sensors when the stick is working?

Br,
Johannes

Check the unRaid log itself in the main GUI when you plug in the USB device, make sure it is creating the port name that you are trying to address. I have the HUSBZB-1 stick and didn’t have any issues seeing the ports and passing them into the container but it should be very similar to yours with only the single port.

Agree with suggestion above …

… also can you confirm that z-wave has been configured in HA i.e. can you access the Configuration -> Z-Wave panel on the side menu? You should see an option to display the OZW Log. There might be some errors messages that provide a clue to the problem. You can also find the log in /config/OZW_Log.txt from the docker cli or in the associated appdata directory if you are sharing that.

In the Developer Tools -> States you should also see a zwave.aeotec entity and any other zwave devices that have been found.

If Z-Wave hasn’t been initialised correctly in HA then you could try removing then re-installing the container. That may force HA to reconfigure any z-wave dependencies.

It was my mistake, somehow I didnt save the zwave config in configuration.yaml :thinking:

Thank you @PeteB , this worked for me