Zwave does not start

Configuration
1

Using HASS on Synology Docker
I have aeotec zwave stick gen 5 I have run ls /dev/tty* severe times always got /dev/ttyACM0
I got no nodes and folowing errors

2018-03-25 14:08:00.085 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2018-03-25 14:08:00.087 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 6
2018-03-25 14:08:00.087 Error, ERROR: Failed to open serial port /dev/ttyACM0
2018-03-25 14:08:00.087 Warning, WARNING: Failed to init the controller (attempt 3)
2018-03-25 14:08:05.087 Info, Opening controller /dev/ttyACM0
2018-03-25 14:08:05.087 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2018-03-25 14:08:05.090 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 6
2018-03-25 14:08:05.090 Error, ERROR: Failed to open serial port /dev/ttyACM0
2018-03-25 14:08:05.090 Warning, WARNING: Failed to init the controller (attempt 4)
2018-03-25 14:08:05.090 Detail, contrlr, Notification: DriverFailed

1 Like
2

Hi

I’ve got the same error, did you figure out the cause and how to fix it?

Many thanks

3

Nope
Bwalberg

4

Same problem here…

5

Exactly what problem are you having - log messages etc please

Have you checked the troubleshooting steps?

6

Got error code 6, and then also noticed that door basically does not respond to switch in HASS.

I was using double quotes in my secrets file and after removing them and properly adding the lock as secure node, this error code disappears. However, door is still unresponsive with the lock switch in hass, and the state of lock/unlock still inconsistent with the actual. But this error message is gone.

7

I also experience this problem :frowning: The only solution I have is to retsrat HA and if this doesn’t help - I need to either restart my NAS running HA in Docker or disconnect the zwaveusb stick and restart HA then.
It’s really bad as because of that HA is not suitable for controlling zwave devices and it makes it unreliable :frowning:

I ssh’ed to my NAS and noticed that the stick is not anymore in /dev. It’s usually ttyACM0, and now I don’t have it. But instead ttyACM1. After disconnecting the stick ACM1 disappeared and ACM0 returned. Very weird. Perhaps it’s a host OS problem, not Open ZWave? Still not sure how to fix it. Would be great to force linux to reattach it without physically removing and reinsterting it.

QUESTIONS TO ALL:

  1. Do you run your HA in Docker e.g. on a NAS?
  2. Do you use a USB hub and connect?
8

I think this may be related to the self-changing device file (from ttyACM0 to ttyACM1).
I found a nice solution for that in the web: symlinks to device files. Shortly: there’s a way to force the system to represent a USB device like Aeotec stick always by the same file eg /dev/USBzwave. I applied the solution. Will see if it solves the problem, but I hope so.

Lecture:

http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/
http://www.reactivated.net/writing_udev_rules.html#example-netif

The exact udev rule I applied to my Synology which works and creates a symlink:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="USBzwave"

Thanks to the above I always have a /dev/USBzwave file and map it in Docker to /zwaveusbstick for HA in HA config