Z Wave mesh stopping working

Hello

For a few weeks now for no reason z wave sensors stop reporting so my automations cease to work. This is on the latest version on a RPi3.

Nothing shows up in the logs and I have to reboot to get it back again. Kind of frustrating and my wife is getting sick of walking into the kitchen and no lights come on when it i dark :slight_smile:
Cheers
Mark

Did you check the OZW_Log.txt file?

It almost sounds like your controller is having issues.

yeah i did, I couldn’t see anything out of the ordinary. has been fine for the last 24 hours, will wait and see.

it has happened twice since… at around 11am this morning my OZW_Log.txt looks like this… does it look like anything anyone can help with please? As it is really annoying me to the point of ditching the whole automation thing now :frowning:

2017-07-19 11:04:41.207 Info, Node005, Received SensorMultiLevel report from node 5, instance 1, Ultraviolet: value=0
2017-07-19 11:04:41.207 Detail, Node005, Refreshed Value: old value=0, new value=0, type=decimal
2017-07-19 11:04:41.207 Detail, Node005, Changes to this value are not verified
2017-07-19 11:04:41.207 Detail, Node005, Notification: ValueChanged
2017-07-19 15:17:18.643 Info, Node010, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-07-19 15:17:18.643 Info, Node010, SwitchBinary::Set - Setting node 10 to On
2017-07-19 15:17:18.643 Detail, Node010, Queuing (Send) SwitchBinaryCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x25, 0x01, 0xff, 0x25, 0xc5, 0xd4
2017-07-19 15:17:18.643 Detail, Node010, Queuing (Send) SwitchBinaryCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x25, 0x02, 0x25, 0xc6, 0x29
2017-07-19 15:17:18.643 Detail, 
2017-07-19 15:17:18.643 Info, Node010, Sending (Send) message (Callback ID=0xc5, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x25, 0x01, 0xff, 0x25, 0xc5, 0xd4
2017-07-19 15:17:19.644 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:17:19.644 Detail, Node010, Removing current message
2017-07-19 15:17:19.644 Detail, Node010, Notification: Notification - TimeOut
2017-07-19 15:17:19.646 Detail, 
2017-07-19 15:17:19.646 Info, Node010, Sending (Send) message (Callback ID=0xc6, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x25, 0x02, 0x25, 0xc6, 0x29
2017-07-19 15:17:20.646 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:17:20.647 Detail, Node010, Removing current message
2017-07-19 15:17:20.647 Detail, Node010, Notification: Notification - TimeOut
2017-07-19 15:21:29.161 Info, Node008, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-07-19 15:21:29.162 Info, Node008, SwitchBinary::Set - Setting node 8 to On
2017-07-19 15:21:29.162 Detail, Node008, Queuing (Send) SwitchBinaryCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x25, 0x01, 0xff, 0x25, 0xc7, 0xd4
2017-07-19 15:21:29.162 Detail, Node008, Queuing (Send) SwitchBinaryCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x25, 0x02, 0x25, 0xc8, 0x25
2017-07-19 15:21:29.162 Detail, 
2017-07-19 15:21:29.162 Info, Node008, Sending (Send) message (Callback ID=0xc7, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x25, 0x01, 0xff, 0x25, 0xc7, 0xd4
2017-07-19 15:21:30.162 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:21:30.162 Detail, Node008, Removing current message
2017-07-19 15:21:30.162 Detail, Node008, Notification: Notification - TimeOut
2017-07-19 15:21:30.165 Detail, 
2017-07-19 15:21:30.165 Info, Node008, Sending (Send) message (Callback ID=0xc8, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x25, 0x02, 0x25, 0xc8, 0x25
2017-07-19 15:21:31.165 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:21:31.165 Detail, Node008, Removing current message
2017-07-19 15:21:31.165 Detail, Node008, Notification: Notification - TimeOut
2017-07-19 15:30:04.364 Detail, Node001, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node003, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node004, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node005, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node006, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node007, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node008, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.365 Detail, Node009, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.366 Detail, Node010, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.366 Detail, Node011, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:04.366 Info, Requesting Neighbor Update for node 1
2017-07-19 15:30:04.366 Detail, Node001, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0xc9, 0x7a
2017-07-19 15:30:04.366 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:04.366 Detail, 
2017-07-19 15:30:04.366 Info, Node001, Sending (Command) message (Callback ID=0xc9, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0xc9, 0x7a
2017-07-19 15:30:05.367 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:05.367 Detail, Node001, Removing current message
2017-07-19 15:30:05.367 Detail, Node001, Notification: Notification - TimeOut
2017-07-19 15:30:05.369 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:05.370 Info, Requesting Neighbor Update for node 2
2017-07-19 15:30:05.370 Detail, 
2017-07-19 15:30:05.370 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:05.370 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:05.370 Detail, Notification: ControllerCommand - Sleeping
2017-07-19 15:30:05.371 Info, Requesting Neighbor Update for node 3
2017-07-19 15:30:05.371 Detail, 
2017-07-19 15:30:05.371 Detail, Node003, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:05.371 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:05.371 Detail, Notification: ControllerCommand - Sleeping
2017-07-19 15:30:05.371 Info, Requesting Neighbor Update for node 4
2017-07-19 15:30:05.371 Detail, Node004, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=4): 0x01, 0x05, 0x00, 0x48, 0x04, 0xcc, 0x7a
2017-07-19 15:30:05.371 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:05.371 Detail, 
2017-07-19 15:30:05.372 Info, Node004, Sending (Command) message (Callback ID=0xcc, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=4): 0x01, 0x05, 0x00, 0x48, 0x04, 0xcc, 0x7a
2017-07-19 15:30:06.372 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:06.379 Detail, Node004, Removing current message
2017-07-19 15:30:06.379 Detail, Node004, Notification: Notification - TimeOut
2017-07-19 15:30:06.382 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:06.383 Info, Requesting Neighbor Update for node 5
2017-07-19 15:30:06.383 Detail, Node005, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=5): 0x01, 0x05, 0x00, 0x48, 0x05, 0xcd, 0x7a
2017-07-19 15:30:06.383 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:06.384 Detail, 
2017-07-19 15:30:06.384 Info, Node005, Sending (Command) message (Callback ID=0xcd, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=5): 0x01, 0x05, 0x00, 0x48, 0x05, 0xcd, 0x7a
2017-07-19 15:30:07.384 Error, Node005, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:07.384 Detail, Node005, Removing current message
2017-07-19 15:30:07.384 Detail, Node005, Notification: Notification - TimeOut
2017-07-19 15:30:07.388 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:07.388 Info, Requesting Neighbor Update for node 6
2017-07-19 15:30:07.389 Detail, 
2017-07-19 15:30:07.389 Detail, Node006, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:07.389 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:07.389 Detail, Notification: ControllerCommand - Sleeping
2017-07-19 15:30:07.389 Info, Requesting Neighbor Update for node 7
2017-07-19 15:30:07.389 Detail, Node007, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=7): 0x01, 0x05, 0x00, 0x48, 0x07, 0xcf, 0x7a
2017-07-19 15:30:07.389 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:07.390 Detail, 
2017-07-19 15:30:07.390 Info, Node007, Sending (Command) message (Callback ID=0xcf, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=7): 0x01, 0x05, 0x00, 0x48, 0x07, 0xcf, 0x7a
2017-07-19 15:30:08.390 Error, Node007, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:08.390 Detail, Node007, Removing current message
2017-07-19 15:30:08.390 Detail, Node007, Notification: Notification - TimeOut
2017-07-19 15:30:08.392 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:08.393 Info, Requesting Neighbor Update for node 8
2017-07-19 15:30:08.393 Detail, Node008, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=8): 0x01, 0x05, 0x00, 0x48, 0x08, 0xd0, 0x6a
2017-07-19 15:30:08.393 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:08.394 Detail, 
2017-07-19 15:30:08.394 Info, Node008, Sending (Command) message (Callback ID=0xd0, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=8): 0x01, 0x05, 0x00, 0x48, 0x08, 0xd0, 0x6a
2017-07-19 15:30:09.394 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:09.394 Detail, Node008, Removing current message
2017-07-19 15:30:09.394 Detail, Node008, Notification: Notification - TimeOut
2017-07-19 15:30:09.396 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:09.397 Info, Requesting Neighbor Update for node 9
2017-07-19 15:30:09.397 Detail, 
2017-07-19 15:30:09.397 Detail, Node009, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:09.397 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:09.398 Detail, Notification: ControllerCommand - Sleeping
2017-07-19 15:30:09.398 Info, Requesting Neighbor Update for node 10
2017-07-19 15:30:09.398 Detail, Node010, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=10): 0x01, 0x05, 0x00, 0x48, 0x0a, 0xd2, 0x6a
2017-07-19 15:30:09.398 Detail, Notification: ControllerCommand - Starting

and when I rebooted

2017-07-19 15:30:08.394 Detail, 
2017-07-19 15:30:08.394 Info, Node008, Sending (Command) message (Callback ID=0xd0, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=8): 0x01, 0x05, 0x00, 0x48, 0x08, 0xd0, 0x6a
2017-07-19 15:30:09.394 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:09.394 Detail, Node008, Removing current message
2017-07-19 15:30:09.394 Detail, Node008, Notification: Notification - TimeOut
2017-07-19 15:30:09.396 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:09.397 Info, Requesting Neighbor Update for node 9
2017-07-19 15:30:09.397 Detail, 
2017-07-19 15:30:09.397 Detail, Node009, Queuing (Controller) Request Node Neighbor Update
2017-07-19 15:30:09.397 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:09.398 Detail, Notification: ControllerCommand - Sleeping
2017-07-19 15:30:09.398 Info, Requesting Neighbor Update for node 10
2017-07-19 15:30:09.398 Detail, Node010, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=10): 0x01, 0x05, 0x00, 0x48, 0x0a, 0xd2, 0x6a
2017-07-19 15:30:09.398 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:09.398 Detail, 
2017-07-19 15:30:09.398 Info, Node010, Sending (Command) message (Callback ID=0xd2, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=10): 0x01, 0x05, 0x00, 0x48, 0x0a, 0xd2, 0x6a
2017-07-19 15:30:10.398 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:10.399 Detail, Node010, Removing current message
2017-07-19 15:30:10.399 Detail, Node010, Notification: Notification - TimeOut
2017-07-19 15:30:10.401 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 15:30:10.401 Info, Requesting Neighbor Update for node 11
2017-07-19 15:30:10.401 Detail, Node011, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=11): 0x01, 0x05, 0x00, 0x48, 0x0b, 0xd3, 0x6a
2017-07-19 15:30:10.402 Detail, Notification: ControllerCommand - Starting
2017-07-19 15:30:10.402 Detail, 
2017-07-19 15:30:10.402 Info, Node011, Sending (Command) message (Callback ID=0xd3, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=11): 0x01, 0x05, 0x00, 0x48, 0x0b, 0xd3, 0x6a
2017-07-19 15:30:11.402 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-19 15:30:11.407 Detail, Node011, Removing current message
2017-07-19 15:30:11.407 Detail, Node011, Notification: Notification - TimeOut
2017-07-19 15:30:11.409 Detail, Notification: ControllerCommand - Error - Failed
2017-07-19 17:53:55.284 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xd2a9fa3e
2017-07-19 17:53:59.387 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xd2a9fa3e
2017-07-19 17:53:59.394 Info, mgr,     Driver for controller /dev/zwave pending removal
2017-07-19 17:53:59.394 Detail, Notification: DriverRemoved
2017-07-19 17:53:59.394 Always, ***************************************************************************
2017-07-19 17:53:59.394 Always, *********************  Cumulative Network Statistics  *********************
2017-07-19 17:53:59.394 Always, *** General
2017-07-19 17:53:59.394 Always, Driver run time: . .  . 0 days, 9 hours, 32 minutes
2017-07-19 17:53:59.394 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 5800
2017-07-19 17:53:59.394 Always, Total messages successfully received: . . . . . . . . . . 5800
2017-07-19 17:53:59.394 Always, Total Messages successfully sent: . . . . . . . . . . . . 219
2017-07-19 17:53:59.394 Always, ACKs received from controller:  . . . . . . . . . . . . . 205
2017-07-19 17:53:59.394 Always, *** Errors
2017-07-19 17:53:59.394 Always, Unsolicited messages received while waiting for ACK:  . . 3
2017-07-19 17:53:59.394 Always, Reads aborted due to timeouts:  . . . . . . . . . . . . . 0
2017-07-19 17:53:59.394 Always, Bad checksum errors:  . . . . . . . . . . . . . . . . . . 0
2017-07-19 17:53:59.394 Always, CANs received from controller:  . . . . . . . . . . . . . 3
2017-07-19 17:53:59.395 Always, NAKs received from controller:  . . . . . . . . . . . . . 0
2017-07-19 17:53:59.395 Always, Out of frame data flow errors:  . . . . . . . . . . . . . 0
2017-07-19 17:53:59.395 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 3
2017-07-19 17:53:59.395 Always, Messages dropped and not delivered: . . . . . . . . . . . 23
2017-07-19 17:53:59.395 Always, ***************************************************************************
2017-07-19 17:54:02.252 Info, mgr,     Driver for controller /dev/zwave removed
2017-07-19 17:54:03.259 Error, mgr,     Manager::GetDriver failed - Home ID 0xd2a9fa3e is unknown
2017-07-19 17:54:03.259 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2017-07-19 17:54:03.259 Info, mgr,     GetSendQueueCount() failed - _homeId -760612290 not found

What controller are you using?

Aeon Z-Stick Gen5

Almost looks like it’s failing. Perhaps try another USB port could be an issue with the port as well.

I have this exact problem. Works a bit after I restart HASS but then the state data becomes stale. My GE switches and Dimmers are all zwave plus and support instant status. So not sure whats going on.

tried a new port and the same only last night. Looks like it failed on node 5 both times, which is my powered Aeotec multi sensor. I have it set to report every 10 seconds, so changed that to 60, to see if it was flooding the stick???

2017-07-20 03:09:01.957 Info, Node005, Received SensorMultiLevel report from node 5, instance 1, Temperature: value=24.1C
2017-07-20 03:09:01.957 Detail, Node005, Refreshed Value: old value=24.0, new value=24.1, type=decimal
2017-07-20 03:09:01.957 Detail, Node005, Changes to this value are not verified
2017-07-20 03:09:01.957 Detail, Node005, Notification: ValueChanged
2017-07-20 03:09:02.215 Detail, Node005,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x31, 0x05, 0x05, 0x01, 0x40, 0x80
2017-07-20 03:09:02.215 Detail, 
2017-07-20 03:09:02.215 Info, Node005, Received SensorMultiLevel report from node 5, instance 1, Relative Humidity: value=64%
2017-07-20 03:09:02.215 Detail, Node005, Refreshed Value: old value=64, new value=64, type=decimal
2017-07-20 03:09:02.215 Detail, Node005, Changes to this value are not verified
2017-07-20 03:09:02.215 Detail, Node005, Notification: ValueChanged
2017-07-20 03:09:03.112 Detail, Node005,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x05, 0x03, 0x80, 0x03, 0x64, 0x13
2017-07-20 03:09:03.112 Detail, 
2017-07-20 03:09:03.112 Info, Node005, Received Battery report from node 5: level=100
2017-07-20 03:09:03.112 Detail, Node005, Refreshed Value: old value=100, new value=100, type=byte
2017-07-20 03:09:03.112 Detail, Node005, Changes to this value are not verified
2017-07-20 03:09:03.112 Detail, Node005, Notification: ValueChanged
2017-07-20 06:00:00.276 Info, Node010, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-07-20 06:00:00.277 Info, Node010, SwitchBinary::Set - Setting node 10 to On
2017-07-20 06:00:00.277 Detail, Node010, Queuing (Send) SwitchBinaryCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x25, 0x01, 0xff, 0x25, 0xf6, 0xe7
2017-07-20 06:00:00.277 Detail, Node010, Queuing (Send) SwitchBinaryCmd_Get (Node=10): 0x01, 0x09, 0x00, 0x13, 0x0a, 0x02, 0x25, 0x02, 0x25, 0xf7, 0x18
2017-07-20 06:00:00.277 Detail, 
2017-07-20 06:00:00.277 Info, Node010, Sending (Send) message (Callback ID=0xf6, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=10): 0x01, 0x0a, 0x00, 0x13, 0x0a, 0x03, 0x25, 0x01, 0xff, 0x25, 0xf6, 0xe7
2017-07-20 06:00:01.277 Error, Node010, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-20 06:00:01.277 Detail, Node010, Removing current message
2017-07-20 06:00:01.278 Detail, Node010, Notification: Notification - TimeOut
2017-07-20 06:00:01.281 Detail, 

What device do you have as Node10?

a AN157 Plug-in Appliance Module which I am looking to replace with a modified sonoff device

Based on the latest log you’ve posted, that device has timed out.
Try removing that device from your network and see if the issue still persists.

removed node 10 and happened again last night… last message from mode 5 again.

2017-07-21 02:15:26.688 Info, Node005, Received SensorMultiLevel report from node 5, instance 1, Temperature: value=22.2C
2017-07-21 02:15:26.688 Detail, Node005, Refreshed Value: old value=22.2, new value=22.2, type=decimal
2017-07-21 02:15:26.688 Detail, Node005, Changes to this value are not verified
2017-07-21 02:15:26.688 Detail, Node005, Notification: ValueChanged
2017-07-21 02:15:26.947 Detail, Node005,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x05, 0x05, 0x31, 0x05, 0x05, 0x01, 0x3f, 0xff
2017-07-21 02:15:26.947 Detail, 
2017-07-21 02:15:26.947 Info, Node005, Received SensorMultiLevel report from node 5, instance 1, Relative Humidity: value=63%
2017-07-21 02:15:26.947 Detail, Node005, Refreshed Value: old value=63, new value=63, type=decimal
2017-07-21 02:15:26.947 Detail, Node005, Changes to this value are not verified
2017-07-21 02:15:26.947 Detail, Node005, Notification: ValueChanged
2017-07-21 07:23:10.003 Info, mgr,     Manager::WriteConfig completed for driver with home ID of 0xd2a9fa3e
2017-07-21 07:23:11.014 Info, mgr,     Driver for controller /dev/zwave pending removal
2017-07-21 07:23:11.014 Detail, Notification: DriverRemoved
2017-07-21 07:23:11.014 Always, ***************************************************************************
2017-07-21 07:23:11.014 Always, *********************  Cumulative Network Statistics  *********************
2017-07-21 07:23:11.014 Always, *** General
2017-07-21 07:23:11.015 Always, Driver run time: . .  . 0 days, 22 hours, 46 minutes
2017-07-21 07:23:11.015 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 5810
2017-07-21 07:23:11.015 Always, Total messages successfully received: . . . . . . . . . . 5810
2017-07-21 07:23:11.015 Always, Total Messages successfully sent: . . . . . . . . . . . . 318
2017-07-21 07:23:11.015 Always, ACKs received from controller:  . . . . . . . . . . . . . 304
2017-07-21 07:23:11.015 Always, *** Errors
2017-07-21 07:23:11.015 Always, Unsolicited messages received while waiting for ACK:  . . 7
2017-07-21 07:23:11.015 Always, Reads aborted due to timeouts:  . . . . . . . . . . . . . 0
2017-07-21 07:23:11.015 Always, Bad checksum errors:  . . . . . . . . . . . . . . . . . . 0
2017-07-21 07:23:11.015 Always, CANs received from controller:  . . . . . . . . . . . . . 14
2017-07-21 07:23:11.015 Always, NAKs received from controller:  . . . . . . . . . . . . . 0
2017-07-21 07:23:11.015 Always, Out of frame data flow errors:  . . . . . . . . . . . . . 0
2017-07-21 07:23:11.016 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 13
2017-07-21 07:23:11.016 Always, Messages dropped and not delivered: . . . . . . . . . . . 25
2017-07-21 07:23:11.016 Always, ***************************************************************************
2017-07-21 07:23:13.094 Info, mgr,     Driver for controller /dev/zwave removed
2017-07-21 07:23:14.095 Error, mgr,     Manager::GetDriver failed - Home ID 0xd2a9fa3e is unknown
2017-07-21 07:23:14.095 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2017-07-21 07:23:14.095 Info, mgr,     GetSendQueueCount() failed - _homeId -760612290 not found

Sort of glad to see that others are experiencing the same issue. I have reported it on GitHub some time ago here: https://github.com/home-assistant/home-assistant/issues/7943 , but has not yet been resolved. The issue seems to go and come seemingly without any pattern. Sometimes I make a change and it goes away, for it to re-appear a few days later. I have no idea what debugging or logging I can do to trace the problem.

Trying to look for commonalities: My system is Hass.io on a Pi3. I have an MHZ19 sensor connected for CO2 monitoring and 2 temperature sensors (DS18B20). In my zwave system I have 2 Neo Coolcam power switches, a Fibaro switch and a Neo Coolcam motion sensor. That’s all. What do you guys have?

2 aeotec multisensor 6 (1 powered, 1 battery)
1 aeotec range extender
3 fibaro sensors
1 Aeotec DSC18103 Micro Smart Switch
1 Fibaro FGS212 Switch
1 Everspring AN157 Plug-in
1 GreenWave PowerNode 1 port
1 Aeotec ZW090 Z-Stick Gen5

I have factory reset the powered multisensor to see if that works, so we shall see.

All on a all-in-one on a RPi3 on wifi

I’m having an identical issue on the Aetec Gen5. Anyone find a solution or cause for this?

It seems to me that the problem is possibly induced by heavy data traffic in the zwave network. Perhaps the Pi3 USB buffer is not emtied quickly enough by HA and filling up and then the problem starts. To throttle the data flow I lowered the USB baudrate a few days ago and my zwave hasn’t crashed since. Perhaps others can try and report back? In the (Putty) terminal I give this command: stty -F /dev/ttyACM0 57600
Please note this doesn’t ‘stick’, you will need to do this after every reboot.

I think the z wave traffic is the issue. I reset my only powered sensor and changed a few settings so it reported back a lot less and it appears to be ok. I have been making changes and rebooting but, looks better. so far :slight_smile: