[SOLVED] Zwave Qubino ZMNHCD1 difficulties to re-include

Add-ons Bindings
1

Dear all

I have difficulties to re-include one of my Flush Shutter nodes.

2019-03-06 14:58:19.715 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovered
2019-03-06 14:58:19.716 [DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeDone, new event IncludeDone
2019-03-06 14:58:19.716 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2019-03-06 14:58:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 80 to queue - size 1
2019-03-06 14:58:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-03-06 14:58:19.717 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller end exclusion
2019-03-06 14:58:19.717 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWaveController include done
2019-03-06 14:58:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 79: Advanced to DONE
2019-03-06 14:58:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 163ms
2019-03-06 14:58:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 79: Transaction completed
2019-03-06 14:58:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:79 DONE
2019-03-06 14:58:19.720 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-03-06 14:58:19.720 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-03-06 14:58:19.721 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 00 B5
2019-03-06 14:58:19.721 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 00 B5
2019-03-06 14:58:19.721 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
2019-03-06 14:58:19.722 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 80: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2019-03-06 14:58:19.722 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
2019-03-06 14:58:19.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-03-06 14:58:19.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
2019-03-06 14:58:19.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 80: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
2019-03-06 14:58:19.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
2019-03-06 14:58:19.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-03-06 14:58:19.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
2019-03-06 14:58:24.722 [DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 80: Timeout at state WAIT_REQUEST. 3 retries remaining.
2019-03-06 14:58:24.722 [DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 80: Transaction is current transaction, so clearing!!!
2019-03-06 14:58:24.723 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 80: Transaction CANCELLED
2019-03-06 14:58:24.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:80 CANCELLED
2019-03-06 14:58:24.723 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-03-06 14:58:45.360 [DEBUG] [org.openhab.binding.zwave ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=519, service.bundleid=261, service.scope=singleton} - org.openhab.binding.zwave
2019-03-06 14:58:45.368 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:2f18a74d:node6.
2019-03-06 14:58:45.370 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: MANUFACTURER not set
2019-03-06 14:58:45.370 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller status changed to ONLINE.
2019-03-06 14:58:45.371 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller is ONLINE. Starting device initialisation.
2019-03-06 14:58:45.371 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2019-03-06 14:58:45.371 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising Thing Node…
2019-03-06 14:58:45.371 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling intialised at 1800 seconds - start in 1672200 milliseconds.
2019-03-06 14:58:45.371 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Device initialisation complete.
2019-03-06 14:58:53.183 [DEBUG] [al.protocol.ZWaveInclusionController] - ZWave inclusion controller finalised

I dont get the reason why habmin stays saying: Node not found in Z-wave network

Kind regards
Stefan

2

Meanwhile I found out that the device is definitely not allocated to the Z-Stick anymore - checked this with Zensys tools.
But it seems the OH (v2.4), Zwave binding (2.5 snapshot) still knows about it.

So the question is now: How to get a clean state in OH (cache and tmp already deleted and OH restarted).
Is there anything else to check?

3

When the binding starts, it gets the list of all devices that are known on the network - the binding will report this if the controller doesn’t have the specific device in the network any longer.

4

I have my node back (Same node ID).
After running inclusion out of a domoticz / OZW setup.

5

Why didn’t the inclusion work from OH - or didn’t you try it? It should be exactly the same?

6

I tried it several times with no luck. I have even placed the Qubino in a two meter distance from the controller (Zwave.me UZB) to do so. I don’t know what the reason is for that, I’m sorry. But anyway thank you very much for all your support!

Cheers
Stefan

7

Ok, that’s pretty strange. Given that OZW is doing exactly the same as OH, I doubt it’s related, but who knows.