Is my Z-Wave USB working?

Configuration Z-Wave
1

I have hass 0.16.1 running as a docker imaged on my Ubuntu linux box and have added an Aeotec Z-stick Gen5 and added the necessary zwave section into my configuration.yaml. When I start my docker image with hass inside of it, I get this error:

16-04-02 15:16:35 WARNING (Dummy-6) [openzwave] Z-Wave Notification DriverFailed : {‘homeId’: 0, ‘notificationType’: ‘DriverFailed’, ‘nodeId’: 255}

I know it’s just a warning, but I have a feeling something is not working.

Should I be concerned?

Thanks!

2

Are you, by any chance, using a udev map to point to your z-stick? Docker doesn’t follow the symlinks that are created when you use a udev mapping. I think that’s close to/the same error I got when trying to run ozwcp in docker.

3

Thank you @wyznerd for the reply!

Um, I am just running docker with these flags:

–privileged -v /dev/ttyACM0:/dev/ttyACM0

I’m not sure if that answers your question, but I do appreciate the help!

Thank you!

1 Like
4

Here is docker run with Gen5 Aeotec Z-Stick. Working well.

docker run
–name=“home-assistant”
–net=host
-d
-v /etc/localtime:/etc/localtime:ro
-v /root/docker/HA/config:/config
–device=/dev/ttyACM0:/dev/ttyACM0
balloob/home-assistant:latest

2 Likes
5

Ok, that makes sense, I will give it a try. Thank you so much!!

6

I keep getting this error:

FATA[0000] Error response from daemon: Cannot start container e3f786c89f7068669ba321be736c194485397f23ee4cadf69360f7b493159b28: error gathering device information while adding custom device “/dev/ttyACM0”: not a device node

I wonder if something is wrong with my linux box… when I do an ls -al on /dev/ttyACM0 it looks like an empty folder, I would expect it to look like a special file or something…

7

Run the following and see if the zwave stick is being assigned to a different ACM#. Mine occasionally maps to ttyACM1 instead of ACM0.

ls /dev/ttyACM*

If the output is something other than ACM0, try removing the USB stick and plugging it back in. Then rerun the above.
Otherwise you could just change the mapping in your docker run statement… --device=/dev/ttyACM1:/dev/ttyACM0

8

Thank you for continuing to try to help. Yeah, I keep seeing an empty directory whether the USB stick is plugged in or not:

user@ubuntubox ~ $ ls -al /dev/ttyACM*
total 0
drwxr-xr-x  2 root root   40 Apr  8 19:57 .
drwxr-xr-x 18 root root 4380 Apr 10 09:14 ..
user@ubuntubox ~ $ ls -ald /dev/ttyACM*
drwxr-xr-x 2 root root 40 Apr  8 19:57 /dev/ttyACM0

On my raspberry pi it looks right:

pi@raspberrypi:~ $ ls -al /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Apr 11 20:10 /dev/ttyACM0

Thanks again for the help!

9

Not sure whats going on with your ubuntubox. I’m running debian and it looks like your raspberry box.

root@NetSrv1:/dev# ls -al ttyACM*
crw-rw---- 1 root dialout 166, 0 Apr 11 10:06 ttyACM0

Might try removing the USB stick and then deleting the ttyACM0 directory. Then try again.

10

I know this has been a while, is there a way to get docker to follow udev symlinks?

1 Like