Getting zwave going with hass.io

Installation Home Assistant OS
1

So I’ve installed Hass.IO for the first time. Was previously using the AIO installer but upgraded because of python.

Anyway, I can’t get zwave to work at all. On my old raspi AIO instance, I was able to run a config like this:

zwave:
usb_path: /dev/zwave
config_path: /srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/libopenzwave-0.3.1-py3.4-linux-armv7l.egg/config/

Now with hass.io when I run ls /dev/tty* the only result is tty

putting this in to my configuration file does not yield positive results. The logfile gives me an error stating it cannot load the zwave stick.

thoughts? I’m not very familiar with the OS that hass.io is built on, so it’s hard to troubleshoot. any help would be appreciated.

2

Have you seen the Z-Wave guide for HassIO?

You’ll not need (or want) the config_path line.

3

Yes I’ve seen it, the config_path was from my old configuration and not in the new one.

Again the only device I can see from the CLI is tty, there is no ttyACM0 or ttyUSB0 or anything like that. Does hass.io keep these somewhere other than /dev/ ?

4

Nope, it’ll be in /dev. What Z-Wave stick are you using?

5

Aeotec Z-Stick Gen5.

Last night I reinstalled hass.io, still getting the same results: the only device in /dev is tty and that doesn’t load the zwave module.

:-/

6

You’ve run the command to map it through as explained in the documentation?

7

Correct, it gives this result: {"result": "ok", "data": {}}core-ssh:~# which certainly sounds positive to me.

Doing ls /dev/tty* still only yields the single tty result.

Could it be an issue since the same devices were used in an old, pre-hass.io instance of home assistant?

8

For hassio, run hassio host hardware while you’re ssh’ed into the ssh addon and you should see the list of serial devices visible by your hassio machine.

9

I stood up a new instance of home assistant running on a Windows VM and was unable to get the z-stick to work. Upon,interrogating the device, Windows detected errors with it. I then did a hard reset on the device and it is now working in hass.io and windows.

I do find it odd that the device doesn’t display in /dev/tty* like other USB devices do though, perhaps this could be future improvement for hass.io

Anyway, the device is now working and I’m posting this report as an FYI in case anyone comes across something similar in the future.