No more ZWave device since this night

Configuration
1

I do not have any ZWave device since this night. Tried several version 0.83.x … 0.84.x and none seems working.
The OZW_Log.txt just displays the following lines:

2018-12-26 11:56:37.029 Always, OpenZwave Version 1.4.3254 Starting Up
2018-12-26 11:57:04.075 Info, Setting Up Provided Network Key for Secure Communications
2018-12-26 11:57:04.075 Info, mgr,     Added driver for controller /dev/ttyUSB-ZStick-5G
2018-12-26 11:57:04.075 Info,   Opening controller /dev/ttyUSB-ZStick-5G
2018-12-26 11:57:04.075 Info, Trying to open serial port /dev/ttyUSB-ZStick-5G (attempt 1)
2018-12-26 11:57:04.076 Info, Serial port /dev/ttyUSB-ZStick-5G opened (attempt 1)
2018-12-26 11:57:04.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-12-26 11:57:04.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-12-26 11:57:04.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-12-26 11:57:04.077 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-12-26 11:57:04.077 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-12-26 11:57:04.077 Detail,
2018-12-26 11:57:04.077 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2018-12-26 11:57:05.077 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-26 11:57:05.077 Detail, contrlr, Removing current message
2018-12-26 11:57:05.077 Detail, contrlr, Notification: Notification - TimeOut
2018-12-26 11:57:05.080 Detail,
2018-12-26 11:57:05.080 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2018-12-26 11:57:06.081 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-26 11:57:06.081 Detail, contrlr, Removing current message
2018-12-26 11:57:06.081 Detail, contrlr, Notification: Notification - TimeOut
2018-12-26 11:57:06.082 Detail,
2018-12-26 11:57:06.082 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2018-12-26 11:57:07.083 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-26 11:57:07.083 Detail, contrlr, Removing current message
2018-12-26 11:57:07.083 Detail, contrlr, Notification: Notification - TimeOut
2018-12-26 11:57:07.085 Detail,
2018-12-26 11:57:07.085 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2018-12-26 11:57:08.085 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-26 11:57:08.086 Detail, contrlr, Removing current message
2018-12-26 11:57:08.086 Detail, contrlr, Notification: Notification - TimeOut
2018-12-26 11:57:08.090 Detail,
2018-12-26 11:57:08.090 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2018-12-26 11:57:09.091 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-12-26 11:57:09.091 Detail, contrlr, Removing current message
2018-12-26 11:57:09.091 Detail, contrlr, Notification: Notification - TimeOut

Main log display ZWave is stuck somewhere:

2018-12-26 12:02:04 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave not ready after 300 seconds, continuing anyway
2018-12-26 12:02:04 INFO (MainThread) [homeassistant.components.zwave] final network state: 0 Network is stopped
2018-12-26 12:02:04 INFO (Thread-3) [homeassistant.components.zwave] Z-Wave polling interval set to 60000 ms

Any idea?
My ZWave divice is a Z-Wave Plus Z-Stick GEN5 and does not even appear in the Zwave page. /dev/ttyUSB-ZStick-5G points well to /dev/ttyACM0 which is the ZWave stick, like seen in dmesg:

[    5.189458] usbcore: registered new interface driver brcmfmac
[    5.198532] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device

Here is the lsusb:

$ lsusb -v

Bus 001 Device 005: ID 0658:0200 Sigma Designs, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength                18
bDescriptorType         1
bcdUSB               2.00
bDeviceClass            2 Communications
bDeviceSubClass         0
bDeviceProtocol         0
bMaxPacketSize0         8
idVendor           0x0658 Sigma Designs, Inc.
idProduct          0x0200
bcdDevice            0.00
iManufacturer           0
iProduct                0
iSerial                 0
bNumConfigurations      1
Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
    (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
    bLength                 9
    bDescriptorType         4
    bInterfaceNumber        0
    bAlternateSetting       0
    bNumEndpoints           1
    bInterfaceClass         2 Communications
    bInterfaceSubClass      2 Abstract (modem)
    bInterfaceProtocol      1 AT-commands (v.25ter)
    iInterface              0
    CDC Header:
        bcdCDC               1.10
    CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
    CDC ACM:
        bmCapabilities       0x00
    CDC Union:
        bMasterInterface        0
        bSlaveInterface         1
    Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
        Transfer Type            Interrupt
        Synch Type               None
        Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              32
    Interface Descriptor:
    bLength                 9
    bDescriptorType         4
    bInterfaceNumber        1
    bAlternateSetting       0
    bNumEndpoints           2
    bInterfaceClass        10 CDC Data
    bInterfaceSubClass      0 Unused
    bInterfaceProtocol      0
    iInterface              0
    Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
        Transfer Type            Bulk
        Synch Type               None
        Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
    Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
        Transfer Type            Bulk
        Synch Type               None
        Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
2

I’m not 100% sure but could this be wrong path set to find your USB Z-Stick?

Appears to be looking for z-stick at /dev/ttyUSB-ZStick-5G but based on

I think the path should be /dev/ttyACM0

Edit : I see that you mention "/dev/ttyUSB-ZStick-5G points well to /dev/ttyACM0" maybe just try your HA configuration with /dev/ttyACM0.

3

Indeed, had to reboot and change to /dev/ttyACM0 and it works. Why the symbolic link does not work anymore? They seems ok:

lrwxrwxrwx 1 root root          7 Nov  3  2016 /dev/ttyUSB-RFX433-A -> ttyUSB0
lrwxrwxrwx 1 root root          7 Nov  3  2016 /dev/ttyUSB-ZStick-5G -> ttyACM0

Weird, this was working well previously.

Here are my rules for creating them:

# RFXCOM:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A1HCLNT", SYMLINK+="ttyUSB-RFX433-A"

# AeoTec Z-Stick Gen5:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="ttyUSB-ZStick-5G"
4

That should work perfectly fine. You seem to be using the method I started last year when I first started using zwave (I can tell because of the unique symlink name I made up :wink: ).

I’ve been using the exact method you are using for over a year and have had no issues.

I don’t think the issues you are experiencing are from a “failed” symlink. From all the info you posted the symlink is obviously working.

From your log above:

2018-12-26 11:57:04.075 Info, Opening controller /dev/ttyUSB-ZStick-5G
2018-12-26 11:57:04.075 Info, Trying to open serial port /dev/ttyUSB-ZStick-5G (attempt 1) 
2018-12-26 11:57:04.076 Info, Serial port /dev/ttyUSB-ZStick-5G opened (attempt 1)

if the symlink was not working you wouldn’t see a successful opening of the port based on that symlink address.

But this tells me something might be wrong with the stick:

Try switching back to the “/dev/ttyUSB-ZStick-5G” and see if it works again. Maybe it was a glitch in the z stick itself that caused it.

The problem is if you don’t use a persistent USB path then when you reboot your HA machine the USB address could change and you will be chasing USB addresses for your zwave stick all the time.

5

Did that, tried several times to switch back and forth, only usb_path: /dev/ttyACM0 works. Weird. I cannot get the fullpath of the symblink to be created /dev/ttyUSB-ZStick-5G => /dev/ttyACM0 instead of => ttyACM0 but I do not see why it should fail…

6

What command are you running to get this result:

lrwxrwxrwx 1 root root 7 Nov 3 2016 /dev/ttyUSB-RFX433-A -> ttyUSB0 
lrwxrwxrwx 1 root root 7 Nov 3 2016 /dev/ttyUSB-ZStick-5G -> ttyACM0

I’ll check mine to see if it matches. So far I can’t see anything obviously wrong.