2.5.3 Z-wave - thing receives a command, mostly does it, then goes offline

psyciknz · June 24, 2020, 4:09am

So I have a couple of aeotec smart switches… As the crow flies one is about 3m from the controller, another maybe 5.

They both seem to maintain a direct connection to the controller. But it seems after sending a command (ie they’ve both just been told to turn on at sunset as they have lamps on them) then they go offline. Maybe coming back if 30 mins to an hour).

I wonder if they’re at a weird limit for communication. Is there a way i can lower their transmit power so they route though something else? or anything else I can do? I could alter the aeotec stick slightly and move it…and if I really want to I can put it in a rack

Bruce_Osborne · June 24, 2020, 11:40am

Does openHAB discover any zombie nodes on the network that do not really exist? That can mess up Z-Wave routing.

psyciknz · June 24, 2020, 7:12pm

No I’ve cleaned those previously.

I’ve seen a bunch of documentation that the inclusion order of nodes can have an effect, in that it likes routing through lower number nodes first. So mine are added in order or when I can physically install them, not in order of distance to the zwave controller.

But I’m not overly keen on starting my network from scratch to reorder the nodes in a slightly better order.
Pity I can’t just swap a couple of node ids around based on distance.

Bruce_Osborne · June 24, 2020, 9:07pm

I doubt node id numbers make a difference. @chris should know for sure.

chris · June 24, 2020, 10:53pm

I don’t believe that the node number will make any difference to routing. The routing is a simple list of node numbers that’s sent in each frame and it won’t depend on the node ID “order” (ie lower node numbers won’t have some sort of higher priority than higher nodes).

psyciknz · June 25, 2020, 12:01am

maybe it was just someone speculating that node order played a part in routing preference

psyciknz · June 25, 2020, 6:53pm

Still not helping me get this node online though. It seems to refuse to run through other nodes, and tried hitting the controller directly and struggling.

Bruce_Osborne · June 25, 2020, 8:00pm

Are you sure the device is waking up? I have a sensor where the manufacturer’s directions for waking up do not work.
The log should show the device being waked up. I do not recall is debug needs to be turned on for that though.

psyciknz · June 25, 2020, 8:07pm

It’s an aeotec nano switch…as far as I know power devices don’t do a wake up do they?

It’s showing as online now, but any attempt to heal or reinitialise or delete/add don’t seem to resolve it.

Can not start heal as initialisation is not complete (DELETE_SUC_ROUTES)

And I can’t force it to use an intermediary for routing. It’s almost like a need to drop its transmit power just a little, so it can’t see the controller directly.

chris · June 25, 2020, 8:27pm

Have you looked in the debug log to see what is happening? Probably there’s an issue with the device not responding, but maybe it’s something else - the log should provide a lot of insight into what’s happening.

Bruce_Osborne · June 25, 2020, 8:40pm

2.5.3 was released in March. Those devices in our database were updated early May. Please either upgrade openHAB or, at a minimum, update the Z-Wave binding.

Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community

psyciknz · June 26, 2020, 1:17am

So I updated to 2.5.6 today. No change to node 19.

I just see a lot of red for it. So this is from a restart. 19 was existing before the restart. But if I delete it and add it, no change. I have all this as a log file. Its 8mb. I’d been playing with moving the controller around, just trying to get it to pick up 19, but nothing seemed to help.

psyciknz · June 26, 2020, 1:19am

Or maybe this is a better format.

psyciknz · June 26, 2020, 1:25am

Ahh this time it’s actually completed figuring out what it is…but seems to be sitting offline…quite often does this. And then it might come back online in an hour or so, and so I’ll try to heal it to get a neighbour update.

psyciknz · June 26, 2020, 1:42am

So it’s already come back online which is good. So I’ve fired an On Command to it, which just tries and tries and tires.

psyciknz · June 26, 2020, 7:05am

2020-06-26 18:58:32.699 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Command received zwave:device:a5365e91:node19:switch_binary --> OFF [OnOffType]
2020-06-26 18:58:32.700 [DEBUG] [rotocol.commandclass.ZWaveBinarySwitchCommandClass] - NODE 19: Creating new message for application command SWITCH_BINARY_SET
2020-06-26 18:58:32.701 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: SECURITY not supported
2020-06-26 18:58:32.701 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Command Class COMMAND_CLASS_SWITCH_BINARY is NOT required to be secured
2020-06-26 18:58:32.701 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Adding to device queue
2020-06-26 18:58:32.701 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Added 867 to queue - size 1
2020-06-26 18:58:32.703 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 25 01 00 25 D8 2F
2020-06-26 18:58:32.705 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Polling initialised at 86400 seconds - start in 15000 milliseconds.
2020-06-26 18:58:32.710 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: sentData successfully placed on stack.
2020-06-26 18:58:32.710 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 867: Transaction not completed
2020-06-26 18:58:34.147 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Command received zwave:device:a5365e91:node19:switch_binary --> ON [OnOffType]
2020-06-26 18:58:34.147 [DEBUG] [rotocol.commandclass.ZWaveBinarySwitchCommandClass] - NODE 19: Creating new message for application command SWITCH_BINARY_SET
2020-06-26 18:58:34.147 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: SECURITY not supported
2020-06-26 18:58:34.147 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Command Class COMMAND_CLASS_SWITCH_BINARY is NOT required to be secured
2020-06-26 18:58:34.147 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Adding to device queue
2020-06-26 18:58:34.147 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Added 868 to queue - size 1
2020-06-26 18:58:34.148 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Polling initialised at 86400 seconds - start in 15000 milliseconds.
2020-06-26 18:58:37.711 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 19: TID 867: Timeout at state WAIT_REQUEST. 3 retries remaining.
2020-06-26 18:58:48.730 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 216, Status = Transmission complete, no ACK received(1)
2020-06-26 18:58:48.730 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 18:58:48.731 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: CANCEL while sending message. Requeueing - 2 attempts left!
2020-06-26 18:58:48.731 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Adding to device queue
2020-06-26 18:58:48.731 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Added 867 to queue - size 2
2020-06-26 18:58:48.731 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 25 01 00 25 D9 2E
2020-06-26 18:58:48.732 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 867: Transaction not completed
2020-06-26 18:58:48.740 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: sentData successfully placed on stack.
2020-06-26 18:58:48.740 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 867: Transaction not completed
2020-06-26 18:58:49.148 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Polling...
2020-06-26 18:58:49.148 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Polling deferred until initialisation complete
2020-06-26 18:58:53.740 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 19: TID 867: Timeout at state WAIT_REQUEST. 2 retries remaining.
2020-06-26 18:59:04.486 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 217, Status = Transmission complete, no ACK received(1)
2020-06-26 18:59:04.487 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 18:59:04.487 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: CANCEL while sending message. Requeueing - 1 attempts left!
2020-06-26 18:59:04.487 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Adding to device queue
2020-06-26 18:59:04.487 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Added 867 to queue - size 2
2020-06-26 18:59:04.488 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 25 01 00 25 DA 2D
2020-06-26 18:59:04.489 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 867: Transaction not completed
2020-06-26 18:59:04.497 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: sentData successfully placed on stack.
2020-06-26 18:59:04.497 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 867: Transaction not completed
2020-06-26 18:59:09.497 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 19: TID 867: Timeout at state WAIT_REQUEST. 1 retries remaining.
2020-06-26 18:59:20.306 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 218, Status = Transmission complete, no ACK received(1)
2020-06-26 18:59:20.306 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 18:59:20.306 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Retry count exceeded. Discarding message: TID 867: [CANCELLED] priority=Set, requiresResponse=true, callback: 218
2020-06-26 18:59:20.306 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2020-06-26 18:59:20.306 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Setting OFFLINE
2020-06-26 18:59:20.307 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - NODE 19: Node Status event - Node is DEAD
2020-06-26 18:59:20.307 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Node is DEAD.
2020-06-26 18:59:20.307 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2020-06-26 18:59:20.307 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Setting OFFLINE
2020-06-26 18:59:20.307 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - NODE 19: Node Status event - Node is DEAD
2020-06-26 18:59:20.307 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 867: Transaction completed
2020-06-26 18:59:20.308 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: notifyTransactionResponse TID:867 CANCELLED
2020-06-26 18:59:20.308 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 18:59:20.308 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 25 01 FF 25 DB D3
2020-06-26 18:59:20.317 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: sentData successfully placed on stack.
2020-06-26 18:59:20.318 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 868: Transaction not completed
2020-06-26 18:59:25.317 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 19: TID 868: Timeout at state WAIT_REQUEST. 3 retries remaining.
2020-06-26 18:59:36.144 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 219, Status = Transmission complete, no ACK received(1)
2020-06-26 18:59:36.145 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 18:59:36.145 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: CANCEL while sending message. Requeueing - 2 attempts left!
2020-06-26 18:59:36.145 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Adding to device queue
2020-06-26 18:59:36.145 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Added 868 to queue - size 1
2020-06-26 18:59:36.146 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 25 01 FF 25 DC D4
2020-06-26 18:59:36.146 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 868: Transaction not completed
2020-06-26 18:59:36.155 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: sentData successfully placed on stack.
2020-06-26 18:59:36.155 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 868: Transaction not completed
2020-06-26 18:59:41.155 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 19: TID 868: Timeout at state WAIT_REQUEST. 2 retries remaining.
2020-06-26 18:59:52.013 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 220, Status = Transmission complete, no ACK received(1)
2020-06-26 18:59:52.013 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 18:59:52.014 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: CANCEL while sending message. Requeueing - 1 attempts left!
2020-06-26 18:59:52.014 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Adding to device queue
2020-06-26 18:59:52.014 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Added 868 to queue - size 1
2020-06-26 18:59:52.014 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 19: Sending REQUEST Message = 01 0A 00 13 13 03 25 01 FF 25 DD D5
2020-06-26 18:59:52.015 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 868: Transaction not completed
2020-06-26 18:59:52.023 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: sentData successfully placed on stack.
2020-06-26 18:59:52.023 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 868: Transaction not completed
2020-06-26 18:59:57.023 [DEBUG] [ocol.ZWaveTransactionManager$ZWaveTransactionTimer] - NODE 19: TID 868: Timeout at state WAIT_REQUEST. 1 retries remaining.
2020-06-26 19:00:07.801 [DEBUG] [ternal.protocol.serialmessage.SendDataMessageClass] - NODE 19: SendData Request. CallBack ID = 221, Status = Transmission complete, no ACK received(1)
2020-06-26 19:00:07.802 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 19:00:07.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Retry count exceeded. Discarding message: TID 868: [CANCELLED] priority=Set, requiresResponse=true, callback: 221
2020-06-26 19:00:07.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: TID 868: Transaction completed
2020-06-26 19:00:07.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: notifyTransactionResponse TID:868 CANCELLED
2020-06-26 19:00:07.803 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-06-26 19:01:43.264 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (DEAD:DELETE_SUC_ROUTES)
2020-06-26 19:01:43.264 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2020-06-26 19:01:43.264 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Setting ONLINE
2020-06-26 19:01:43.265 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - NODE 19: Node Status event - Node is ALIVE
2020-06-26 19:01:43.265 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Node is ALIVE. Init stage is DELETE_SUC_ROUTES.
2020-06-26 19:01:43.266 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2020-06-26 19:01:43.266 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Setting ONLINE
2020-06-26 19:01:43.266 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - NODE 19: Node Status event - Node is ALIVE
2020-06-26 19:01:43.266 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Incoming command class COMMAND_CLASS_METER, endpoint 0
2020-06-26 19:01:43.266 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: SECURITY not supported
2020-06-26 19:01:43.266 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 19: Received COMMAND_CLASS_METER V3 METER_REPORT
2020-06-26 19:01:43.266 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 19: Meter: Type=Electric(1), Scale=W(2), Value=0E+1
2020-06-26 19:01:43.267 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveMeterValueEvent
2020-06-26 19:01:43.267 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_METER, value=0E+1
2020-06-26 19:01:43.267 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Updating channel state zwave:device:a5365e91:node19:meter_watts to 0 [DecimalType]
2020-06-26 19:01:43.267 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Commands processed 1.
2020-06-26 19:01:43.268 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3b9d398a.
2020-06-26 19:01:59.057 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-06-26 19:01:59.057 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Incoming command class COMMAND_CLASS_HAIL, endpoint 0
2020-06-26 19:01:59.057 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: SECURITY not supported
2020-06-26 19:01:59.057 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 19: Received COMMAND_CLASS_HAIL V1 HAIL
2020-06-26 19:01:59.057 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Commands processed 1.

so what i tend to see is that the device will send a meter report, openhad will class it as awake, until you try and send something to it, where it will go offline again.

it doesnt seem to complete the command

psyciknz · June 26, 2020, 9:42am

I’m getting power reports from it now. but i had to manually turn it on. but nothing i send to it via opehab seems to get there.

    2020-06-26 21:38:03.296 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-06-26 21:38:05.862 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 13 0A 32 02 21 74 00 00 0C 13 00 00 88
2020-06-26 21:38:05.863 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=19, callback=0, payload=00 13 0A 32 02 21 74 00 00 0C 13 00 00
2020-06-26 21:38:05.863 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=19, callback=0, payload=00 13 0A 32 02 21 74 00 00 0C 13 00 00
2020-06-26 21:38:05.863 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-06-26 21:38:05.863 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Application Command Request (ALIVE:DELETE_SUC_ROUTES)
2020-06-26 21:38:05.863 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: Incoming command class COMMAND_CLASS_METER, endpoint 0
2020-06-26 21:38:05.864 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 19: SECURITY not supported
2020-06-26 21:38:05.864 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 19: Received COMMAND_CLASS_METER V3 METER_REPORT
2020-06-26 21:38:05.864 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 19: Meter: Type=Electric(1), Scale=W(2), Value=3.091
2020-06-26 21:38:05.864 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got an event from Z-Wave network: ZWaveMeterValueEvent
2020-06-26 21:38:05.864 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_METER, value=3.091
2020-06-26 21:38:05.864 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 19: Updating channel state zwave:device:a5365e91:node19:meter_watts to 3.091 [DecimalType]
2020-06-26 21:38:05.864 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Commands processed 1.
2020-06-26 21:38:05.864 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 19: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@24ecd54a.
2020-06-26 21:38:05.865 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-06-26 21:38:05.865 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2020-06-26 21:38:05.865 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2020-06-26 21:38:05.865 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2020-06-26 21:38:06.977 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 08 02 82 01 7A
2020-06-26 21:38:06.978 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=8, callback=0, payload=00 08 02 82 01

Bruce_Osborne · June 26, 2020, 11:32am

@chris what do you think?

chris · June 26, 2020, 12:02pm

From a quick look, it seems that the device is not responding - I see requests timing out and it looks like the device didn’t respond (which is normally what the timeout means).

Does the crow have to fly through walls?

8 meters is possibly getting a bit far potentially - it really depends on a lot of things - how many walls are in the way, what the walls are made of, what the devices are etc.

psyciknz · June 26, 2020, 6:52pm

But isn’t that when it should run through other devices? It seems to think it can hit the controller directly. And noThing I do with placing smart switches within a few meters changes its routing.

This is an aeotec nano. Yes there are walls and even a floor between these controller and switch