Aeon USB stick crashing?

Configuration Z-Wave
1

Hello,

I’ve had my usb stick for a few days and it appears to be failing (going to sleep) every night at midnight. Any idea what is going on please? I have to reboot to get it to work again. this is from the log file. My Fibaro latest version has always reported 0 battery, cannot get it to report.

2017-01-30 22:47:03.818 Info, Node002, Received Battery report from node 2: level=0
2017-01-30 22:47:03.818 Detail, Node002, Refreshed Value: old value=0, new value=0, type=byte
2017-01-30 22:47:03.818 Detail, Node002, Changes to this value are not verified
2017-01-30 22:47:03.818 Detail, Node002, Notification: ValueChanged
2017-01-31 00:00:00.504 Detail, Node001, Queuing (Controller) Request Node Neighbor Update
2017-01-31 00:00:00.505 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2017-01-31 00:00:00.508 Info, Requesting Neighbor Update for node 1
2017-01-31 00:00:00.509 Detail, Node001, Queuing (Command) ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x21, 0x92
2017-01-31 00:00:00.509 Detail, Notification: ControllerCommand - Starting
2017-01-31 00:00:00.509 Detail,
2017-01-31 00:00:00.509 Info, Node001, Sending (Command) message (Callback ID=0x21, Expected Reply=0x48) - ControllerCommand_RequestNodeNeighborUpdate (Node=1): 0x01, 0x05, 0x00, 0x48, 0x01, 0x21, 0x92
2017-01-31 00:00:01.509 Error, Node001, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-01-31 00:00:01.510 Detail, Node001, Removing current message
2017-01-31 00:00:01.510 Detail, Node001, Notification: Notification - TimeOut
2017-01-31 00:00:01.510 Detail, Notification: ControllerCommand - Error - Failed
2017-01-31 00:00:01.510 Info, Requesting Neighbor Update for node 2
2017-01-31 00:00:01.510 Detail,
2017-01-31 00:00:01.510 Detail, Node002, Queuing (Controller) Request Node Neighbor Update
2017-01-31 00:00:01.510 Detail, Notification: ControllerCommand - Starting
2017-01-31 00:00:01.511 Detail, Notification: ControllerCommand - Sleeping
2017-01-31 07:44:12.650 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd0bcfe3f
2017-01-31 07:44:13.654 Info, mgr, Driver for controller /dev/ttyACM0 pending removal
2017-01-31 07:44:13.654 Detail, Notification: DriverRemoved
2017-01-31 07:44:13.654 Always, ***************************************************************************
2017-01-31 07:44:13.654 Always, ********************* Cumulative Network Statistics *********************
2017-01-31 07:44:13.654 Always, *** General
2017-01-31 07:44:13.655 Always, Driver run time: . . . 0 days, 13 hours, 59 minutes
2017-01-31 07:44:13.655 Always, Frames processed: . . . . . . . . . . . . . . . . . . . . 345
2017-01-31 07:44:13.655 Always, Total messages successfully received: . . . . . . . . . . 345
2017-01-31 07:44:13.655 Always, Total Messages successfully sent: . . . . . . . . . . . . 35
2017-01-31 07:44:13.655 Always, ACKs received from controller: . . . . . . . . . . . . . 34
2017-01-31 07:44:13.655 Always, *** Errors
2017-01-31 07:44:13.655 Always, Unsolicited messages received while waiting for ACK: . . 0
2017-01-31 07:44:13.655 Always, Reads aborted due to timeouts: . . . . . . . . . . . . . 0
2017-01-31 07:44:13.655 Always, Bad checksum errors: . . . . . . . . . . . . . . . . . . 0
2017-01-31 07:44:13.655 Always, CANs received from controller: . . . . . . . . . . . . . 0
2017-01-31 07:44:13.655 Always, NAKs received from controller: . . . . . . . . . . . . . 0
2017-01-31 07:44:13.655 Always, Out of frame data flow errors: . . . . . . . . . . . . . 0
2017-01-31 07:44:13.655 Always, Messages retransmitted: . . . . . . . . . . . . . . . . . 0
2017-01-31 07:44:13.655 Always, Messages dropped and not delivered: . . . . . . . . . . . 1
2017-01-31 07:44:13.655 Always, ***************************************************************************
2017-01-31 07:44:15.668 Info, mgr, Driver for controller /dev/ttyACM0 removed
2017-01-31 07:44:16.669 Error, mgr, Manager::GetDriver failed - Home ID 0xd0bcfe3f is unknown
2017-01-31 07:44:16.669 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2017-01-31 07:44:16.669 Info, mgr, GetSendQueueCount() failed - _homeId -792920513 not found

2

will probably need more info before we can help like what hardware, os etc.

From my experience and from talking to others the Aeotec hardware is usually pretty good so I don’t think the problem is hardware related could be OS.

Aeotec support is excellent should you need to escalate.

3

good point it is a new build on a RPi3 using the all in one installer. Not sure what else to provide?

4

thats odd. I have been the running the USB stick Gen 5 for close to a year and the only time I had problems is when I was running the stick on a Win7 VM (windows likes to reserve power and shuts the USB port down) however I don’t think your problem is related to this as I haven’t heard anyone have problems with Rpi.

You don’t have anything else running on the pi? that could be affecting the USB port.

Maybe it is power related, are you sure has the correct rating see link.

Maybe firmware upgrade the stick?

5

interesting about the power… will try a higher powered adapter, but odd it happens at midnight. Thanks!

6

Midnight is when the auto heal runs and judging from the logs this is what is running. Give it a try from the services menu to run zwave → heal and see whether it fails again. If it does - replace the power supply with a 2Amp one and run zwave → heal again and see whether the better power supply fixes the issue.

7

Does the /dev/ttyACM device perhaps switch from ACM0 to ACM1 or vice versa during reset/heal?

Domoticz has a nice write up on how to make a persistent USB device path in /dev:

https://www.domoticz.com/wiki/PersistentUSBDevices

8

thanks guys I think that has done it… got a 2.5a power adapter and had already set it to use /dev/zwave as it was flipping after a reboot. Looking good so far. Just need to get my sensor scripts working now :smiley: