Zwave stick dissapeared

Configuration Z-Wave
1

My Ubuntu 18.04 quit responding the other day and I rebooted it. did updates and almost everything is working. Except home assistant.

arch x86_64
dev false
docker true
hassio false
os_name Linux
python_version 3.7.2
timezone America/Chicago
version 0.88.0
virtualenv false

It apparently is not seeing the aeotech zwave usb stick. I can’t see where to check that in the gui. I don’t think on this version I am supposed to put it in configuration.yaml

Integration/Zwave shows me all the modules, but not the stick. Zwave managment does not show where I would enter the controller.

2

I don’t see how to edit this. This is running under docker on 18.04.

3

Did the mount point change on the reboot?

Check the mount in Ubuntu and confirm your docket settings to ensure it’s being passed to the container properly still.

4

You can put the zwave configuration in configuration.yaml in any version.

As a matter of fact if you do put the USB path in configuration.yaml as of v91 the configuration.yaml setting for the USB path will override the setting in the device registry.

So, yes, make sure that the path in HA matches the path of the stick on the host and the path of the stick in Docker.

If the stick path changed on the host then you should set up a persistent path so reboots don’t affect your HA.

5

That’s what happened to me when I inexplicably lost access to my ZStick. It had jumped to another tty entry (TTYACM1 vs. TTYACM0 in my case), and I had to adjust the dev node in the zwave config and restart hass. It was back on ACM0 on the next reboot, so I had to put it back. Hasn’t happened since.

I imagine that one could use a “by-id” path to avoid this nonsense, but I haven’t looked into it.

6

i use a udev rule to set the path and i never have any issues. i tried by_id but i didn’t get it to work so since the udev was working i just stuck with that.