FGFS-101 device not recognized anymore (firmware 2.5)

Alan_Alberghini · August 3, 2016, 8:49am

Well, this is weird…
I’m testing two different firmware versions of this device (2.5 and 3.2) and the older one has worked flawlessly till yesterday. It suddenly stopped working as before after this happened:

I accidentally performed a hard reset of the controller
I performed a reset of the device in order to include it again on the controller
the zwave binding now does not recognize it anymore with a Device discovery could not resolve to a thingType! 010F:0B00:1001::25.25 error.

It seems like the identifier of the device does not match the one inside the DB that the zwave binding embeds, but this is very unlikely, as it was working ok just minutes before step 1.

@chris: any clue what might have gone horribly wrong here? Could it be a regression in a recent update of the binding that makes the detection of this device fail now, while it just keeps working ok if it was added to the system using an earlier version?

chris · August 3, 2016, 9:31am

Not really. As you say, the 25.25 looks wrong and will likely cause the issue, but why this happened is another question. I don’t suppose you have a debug log when this happened?

I don’t think it’s a problem with the database, and I’d be surprised if it’s a problem with the binding since nothing has changed here. It might be that the device returned the wrong data, or it somehow got corrupted (which of course shouldn’t be able to happen, but clearly the version number is wrong, so something’s screwed up somewhere).

If you delete the XML and restart, or click the ‘reinitialise’ button in the tools menu in HABmin, then it should either sort itself out, of if the same thing happens then we definately should grab a log and I’ll take a look.

andrew · August 3, 2016, 10:37am

I had something similar the other day. I excluded the device and then re-included it. It worked okay for me after the device initialised.

chris · August 3, 2016, 10:41am

Excluding and re-including shouldn’t make any difference unless the device is not included correctly, or it needs to be reset for some reason. The full device reconfiguration is done either by deleting the XML file for the node, or by clicking on the reinitialise option - the question is why the version is wrong…

@Alan_Alberghini - before you reinitialise, can you post the XML file (if you haven’t deleted it already). It might be useful to take a quick look to see if there’s anything else strange in there…

shorty707 · August 3, 2016, 12:06pm

Same for me …
Exact same device and firmware Version.

@chris after sending a log to Chris he wrote in an email he thinks: " it is being discovered ok, but I think the problem is the ESH issue that means the discovery isn’t being properly updated. https://github.com/eclipse/smarthome/issues/1791 "

Not sure if that’s still the reason after more people have issues with that exact device?

chris · August 3, 2016, 1:21pm

I think this is different. This one has a corrupt version number (at least I’m pretty sure that version 25.25 is not correct). Or do you also have this same version being indicated?

shorty707 · August 3, 2016, 1:50pm

Yep. The last two parts from the node thingy in the inbox reflect the firmware i think … So Mine is

Node 10 (010F:0B00:1001:25.25)

25.25

chris · August 3, 2016, 2:58pm

Hmmm - interesting, I’d not noticed that earlier (not sure if you posted that earlier). I’ll check if this is a bug in the code - if the version isn’t known, then it should be 255.255, so maybe it’s this with a format error…

shorty707 · August 3, 2016, 4:27pm

The full initialization is in the log i sent you few days ago by mail. Maybe that helps.

(The Mail with the pan11 stuff)

chris · August 3, 2016, 4:28pm

Ok - thanks. I’ll try and take another look at that tonight - I’ve been tied up over the past couple of evenings with some other issues…

chris · August 3, 2016, 4:42pm

So it seems that the device is reporting the version as 25.25!

It should therefore detect it as the later version I think (ie the version 3).

The question is if this is normal, and if so we probably need to make a new version 25.25!!!

shorty707 · August 3, 2016, 8:10pm

25.25 is also a listed Version on Zwave Alliance.
However…why is it not recognized by the binding as max 3 Version which exists already?

chris · August 3, 2016, 8:27pm

Ok - that’s good - at least there’s no mystery there

Good question - I’ll have to look deeper into the log…

shorty707 · August 5, 2016, 6:33pm

@chris

anything we can help to find the issue?

chris · August 5, 2016, 6:41pm

Sorry - I’ve not had the chance to look at this - I’ve had a few other things to look at at the moment.

shorty707 · August 10, 2016, 5:13pm

its still recognized like this. so should we add a db entry for 25.25?

chris · August 10, 2016, 6:01pm

No - at least the issue with your device is the IDs are not in the database. I’ll update this tonight so let’s see if it solves the issue in tomorrows snapshot.

shorty707 · August 12, 2016, 8:24am

hi
its recognized now and all items are auto created.
however all auto created items dont show any values:

10:20:24.139 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=0, expected=ApplicationUpdate, cancelled=true      MISMATCH
10:20:24.172 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 49 84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 C6 
10:20:24.187 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:24.191 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 13 00 49 84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 C6 
10:20:24.195 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 13 00 49 84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 C6 
10:20:24.199 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 
10:20:24.253 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 10: Application update request. Node information received.
10:20:24.255 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
10:20:24.257 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@270b74 already registered
10:20:24.260 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 10: Is awake with 1 messages in the wake-up queue.
10:20:24.264 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
10:20:24.269 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Wakeup during initialisation.
10:20:24.273 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: queue length(1), free to send(false)
10:20:24.277 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - queued packet. Queue length is 1
10:20:24.279 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 31. Queue={}
10:20:24.280 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveWakeUpEvent
10:20:24.285 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 32. Queue={}
10:20:24.288 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=RequestNodeInfo[0x60], type=Request[0x00], priority=High, dest=255, callback=0, payload=0A 
10:20:24.291 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 
10:20:24.293 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=0, expected=ApplicationUpdate, cancelled=false        transaction complete!
10:20:24.295 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
10:20:24.297 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: Transaction complete (RequestNodeInfo:Request) success(true)
10:20:24.298 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - checking initialisation queue. Queue size 1.
10:20:24.300 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - message removed from queue. Queue size 0.
10:20:24.302 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: queue length(0), free to send(true)
10:20:24.304 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: loop - DETAILS try 2: stageAdvanced(false)
10:20:24.305 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: DETAILS - send RequestNodeInfo
10:20:24.308 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - queued packet. Queue length is 1
10:20:24.310 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 33. Queue={}
10:20:24.312 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 476ms/4771ms.
10:20:24.314 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 32
10:20:24.317 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 0A 02 84 08 25 D4 90 
10:20:24.321 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 10: Sending REQUEST Message = 01 09 00 13 0A 02 84 08 25 D4 90 
10:20:24.334 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
10:20:24.347 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:24.351 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
10:20:24.354 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
10:20:24.358 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:20:24.361 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 10: Sent Data successfully placed on stack.
10:20:24.373 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 D4 00 00 04 3B 
10:20:24.379 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:24.382 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 D4 00 00 04 00 00 35 
10:20:24.386 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 D4 00 00 04 00 00 35 
10:20:24.397 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=D4 00 00 04 
10:20:24.400 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 10: SendData Request. CallBack ID = 212, Status = Transmission complete and ACK received(0)
10:20:24.403 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
10:20:24.406 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@270b74 already registered
10:20:24.410 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=10, callback=212, payload=0A 02 84 08 
10:20:24.413 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=D4 00 00 04 
10:20:24.416 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=212, expected=SendData, cancelled=false        transaction complete!
10:20:24.418 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
10:20:24.421 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: Transaction complete (SendData:Request) success(true)
10:20:24.423 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - checking initialisation queue. Queue size 1.
10:20:24.426 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 10: Went to sleep
10:20:24.429 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 10: Is sleeping
10:20:24.432 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
10:20:24.434 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 10: Response processed after 109ms/4771ms.
10:20:24.439 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 31
10:20:24.443 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 60 0A 91 
10:20:24.445 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 60 0A 91 
10:20:24.460 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 60 01 9B 
10:20:24.465 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:24.467 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 60 01 9B 
10:20:24.470 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 60 01 9B 
10:20:24.476 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=RequestNodeInfo[0x60], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:20:24.480 [DEBUG] [lmessage.RequestNodeInfoMessageClass] - Request node info successfully placed on stack.
10:20:24.484 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=RequestNodeInfo[0x60], type=Request[0x00], priority=High, dest=255, callback=0, payload=0A 
10:20:24.488 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=RequestNodeInfo[0x60], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:20:24.492 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=RequestNodeInfo, callback id=0, expected=ApplicationUpdate, cancelled=false      MISMATCH
10:20:24.552 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 49 84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 C6 
10:20:24.557 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:24.561 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 13 00 49 84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 C6 
10:20:24.566 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 13 00 49 84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 C6 
10:20:24.571 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 
10:20:24.576 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 10: Application update request. Node information received.
10:20:24.579 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Starting initialisation from DONE
10:20:24.591 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@270b74 already registered
10:20:24.592 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 10: Is awake with 0 messages in the wake-up queue.
10:20:24.593 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
10:20:24.594 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Wakeup during initialisation.
10:20:24.595 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: queue length(1), free to send(false)
10:20:24.597 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: loop - DETAILS try 3: stageAdvanced(false)
10:20:24.598 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: DETAILS - send RequestNodeInfo
10:20:24.600 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - queued packet. Queue length is 1
10:20:24.602 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 32. Queue={}
10:20:24.603 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveWakeUpEvent
10:20:24.607 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=RequestNodeInfo[0x60], type=Request[0x00], priority=High, dest=255, callback=0, payload=0A 
10:20:24.610 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationUpdate[0x49], type=Request[0x00], priority=High, dest=255, callback=0, payload=84 0A 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 
10:20:24.612 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationUpdate, callback id=0, expected=ApplicationUpdate, cancelled=false        transaction complete!
10:20:24.613 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
10:20:24.615 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: Transaction complete (RequestNodeInfo:Request) success(true)
10:20:24.616 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - checking initialisation queue. Queue size 1.
10:20:24.618 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - message removed from queue. Queue size 0.
10:20:24.619 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - DETAILS: queue length(0), free to send(true)
10:20:24.621 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: loop - DETAILS try 4: stageAdvanced(false)
10:20:24.622 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer: DETAILS - send RequestNodeInfo
10:20:24.624 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 10: Node advancer - queued packet. Queue length is 1
10:20:24.626 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 33. Queue={}
10:20:24.628 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 177ms/4771ms.
10:20:24.630 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 32
10:20:24.633 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 00 60 0A 91 
10:20:24.635 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 04 00 60 0A 91 
10:20:24.646 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 60 01 9B 
10:20:24.649 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:24.650 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 60 01 9B 
10:20:24.652 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 60 01 9B 
10:20:24.654 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=RequestNodeInfo[0x60], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:20:24.655 [DEBUG] [lmessage.RequestNodeInfoMessageClass] - Request node info successfully placed on stack.
10:20:24.657 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=RequestNodeInfo[0x60], type=Request[0x00], priority=High, dest=255, callback=0, payload=0A 
10:20:24.659 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=RequestNodeInfo[0x60], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:20:24.660 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=RequestNodeInfo, callback id=0, expected=ApplicationUpdate, cancelled=false      MISMATCH
10:20:25.627 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 10: No more messages, go back to sleep
10:20:25.629 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 10: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
10:20:25.631 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 33. Queue={}
10:20:29.641 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Too many retries. Discarding message: Message: class=RequestNodeInfo[0x60], type=Request[0x00], priority=High, dest=255, callback=0, payload=0A 
10:20:29.642 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 32
10:20:29.644 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 0A 02 84 08 25 D5 91 
10:20:29.651 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 10: Sending REQUEST Message = 01 09 00 13 0A 02 84 08 25 D5 91 
10:20:29.665 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8 
10:20:29.670 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
10:20:29.672 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8 
10:20:29.674 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8 
10:20:29.676 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01 
10:20:29.677 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 10: Sent Data successfully placed on stack.

chris · August 12, 2016, 12:42pm

I haven#t processed the log fully, but from a quick look I don’t see any data received from the device that would relate to a channel. I think these packets are all associated with NIFs and wakeup management - the device hasn’t sent any actual user data I think.

I’ll process the log properly later, but I expect my first question will be for a longer log that actually has some data included, so if you can send this it might speed things up

chris · August 12, 2016, 6:18pm

Having now processed the log, there is nothing to look at so there is no surprise that there is no updates to the channels (based solely on this log).