[SOLVED] Zwave stick gen 5 does not show up in HA

Configuration Z-Wave
1

Hello All,

I have now for days tried to get the zwave stick working under HA. I have HA supervisor running on Ubuntu. I can see the device in the hardware overview and add the zwave in the configuration of HA.

zwave:
  usb_path: /dev/serial/by-id/usb-0658_0200-if00
  device_config: !include zwave_device_config.yaml
  network_key: " some key"

I also tried with /dev/ttyACM0 as usb_path but i saw in some post that i should use the serial one.

I can go to the gui of zwave under configuration but the node is empty and i cannot choose a node. Also the OZW log is empty.

Can anyone please help me?

2

Do you use a RPi4 ?

3

no, i am using a virtual Ubuntu 18.04 server and installed the supervised edition…

4

Did you uninstall ModemManager? https://www.home-assistant.io/docs/z-wave/installation#home-assistant

5

yes i did…

It seems it can not connect to the zwave stick

2020-04-22 20:32:53 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Z-Wave (import from configuration.yaml) for zwave
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/openzwave/option.py", line 78, in __init__
    raise ZWaveException(u"Can't find device %s : %s" % (device, traceback.format_exception(*sys.exc_info())))
openzwave.object.ZWaveException: "Zwave Generic Exception : Can't find device /dev/serial/by-id/usb-0658_0200-if00 : ['NoneType: None\\n']"
6

It does look like the path is not available. When this happens you can still see the path when looking at the HA hardware info?

7

This what i see

afbeelding
afbeelding590×584 15.6 KB

and this

afbeelding
afbeelding1070×114 71.4 KB

8

Ok started up my Domoticz Pi and connected the stick. That worked flawless. So the stick is OK.
Also tried the usbip setup to make sure that the usb passthrough was not the problem…still no joy.

I am about to start a clean install of HA supervised…

9

Do the devices show up in the container? I’m running Home Assistant Core inside of regular docker, and need to pass in the device when launching the container with --device or equivalent if using docker-compose.

Maybe from the “outside”, you can launch a shell inside the running container and see if the device appears where you expect it. E.g., docker exec -it hass bash

louie@hass[2] $ docker exec -it hass /bin/bash
bash-5.0# ls -l /dev/
total 76
lrwxrwxrwx    1 root     root            11 Apr 21 13:20 core -> /proc/kcore
lrwxrwxrwx    1 root     root            13 Apr 21 13:20 fd -> /proc/self/fd
crw-rw-rw-    1 root     root        1,   7 Apr 21 13:20 full
-rw-r--r--    1 root     root         74802 Apr 23 06:20 kmsg
drwxrwxrwt    2 root     root            40 Apr 21 13:20 mqueue
crw-rw-rw-    1 root     root        1,   3 Apr 21 13:20 null
lrwxrwxrwx    1 root     root             8 Apr 21 13:20 ptmx -> pts/ptmx
drwxr-xr-x    2 root     root             0 Apr 21 13:20 pts
crw-rw-rw-    1 root     root        1,   8 Apr 21 13:20 random
drwxrwxrwt    2 root     root            40 Apr 21 13:20 shm
lrwxrwxrwx    1 root     root            15 Apr 21 13:20 stderr -> /proc/self/fd/2
lrwxrwxrwx    1 root     root            15 Apr 21 13:20 stdin -> /proc/self/fd/0
lrwxrwxrwx    1 root     root            15 Apr 21 13:20 stdout -> /proc/self/fd/1
crw-rw-rw-    1 root     root        5,   0 Apr 21 13:20 tty
crw-rw-rw-    1 root     root        1,   9 Apr 21 13:20 urandom
crw-rw-rw-    1 root     root        1,   5 Apr 21 13:20 zero
crw-rw----    1 root     dialout   166,   0 Apr 23 10:29 zwavestick

In my case, I pass in the USB stick as /dev/zwavestick in my docker-compose file:

services:
  hass:
    container_name: hass
    image: "homeassistant/home-assistant:0.108.6"
    restart: "always"
    network_mode: "host"
    environment:
      - "TZ=America/New_York"
    volumes:
      - "/home/hass/home-assistant/config:/config"
      - "/home/hass/home-assistant/db:/config/db"
      - "/home/hass/home-assistant/logs:/config/logs"
    devices:
      - "/dev/ttyACM0:/dev/zwavestick"
10

Ok, i have to check that. In the mean time i installed a fresh installation on a new Ubuntu vm and now it works.

But i need to migrate other things also, so i rather have it solved on the current system.

11

ok that strange. I looked with in the docker (ls /dev/) but as the HA gui shows the ttyACM0 device, within the container itself not.

whats going on?

12

ok found the solution, it was my own fault. While playing with socat, i had a dsystem service running also claiming ttyAMC0…

Thanks for all the help. It helped me solve the problem.

Regards,

Francis