Nodes timing out and weird behaviour

Hardware
1

I have a Z-Wave.Me ZME_UZB1 USB Stick, it is an AU one (since I am in Australia).

I have 29 nodes in my network covering a 5 bedroom house and I am having trouble with my Goap Flush 2 Z-Wave Double Relay.

The symptoms seem to be:

  • Some lights will turn back on automatically after switching them off manually.
  • my zwave network takes 7 or so minutes to start up with a HASS restart.
  • you will turn them off or an automation will turn them off but they will remain on in the interface.
  • sometimes nodes just won’t work, eg. I have a button the button at night should shut the house down for bed/sleeping.
  • some nodes are turning up dead for no reason… and I have to remove and readd.

Last night a whole bunch of lights and things did not work. After reviewing the logs this morning at that time I see a lot of :

2018-01-12 22:35:36.785 Info, Node017, Sending (Send) message (Callback ID=0xf2, Expected Reply=0x13) - SwitchBinaryCmd_Set (Node=17): 0x01, 0x0a, 0x00, 0x13, 0x11, 0x03, 0x25, 0x01, 0xff, 0x25, 0xf2, 0xf8
2018-01-12 22:35:37.786 Error, Node017, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-01-12 22:35:37.792 Detail, Node017, Removing current message
2018-01-12 22:35:37.792 Detail, Node017, Notification: Notification - TimeOut

I have narrowed down to this switch because it is the only type of node giving the time out regularly.

2018-01-13 08:31:59.698 Error, Node039, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-01-13 08:31:59.698 Detail, Node039, Removing current message
2018-01-13 08:31:59.699 Detail, Node039, Notification: Notification - TimeOut
2018-01-13 08:31:59.711 Detail,
2018-01-13 08:31:59.712 Info, Node039, Sending (Send) message (Callback ID=0x63, Expected Reply=0x04) - MultiChannel Encapsulated (instance=2): SwitchBinaryCmd_Get (Node=39): 0x01, 0x0d, 0x00, 0x13, 0x27, 0x06, 0x60, 0x0d, 0x01, 0x01, 0x25, 0x02, 0x25, 0x63, 0xcc
2018-01-13 08:31:59.720 Detail, Node039,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-01-13 08:31:59.720 Detail, Node039,   ZW_SEND_DATA delivered to Z-Wave stack
2018-01-13 08:31:59.783 Detail, Node039,   Received: 0x01, 0x07, 0x00, 0x13, 0x63, 0x00, 0x00, 0x07, 0x8f
2018-01-13 08:31:59.783 Detail, Node039,   ZW_SEND_DATA Request with callback ID 0x63 received (expected 0x63)
2018-01-13 08:31:59.784 Info, Node039, Request RTT 71 Average Request RTT 73
2018-01-13 08:31:59.784 Detail,   Expected callbackId was received
2018-01-13 08:32:09.712 Error, Node039, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-01-13 08:32:09.712 Detail, Node039, Removing current message
2018-01-13 08:32:09.713 Detail, Node039, Notification: Notification - TimeOut
2018-01-13 08:32:09.724 Detail,
2018-01-13 08:32:09.724 Info, Node039, Sending (Send) message (Callback ID=0x64, Expected Reply=0x04) - MultiChannel Encapsulated (instance=3): SwitchBinaryCmd_Get (Node=39): 0x01, 0x0d, 0x00, 0x13, 0x27, 0x06, 0x60, 0x0d, 0x01, 0x02, 0x25, 0x02, 0x25, 0x64, 0xc8
2018-01-13 08:32:09.733 Detail, Node039,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2018-01-13 08:32:09.734 Detail, Node039,   ZW_SEND_DATA delivered to Z-Wave stack
2018-01-13 08:32:09.794 Detail, Node039,   Received: 0x01, 0x07, 0x00, 0x13, 0x64, 0x00, 0x00, 0x07, 0x88
2018-01-13 08:32:09.794 Detail, Node039,   ZW_SEND_DATA Request with callback ID 0x64 received (expected 0x64)
2018-01-13 08:32:09.794 Info, Node039, Request RTT 69 Average Request RTT 71
2018-01-13 08:32:09.794 Detail,   Expected callbackId was received
2018-01-13 08:32:09.864 Detail, Node039,   Received: 0x01, 0x0d, 0x00, 0x04, 0x00, 0x27, 0x07, 0x60, 0x0d, 0x02, 0x01, 0x25, 0x03, 0x00, 0x9e
2018-01-13 08:32:09.864 Detail,
2018-01-13 08:32:09.864 Info, Node039, Response RTT 139 Average Response RTT 387
2018-01-13 08:32:09.865 Info, Node039, Received a MultiChannelEncap from node 39, endpoint 2 for Command Class COMMAND_CLASS_SWITCH_BINARY
2018-01-13 08:32:09.865 Info, Node039, Received SwitchBinary report from node 39: level=Off
2018-01-13 08:32:09.865 Detail, Node039, Refreshed Value: old value=true, new value=false, type=bool
2018-01-13 08:32:09.865 Detail, Node039, Changes to this value are not verified
2018-01-13 08:32:09.865 Detail, Node039,   Expected reply and command class was received
2018-01-13 08:32:09.865 Detail, Node039,   Message transaction complete
2018-01-13 08:32:09.865 Detail,
2018-01-13 08:32:09.866 Detail, Node039, Removing current message
2018-01-13 08:32:09.866 Detail, Node039, Notification: ValueChanged

https://hastebin.com/zuvifapeda.vbs

I ran through a network heal and then a network test with Tinkerer from discord,… The heal works fine but for the test all of the nodes that failed last night responded with a timeout and dump. I tried a stop/start inside HASS but on the start I ended up with two of everything node in HASS. I restarted HASS to reset it to a clean state which while still having the timeouts it mostly works but over time it will degraded more and more… Any thoughts?

Thanks

2

Hi @jurgenweber,
I have similar problems with hass.io and Aeon Z-stick on a Raspberry Pi3. There seem to be limited knowledge about this in the forums, because I haven’t received much response to my thread here.

My z-wave network started acting up a few weeks ago, but only in the past few days it has more or less stopped responding completely.

I am trying all sorts of things, restarting, rebooting etc. but always the same and initialization of z-wave usually takes 15-20 minutes or more! When all nodes report as “ready”, they don’t respond to commands and show the wrong state in HA. Occasionally, a command slips through and does something, but that’s rare. My OSW_Log.txt also grows to grotesque proportions, could be several MBs after less than an hour.

I also rolled back to a previous hass.io snapshot to see if it could be config or upgrade related, but it doesn’t appear to be the case as problem persists.

I am thinking that the z-stick hardware might be broken somehow. I managed to back up the eprom on it and consider buying another one and restore the data to see if there’s a difference.

3

TBH I do not thing they are related. I have found when these troubles occur my nodes have the folowing error:

2018-02-21 19:32:58.646 Error, Node028, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-21 19:32:59.430 Error, Node028, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2018-02-21 19:33:15.231 Error, Node019, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-21 19:51:19.582 Error, Node028, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-21 19:59:04.479 Error, Node028, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-21 19:59:05.492 Error, Node028, ERROR: Dropping command, expected response not received after 1 attempt(s)
2018-02-21 19:59:06.009 Error, Node019, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2018-02-21 19:59:06.014 Error, Node019, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2018-02-21 19:59:15.513 Error, Node019, ERROR: Dropping command, expected response not received after 2 attempt(s)

I am still experiencing this even thou upgraded to the latest HASS version last night. Some commands are just disappearing.

4

Yes, I am still getting some of these errors, but the operation of my z-wave network is like night and day compared to when I had the NodOn smart plugs included. After contacting the reseller I got the following suggestion on NodOn:

Try changing Parameters 21 and 23 to “0”, and make sure parameter 24 is 3600. You can also try setting parameter 24 to 0. Some of these should cause the problem.

Haven’t tried that yet though.

5

Interesting, with more discord discussions it has been recommended to me that I remove ‘non zwave plus’ devices from my network (I only have a few) and run a pure ‘zwave plus’ network.

I am trying that now and I will report back how it goes in the next few days.

6

mine is a lot better since removing the non ‘plus’ components.