ZWAVE network stopped working, suddenly

Klagio · August 24, 2019, 4:24pm

It has been very solid since a year or more, today, not sure if after a restart or when, is totally off.

Below the LOG, what can that be?


2019-08-24 18:19:56.765 Always, OpenZwave Version 1.4.3440 Starting Up
2019-08-24 18:22:04.073 Info, Setting Up Provided Network Key for Secure Communications
2019-08-24 18:22:04.073 Warning, Failed - Network Key Not Set
2019-08-24 18:22:04.074 Info, mgr,     Added driver for controller /dev/ttyACM0
2019-08-24 18:22:04.074 Info,   Opening controller /dev/ttyACM0
2019-08-24 18:22:04.074 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
2019-08-24 18:22:04.074 Info, Serial port /dev/ttyACM0 opened (attempt 1)
2019-08-24 18:22:04.074 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-08-24 18:22:04.074 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-08-24 18:22:04.074 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-08-24 18:22:04.074 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-08-24 18:22:04.074 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-08-24 18:22:04.074 Detail,
2019-08-24 18:22:04.074 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-08-24 18:22:05.075 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-24 18:22:05.075 Detail, contrlr, Removing current message
2019-08-24 18:22:05.075 Detail, contrlr, Notification: Notification - TimeOut
2019-08-24 18:22:05.078 Detail,
2019-08-24 18:22:05.078 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-08-24 18:22:06.078 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-24 18:22:06.078 Detail, contrlr, Removing current message
2019-08-24 18:22:06.078 Detail, contrlr, Notification: Notification - TimeOut
2019-08-24 18:22:06.079 Detail,
2019-08-24 18:22:06.079 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-08-24 18:22:07.079 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-24 18:22:07.079 Detail, contrlr, Removing current message
2019-08-24 18:22:07.079 Detail, contrlr, Notification: Notification - TimeOut
2019-08-24 18:22:07.089 Detail,
2019-08-24 18:22:07.089 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-08-24 18:22:08.091 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-24 18:22:08.091 Detail, contrlr, Removing current message
2019-08-24 18:22:08.091 Detail, contrlr, Notification: Notification - TimeOut
2019-08-24 18:22:08.141 Detail,
2019-08-24 18:22:08.141 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-08-24 18:22:09.141 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-24 18:22:09.141 Detail, contrlr, Removing current message
2019-08-24 18:22:09.141 Detail, contrlr, Notification: Notification - TimeOut

firstof9 · August 24, 2019, 4:28pm

OpenZwave is unable to talk to the stick at /dev/ttyACM0. So either the path has changed, (ie: /dev/ttyACM1), the kernel is having a fit (reboot), or the device has died.

Klagio · August 24, 2019, 8:36pm

Thanks. But seems OK the port, no?


. 

:~$ lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 006: ID 8087:0a2a Intel Corp.
Bus 002 Device 003: ID 0658:0200 Sigma Designs, Inc.
Bus 002 Device 002: ID 0603:0002 Novatek Microelectronics Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hu


io@ubuntu:~$ ls /dev/ttyACM*
/dev/ttyACM0

this my config


zwave:
  usb_path: /dev/ttyACM0

Klagio · August 24, 2019, 8:54pm

Ok, I took out the stick and put it back, now I have a different log (the nodes still do not populate)


2019-08-24 22:44:43.511 Error, mgr,     Manager::GetDriver failed - Home ID 0x00000000 is unknown
2019-08-24 22:44:43.512 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2019-08-24 22:44:43.512 Info, mgr,     Manager::WriteConfig failed - _homeId 0 not found
2019-08-24 22:44:44.514 Detail, Notification: DriverRemoved
2019-08-24 22:44:44.514 Always, ***************************************************************************
2019-08-24 22:44:44.514 Always, *********************  Cumulative Network Statistics  *********************
2019-08-24 22:44:44.514 Always, *** General
2019-08-24 22:44:44.514 Always, Driver run time: . .  . 0 days, 4 hours, 22 minutes
2019-08-24 22:44:44.514 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, Total messages successfully received: . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, Total Messages successfully sent: . . . . . . . . . . . . 5
2019-08-24 22:44:44.514 Always, ACKs received from controller:  . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, *** Errors
2019-08-24 22:44:44.514 Always, Unsolicited messages received while waiting for ACK:  . . 0
2019-08-24 22:44:44.514 Always, Reads aborted due to timeouts:  . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, Bad checksum errors:  . . . . . . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, CANs received from controller:  . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, NAKs received from controller:  . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, Out of frame data flow errors:  . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0
2019-08-24 22:44:44.514 Always, Messages dropped and not delivered: . . . . . . . . . . . 5
2019-08-24 22:44:44.514 Always, ***************************************************************************
2019-08-24 22:44:44.514 Warning, WARNING: Tried to write driver config with no home ID set
2019-08-24 22:44:44.515 Info, mgr,     Driver for controller /dev/ttyACM0 removed

thundergreen · August 24, 2019, 9:00pm

Did you by chance install deconz and accidently use the same /dev/ttyACM0 ? This happened to me just a hint … Watch in your setup if another component is using this device

omerome · August 24, 2019, 9:18pm

That’st the exact situation I am going through now. When I use my ZWave devices from my Aeotec Z Stick on /dev/ttyACM0 everything works fine, but if I try to load DeCONZ using my Conbee II device and try to assign it /dev/ttyACM1, it just doesn’t work right - especially if I reboot.

freshcoast · August 24, 2019, 9:22pm

Use the persistent path names that are created in /dev/serial/by-id, e.g. /dev/serial/by-id/usb-0658_0200-if00.

Klagio · August 24, 2019, 9:30pm

I use Conbee but on another host, magically now it works again but did not add the nodes (around 10 devices).

Do I have to go through the pairing process again (please tell me I have another option …)?

omerome · August 24, 2019, 9:36pm

Thanks a lot!

My Z Wave devices connected successfully using that method, but my Conbee II which is:

/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE1995746-if00

still isn’t connecting though.

Klagio · August 24, 2019, 10:30pm

Now it works again (had to remove the stick re insert it and reboot), the zwave network is there but no nodes … I never did a zwave restore, I do have previous days backup. Anyone did the restore?

Do I have first to re-pair all the devices and then restore the zwave, viceversa … or simply have to configure everything again (argh!) ?

omerome · August 24, 2019, 11:44pm

Unfortunately in my case, I just configured everything from scratch when I was troubleshooting. I was missing a node (node 2 then node 4 - it was driving me nuts) in my configuration so at least it wasn’t completely pointless.

thundergreen · August 25, 2019, 6:17am

Zwave stick is ACM0 while deconz is usb0 ors usb1 or dependent on what you have attached else on your server .

So normally there’s no shared ACM

For zwave take snapshot and you should be good to go . Information are saved on the stick and hass just creates a file for caching this prevents that homeassistant has to read out all zwave information each start-up. Further this information are only available on pairing mode.

Just be sure not messing up with USB and acm and ty restoring a snapshot and all should be back to normal with your zwave . I’ve alsmot 30 zwave devices and reset my network multiple times. You don’t really want this try to recover if possible I work with snapshots now

Klagio · August 25, 2019, 9:13am

Never restored with snapshots before, I can restore the zwave only part?..

thundergreen · August 25, 2019, 6:48pm

I got SQLite error after restoring and never made partially restore but in theory it’s meant for this yeah but to be sure make full backup/ restore … Doesn’t hurt