Troubleshooting Z-Wave devices going offline

My z-wave devices have been all working without a hitch except for two. They are both the same model device, and the only two of which I have in the network. I’m not sure if they are just junk, or if something else is at play.

They are Aeotec brand Micro Switch G2
Model number: DSC26103-ZWUS
Link: https://www.amazon.com/gp/product/B06Y23DYWV/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

I parced through the debug logs the best I could in attempts to find the relivant info while weeding out the excess. Here are a couple examples of what is going on in the logs leading up to them going offline, I included one for each device. (Node 7 and 12)

16-Jan-2018 13:48:57.032 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 7A 01 92 
16-Jan-2018 13:48:57.038 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
16-Jan-2018 13:48:57.042 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 7A 01 00 00 90 
16-Jan-2018 13:48:57.044 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 7A 01 00 00 90 
16-Jan-2018 13:48:57.047 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=7A 01 
16-Jan-2018 13:48:57.048 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 12: SendData Request. CallBack ID = 122, Status = Transmission complete, no ACK received(1)
16-Jan-2018 13:48:57.050 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 12: Node is DEAD.
16-Jan-2018 13:48:57.051 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
16-Jan-2018 13:48:57.052 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveNodeStatusEvent
16-Jan-2018 13:48:57.054 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 12: Setting OFFLINE
16-Jan-2018 13:48:57.061 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - NODE 12: Node Status event - Node is DEAD
16-Jan-2018 13:48:57.063 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 12: Node is DEAD. Dropping message.
16-Jan-2018 13:48:57.065 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
16-Jan-2018 13:48:57.067 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 12: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
16-Jan-2018 13:48:57.068 [DEBUG] [.internal.protocol.ZWaveController$ZWaveSendThread] - NODE 12: Response processed after 4129ms/4403ms.


16-Jan-2018 13:52:01.951 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 05 00 13 85 01 6D 
16-Jan-2018 13:52:01.954 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
16-Jan-2018 13:52:01.956 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 13 85 01 00 00 6F 
16-Jan-2018 13:52:01.958 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 07 00 13 85 01 00 00 6F 
16-Jan-2018 13:52:01.960 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=85 01 
16-Jan-2018 13:52:01.961 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 7: SendData Request. CallBack ID = 133, Status = Transmission complete, no ACK received(1)
16-Jan-2018 13:52:01.962 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 7: Node is DEAD.
16-Jan-2018 13:52:01.964 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeStatusEvent
16-Jan-2018 13:52:01.965 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveNodeStatusEvent
16-Jan-2018 13:52:01.966 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Setting OFFLINE
16-Jan-2018 13:52:01.972 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - NODE 7: Node Status event - Node is DEAD
16-Jan-2018 13:52:01.976 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 7: Node is DEAD. Dropping message.
16-Jan-2018 13:52:01.977 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
16-Jan-2018 13:52:01.979 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

Not sure if that is helpful or not, as I said, I’m just using self-educated guesses on what inforamtion is useful and what is not. Can anyone here gather anything from those who examples? Are there other parts of the debug logs that would be more useful for troubleshooting something like this?

The only other thing I found that was suspect is that when I searched the logs for the word “error” it only showed up in lines pertaining to nodes 12 and 7, the two that I have been having trouble with. The only thing is that they dont really seem to be getting logged when they are going offline. These messages are also much more common then the offline ones. Since I’m on the fence of them even being relevant I will only include a small example.

8961:15-Jan-2018 12:47:35.103 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=16, expected=ApplicationCommandHandler, cancelled=false      MISMATCH
8962:15-Jan-2018 12:47:40.070 [DEBUG] [.internal.protocol.ZWaveController$ZWaveSendThread] - NODE 7: Timeout while sending message. Requeueing - 1 attempts left!
8963:15-Jan-2018 12:47:40.070 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 7: Got an error while sending data. Resending message.

Any pointers would be much appreciated.

I have a dsc26103-zweu (Aeon micro switch) and it was working fine before I upgraded to OH 2.4. After the upgrade, the device is shown as “Unknown Device” (the rest of my z-wave devices, over 30 of them, are working fine after the upgrade), I have woken it to no avail, any ideas? The device shows connections to peers.

Thanks