Same issue. My config is:
-RPI3
-AOI version 0.48.1
-Z-Stick Gen 5
-2 zwave switches (1 GE, 1 Leviton)
-1 motion sensor (Ecolink)
I don’t have any other hardware sensors
The switches (particularly the Leviton) keep going to ‘dead’ status.
How far away is your PI from the closest switch?
If that question is for me… Right now it’s about 5 feet (I have been testing before installing at the permanent location; when I’m done testing, it’ll be about 50 feet)
I’ve had great luck w/ the GE switches, is the Leviton Zwave+?
Hard to say anything odd show up in the OZW_Log ?
I have yet to have a Zwave device that just randomly dies.
Any news on this? Are you guys still having issues? In addition to the 0.48.1 I have an older 0.39.3 install. I moved the zstick to this one and it seems to be more stable (i.e., devices are not going to ‘dead’ status as far as I can tell from OZW_log.txt)
I ended up moving the stick away from the rack with a USB extension cable and the problems went away, so I guess this is just a range issue.
I wish it was as simple as that. My Pi in in the dining room and no thing else near it and it has started to happen again. Node 4 and 8 are both relay switches. any ideas please? 17 is a fibaro sensor…
2017-08-12 05:01:30.359 Info, Node017, Received SensorMultiLevel report from node 17, instance 1, Temperature: value=21.8C
2017-08-12 05:01:30.359 Detail, Node017, Refreshed Value: old value=21.9, new value=21.8, type=decimal
2017-08-12 05:01:30.359 Detail, Node017, Changes to this value are not verified
2017-08-12 05:01:30.360 Detail, Node017, Notification: ValueChanged
2017-08-12 07:32:47.112 Info, Node008, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-08-12 07:32:47.112 Info, Node008, SwitchBinary::Set - Setting node 8 to On
2017-08-12 07:32:47.112 Detail, Node008, Queuing (Send) SwitchBinaryCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x25, 0x01, 0xff, 0x25, 0xef, 0xfc
2017-08-12 07:32:47.112 Detail, Node008, Queuing (Send) SwitchBinaryCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x25, 0x02, 0x25, 0xf0, 0x1d
2017-08-12 07:32:47.112 Detail,
2017-08-12 07:32:47.112 Info, Node008, Sending (Send) message (Callback ID=0xef, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=8): 0x01, 0x0a, 0x00, 0x13, 0x08, 0x03, 0x25, 0x01, 0xff, 0x25, 0xef, 0xfc
2017-08-12 07:32:48.113 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-12 07:32:48.113 Detail, Node008, Removing current message
2017-08-12 07:32:48.113 Detail, Node008, Notification: Notification - TimeOut
2017-08-12 07:32:48.115 Detail,
2017-08-12 07:32:48.116 Info, Node008, Sending (Send) message (Callback ID=0xf0, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=8): 0x01, 0x09, 0x00, 0x13, 0x08, 0x02, 0x25, 0x02, 0x25, 0xf0, 0x1d
2017-08-12 07:32:49.116 Error, Node008, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-12 07:32:50.176 Detail, Node008, Removing current message
2017-08-12 07:32:50.176 Detail, Node008, Notification: Notification - TimeOut
2017-08-12 07:32:55.396 Info, Node004, Value::Set - COMMAND_CLASS_SWITCH_BINARY - Switch - 0 - 1 - True
2017-08-12 07:32:55.396 Info, Node004, SwitchBinary::Set - Setting node 4 to On
2017-08-12 07:32:55.396 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0xf1, 0xee
2017-08-12 07:32:55.396 Detail, Node004, Queuing (Send) SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0xf2, 0x13
2017-08-12 07:32:55.396 Detail,
2017-08-12 07:32:55.397 Info, Node004, Sending (Send) message (Callback ID=0xf1, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=4): 0x01, 0x0a, 0x00, 0x13, 0x04, 0x03, 0x25, 0x01, 0xff, 0x25, 0xf1, 0xee
2017-08-12 07:32:56.397 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-12 07:32:56.397 Detail, Node004, Removing current message
2017-08-12 07:32:56.397 Detail, Node004, Notification: Notification - TimeOut
2017-08-12 07:32:56.400 Detail,
2017-08-12 07:32:56.400 Info, Node004, Sending (Send) message (Callback ID=0xf2, Expected Reply=0x04) - SwitchBinaryCmd_Get (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x25, 0x02, 0x25, 0xf2, 0x13
2017-08-12 07:32:57.400 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-08-12 07:32:57.400 Detail, Node004, Removing current message
2017-08-12 07:32:57.400 Detail, Node004, Notification: Notification - TimeOut
Has anybody tried to lower the USB baudrate? It seems to work for me, haven’t had any time out’s since.
done, thanks… let’s see… tempted to ditch zwave but then I now have issues with Xiaomi, my wife is not amused 
it died 3 times yesterday… about 4-6 hours apart. changing the baud rate did nothing for me, as it crashed with out with out it working. HA still works, just Zwave doesn’t… I am starting to hate zwave.
Zwave uses radio signals, those can be blocked/reflected easily by many things, very similar to how a home WiFi setup would work. If your Zwave hub/stick isn’t in a central location you’re gonna have a bad day unless you have enough powered devices in range of the hub/stick to relay the commands.
2 Likes
mine is dead centre of the house ground floor and I have 5 powered devices (6 including a repeater) currently only 2 battery as I removed 2 to see if they caused problems… nope 55 minutes later, died again. Since removing the repeater… steady for wow 2 hours… early days still.
looks like the USB zwave device is disconnecting and not connecting back correctly. I have mine connect as a persistent name /dev/zwave
Anyone know how I fix this please?
Aug 14 01:48:52 HomeAssistant kernel: [33080.512784] usb 1-1.3: USB disconnect, device number 4
Aug 14 01:48:52 HomeAssistant hass[562]: #033[32m2017-08-14 01:48:52 INFO (Thread-3) [homeassistant.components.sensor.command_line] Running command: ping -W 1 -c 1 192.168.0.187 > /dev/null 2>&1 && echo success || echo fail#033[0m
Aug 14 01:48:52 HomeAssistant kernel: [33080.818498] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
Aug 14 01:48:53 HomeAssistant kernel: [33080.951724] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200
Aug 14 01:48:53 HomeAssistant kernel: [33080.951732] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 14 01:48:53 HomeAssistant kernel: [33080.952531] cdc_acm 1-1.3:1.0: ttyACM1: USB ACM device
Aug 14 01:48:53 HomeAssistant systemd-udevd[20137]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3 1 6': No such file or directory
Aug 14 01:48:53 HomeAssistant rsyslogd-2007: action 'action 17' suspended, next retry is Mon Aug 14 01:50:23 2017 [try http://www.rsyslog.com/e/2007 ]
Aug 14 01:48:53 HomeAssistant vncserver-x11[650]: AgentInitCheck: agent comms failure
Aug 14 01:48:56 HomeAssistant kernel: [33084.096718] usb 1-1.3: USB disconnect, device number 6
Aug 14 01:48:56 HomeAssistant kernel: [33084.398518] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
Aug 14 01:48:56 HomeAssistant kernel: [33084.528965] usb 1-1.3: device descriptor read/all, error -32
Aug 14 01:48:56 HomeAssistant kernel: [33084.628514] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
Aug 14 01:48:57 HomeAssistant kernel: [33085.158526] usb 1-1.3: new full-speed USB device number 9 using dwc_otg
Aug 14 01:48:57 HomeAssistant kernel: [33085.291723] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200
Aug 14 01:48:57 HomeAssistant kernel: [33085.291731] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 14 01:48:57 HomeAssistant kernel: [33085.297628] cdc_acm 1-1.3:1.0: ttyACM1: USB ACM device
Aug 14 01:48:57 HomeAssistant systemd-udevd[20142]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3 1 9': No such file or directory
Aug 14 01:48:57 HomeAssistant hass[562]: #033[32m2017-08-14 01:48:57 INFO (MainThread) [homeassistant.components.media_player.kodi] Unable to connect to Kodi via websocket#033[0m
Aug 14 01:48:58 HomeAssistant vncserver-x11[650]: AgentInitCheck: no response from agent
Aug 14 01:49:00 HomeAssistant kernel: [33088.704697] usb 1-1.3: USB disconnect, device number 9
Aug 14 01:49:01 HomeAssistant kernel: [33088.998553] usb 1-1.3: new full-speed USB device number 10 using dwc_otg
Aug 14 01:49:01 HomeAssistant kernel: [33089.538573] usb 1-1.3: device not accepting address 10, error -32
Aug 14 01:49:01 HomeAssistant kernel: [33089.868571] usb 1-1.3: new full-speed USB device number 12 using dwc_otg
Aug 14 01:49:02 HomeAssistant kernel: [33089.968563] usb 1-1.3: device descriptor read/64, error -32
Aug 14 01:49:02 HomeAssistant kernel: [33090.188575] usb 1-1.3: device descriptor read/64, error -32
Aug 14 01:49:02 HomeAssistant kernel: [33090.408573] usb 1-1.3: new full-speed USB device number 13 using dwc_otg
Aug 14 01:49:02 HomeAssistant kernel: [33090.508581] usb 1-1.3: device descriptor read/64, error -32
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.received_wlan0=601.7; friendly_name=Received wlan0, unit_of_measurement=MiB, icon=mdi:server-network @ 2017-08-14T01:48:31.774534+01:00>, entity_id=sensor.received_wlan0, new_state=<state sensor.received_wlan0=601.8; friendly_name=Received wlan0, unit_of_measurement=MiB, icon=mdi:server-network @ 2017-08-14T01:49:02.784890+01:00>>#033[0m
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.cpu_use=1; friendly_name=CPU Use, unit_of_measurement=%, icon=mdi:memory @ 2017-08-14T01:48:31.828213+01:00>, entity_id=sensor.cpu_use, new_state=<state sensor.cpu_use=10; friendly_name=CPU Use, unit_of_measurement=%, icon=mdi:memory @ 2017-08-14T01:49:02.804872+01:00>>#033[0m
Aug 14 01:49:02 HomeAssistant kernel: [33090.728618] usb 1-1.3: device descriptor read/64, error -32
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.ram_free=682.7; friendly_name=RAM Free, unit_of_measurement=MiB, icon=mdi:memory @ 2017-08-14T01:48:31.904288+01:00>, entity_id=sensor.ram_free, new_state=<state sensor.ram_free=682.2; friendly_name=RAM Free, unit_of_measurement=MiB, icon=mdi:memory @ 2017-08-14T01:49:02.855151+01:00>>#033[0m
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.since_last_boot=9:10:59.921136; friendly_name=Since Last Boot, unit_of_measurement=, icon=mdi:clock @ 2017-08-14T01:48:31.933988+01:00>, entity_id=sensor.since_last_boot, new_state=<state sensor.since_last_boot=9:11:30.866693; friendly_name=Since Last Boot, unit_of_measurement=, icon=mdi:clock @ 2017-08-14T01:49:02.883906+01:00>>#033[0m
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.ram_use_2=241.1; friendly_name=RAM Use, unit_of_measurement=MiB, icon=mdi:memory @ 2017-08-14T01:48:31.951093+01:00>, entity_id=sensor.ram_use_2, new_state=<state sensor.ram_use_2=241.6; friendly_name=RAM Use, unit_of_measurement=MiB, icon=mdi:memory @ 2017-08-14T01:49:02.901122+01:00>>#033[0m
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.sent_wlan0=499.7; friendly_name=Sent wlan0, unit_of_measurement=MiB, icon=mdi:server-network @ 2017-08-14T01:48:31.967026+01:00>, entity_id=sensor.sent_wlan0, new_state=<state sensor.sent_wlan0=499.8; friendly_name=Sent wlan0, unit_of_measurement=MiB, icon=mdi:server-network @ 2017-08-14T01:49:02.909198+01:00>>#033[0m
Aug 14 01:49:02 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:02 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.ram_free_2=681.2; friendly_name=RAM Free, unit_of_measurement=MiB, icon=mdi:memory @ 2017-08-14T01:48:31.995777+01:00>, entity_id=sensor.ram_free_2, new_state=<state sensor.ram_free_2=681.8; friendly_name=RAM Free, unit_of_measurement=MiB, icon=mdi:memory @ 2017-08-14T01:49:02.917100+01:00>>#033[0m
Aug 14 01:49:03 HomeAssistant kernel: [33091.308578] usb 1-1.3: new full-speed USB device number 15 using dwc_otg
Aug 14 01:49:03 HomeAssistant kernel: [33091.441846] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200
Aug 14 01:49:03 HomeAssistant kernel: [33091.441854] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 14 01:49:03 HomeAssistant kernel: [33091.442647] cdc_acm 1-1.3:1.0: ttyACM1: USB ACM device
Aug 14 01:49:03 HomeAssistant systemd-udevd[20149]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3 1 15': No such file or directory
Aug 14 01:49:03 HomeAssistant vncserver-x11[650]: AgentInitCheck: agent comms failure
Aug 14 01:49:03 HomeAssistant kernel: [33091.776703] usb 1-1.3: USB disconnect, device number 15
Aug 14 01:49:04 HomeAssistant kernel: [33092.068589] usb 1-1.3: new full-speed USB device number 16 using dwc_otg
Aug 14 01:49:04 HomeAssistant kernel: [33092.201848] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200
Aug 14 01:49:04 HomeAssistant kernel: [33092.201856] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 14 01:49:04 HomeAssistant kernel: [33092.202641] cdc_acm 1-1.3:1.0: ttyACM1: USB ACM device
Aug 14 01:49:04 HomeAssistant systemd-udevd[20152]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3 1 16': No such file or directory
Aug 14 01:49:05 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:05 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.dark_sky_cloud_coverage=59.0; friendly_name=Dark Sky Cloud Coverage, attribution=Powered by Dark Sky, unit_of_measurement=%, icon=mdi:weather-partlycloudy @ 2017-08-14T01:32:07.380491+01:00>, entity_id=sensor.dark_sky_cloud_coverage, new_state=<state sensor.dark_sky_cloud_coverage=60.0; friendly_name=Dark Sky Cloud Coverage, attribution=Powered by Dark Sky, unit_of_measurement=%, icon=mdi:weather-partlycloudy @ 2017-08-14T01:49:05.111825+01:00>>#033[0m
Aug 14 01:49:05 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:05 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: old_state=<state sensor.dark_sky_summary=Partly Cloudy; friendly_name=Dark Sky Summary, entity_picture=/static/images/darksky/weather-cloudy.svg, attribution=Powered by Dark Sky @ 2017-08-14T00:56:53.898259+01:00>, entity_id=sensor.dark_sky_summary, new_state=<state sensor.dark_sky_summary=Mostly Cloudy; friendly_name=Dark Sky Summary, entity_picture=/static/images/darksky/weather-cloudy.svg, attribution=Powered by Dark Sky @ 2017-08-14T01:49:05.129052+01:00>>#033[0m
Aug 14 01:49:08 HomeAssistant vncserver-x11[650]: AgentInitCheck: no response from agent
Aug 14 01:49:08 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:08 INFO (MainThread) [homeassistant.components.media_player.kodi] Unable to connect to Kodi via websocket#033[0m
Aug 14 01:49:13 HomeAssistant vncserver-x11[650]: AgentInitCheck: agent comms failure
Aug 14 01:49:18 HomeAssistant vncserver-x11[650]: AgentInitCheck: no response from agent
Aug 14 01:49:19 HomeAssistant hass[562]: #033[32m2017-08-14 01:49:19 INFO (MainThread) [homeassistant.components.media_player.kodi] Unable to connect to Kodi via websocket#033[0m
Aug 14 01:49:23 HomeAssistant vncserver-x11[650]: AgentInitCheck: agent comms failure
Aug 14 01:49:28 HomeAssistant vncserver-x11[650]: AgentInitCheck: no response from agent
It could be:
- An underpowered power supply (it can claim 2A, or 3A, but many don’t live up to their claims, or don’t provide a consistent supply)
- A faulty stick
- An overloaded Pi - what else is it doing?
it was happening and I just got a new 3A and it is still the same, so scratch that off I think.
Faulty Stick - last resort hopefully
what else? - not much to be honest. I did have mysql running but not used, so removed that and removed some HA config options I liked but don’t need as such.
I noticed I was getting a boat load of these… so disabled it
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
Aug 14 05:00:30 HomeAssistant avahi-daemon[443]: Received packet from invalid interface.
bugger dies again after 24 minutes…
Aug 14 12:38:20 HomeAssistant kernel: [ 6680.294733] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
Aug 14 12:38:20 HomeAssistant kernel: [ 6680.428027] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200
Aug 14 12:38:20 HomeAssistant kernel: [ 6680.428036] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 14 12:38:20 HomeAssistant kernel: [ 6680.428823] cdc_acm 1-1.3:1.0: ttyACM1: USB ACM device
Aug 14 12:38:20 HomeAssistant systemd-udevd[2895]: failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3 1 6': No such file or directory
[Disclaimer] I’m VERY new to HA and Zwave, so take what I say with a grain of salt.
I’ve been having Zwave issues. After much testing, adding/removing devices (I only have 3, plus the zstick), and playing with entity IDs the zwave network seemed to work but VERY slow. Yesterday I stopped HA and run OZWCP; it showed that one of the devices was in ‘dead’ status (despite being able to toggle on/off though HA -response time to the toggle was sloooow, though).
Using OZWCP I removed said device; then restored the device to factory default; then added it again with HA ‘add node’ button from zwave control panel. It seems to be working ok for the last 20 or so hours.
Hope this might help.
@MarkR I not so sure about the power issue. You use a raspberry pi or? How many other devices do you have connected to it. Because it can be, that they all together drain too much energy.