Anyone noticied this in the new zwave 2.5 snapshot binding?

[dastrix80 (Kris K)]

Hi All, brand new system, brand new devices (all Aeon Nano Switches) and ZStick. No other bindings. Just the snapshot.

I can see in the logs it sees the node upon include but nothing shows up in the inbox until I restart the binding.

Anyone seen something similiar? Im staging a stack of devices and what should be a 5minute job has taken ages

Cheers!

[dastrix80 (Kris K)]

THink i know what it is… serial port keeps changing ugh!

[sihui]

Maybe related:

Snapshot version of zwave cannot find serial port after OH restart

since about two weeks, I have the following problem on my Openhab raspi system (2.4 stable): after starting openhab, the zwave controller does not work. 2019-05-02 19:45:43.586 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0' 2019-05-02 19:45:43.603 [WARN ] [erial.internal.SerialPortManagerImpl] - No SerialPortProvider found for: /dev/ttyACM0 the following workaround helps out: in paperui change the port for the zwave controller restart openhab serv…

[5iver (Scott Rushworth)]

Which version of OH? PersistentInbox had a bug fixed recently.

[dastrix80 (Kris K)]

2.4 Stable. Controller is online as other nodes are working. Ive just paired Node 4, and I can see it in the logs but nothing in the inbox

Only way I can get them to show is to restart the binding.

I also notice the Controller, once showing, shows node_1 and also node_1_1 for the ZW132 @chris do you know why that would be?

13-May-2019 07:12:28.109 [DEBUG] [b.binding.zwave.internal.protocol.ZWaveTransaction] - TID 143: Transaction ABORTED
13-May-2019 07:12:28.109 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Creating empty message of class = SendDataAbort (0x16), type = Request
13-May-2019 07:12:28.109 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - Calculated checksum = -22
13-May-2019 07:12:28.110 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 03 00 16 EA
13-May-2019 07:12:28.110 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 03 00 16 EA
13-May-2019 07:12:28.110 [DEBUG] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Message SENT
13-May-2019 07:12:28.110 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
13-May-2019 07:12:28.110 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Transaction lastTransaction outstanding...
13-May-2019 07:12:28.110 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - STOP transaction timer
13-May-2019 07:12:28.111 [TRACE] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Start transaction timer to Mon May 13 07:12:40 UTC 2019 - 11998ms
13-May-2019 07:12:28.111 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
13-May-2019 07:12:28.111 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 06
13-May-2019 07:12:28.111 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 74<>54 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
13-May-2019 07:12:29.199 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Received SOF
13-May-2019 07:12:29.200 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 1D 00 49 84 04 17 04 10 01 5E 25 27 32 81 71 60 8E 2C 2B 70 86 72 73 85 59 7A 5A EF 82 38
13-May-2019 07:12:29.201 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 1D 00 49 84 04 17 04 10 01 5E 25 27 32 81 71 60 8E 2C 2B 70 86 72 73 85 59 7A 5A EF 82 38
13-May-2019 07:12:29.201 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - Calculated checksum = 56
13-May-2019 07:12:29.201 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
13-May-2019 07:12:29.201 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 4: Message payload = 84 04 17 04 10 01 5E 25 27 32 81 71 60 8E 2C 2B 70 86 72 73 85 59 7A 5A EF 82
13-May-2019 07:12:29.201 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
13-May-2019 07:12:29.202 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
13-May-2019 07:12:29.202 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 75<>53 : Message: class=ApplicationUpdate[73], type=Request[0], dest=4, callback=132, payload=84 04 17 04 10 01 5E 25 27 32 81 71 60 8E 2C 2B 70 86 72 73 85 59 7A 5A EF 82
13-May-2019 07:12:31.059 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Received SOF
13-May-2019 07:12:31.060 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 08 00 04 00 04 02 82 01 76
13-May-2019 07:12:31.060 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 08 00 04 00 04 02 82 01 76
13-May-2019 07:12:31.060 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - Calculated checksum = 118
13-May-2019 07:12:31.060 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
13-May-2019 07:12:31.060 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 4: Message payload = 00 04 02 82 01
13-May-2019 07:12:31.061 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
13-May-2019 07:12:31.061 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
13-May-2019 07:12:31.061 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 76<>52 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 02 82 01
13-May-2019 07:12:32.060 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Received SOF
13-May-2019 07:12:32.061 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 04 06 60 0D 01 00 82 01 1A
13-May-2019 07:12:32.061 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 0C 00 04 00 04 06 60 0D 01 00 82 01 1A
13-May-2019 07:12:32.062 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - Calculated checksum = 26
13-May-2019 07:12:32.062 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
13-May-2019 07:12:32.062 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 4: Message payload = 00 04 06 60 0D 01 00 82 01
13-May-2019 07:12:32.062 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
13-May-2019 07:12:32.062 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
13-May-2019 07:12:32.062 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 77<>51 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 06 60 0D 01 00 82 01
13-May-2019 07:12:32.087 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Received SOF
13-May-2019 07:12:32.088 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 00 04 06 60 0D 02 00 82 01 19
13-May-2019 07:12:32.088 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 0C 00 04 00 04 06 60 0D 02 00 82 01 19
13-May-2019 07:12:32.088 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - Calculated checksum = 25
13-May-2019 07:12:32.088 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
13-May-2019 07:12:32.089 [TRACE] [nhab.binding.zwave.internal.protocol.SerialMessage] - NODE 4: Message payload = 00 04 06 60 0D 02 00 82 01
13-May-2019 07:12:32.089 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
13-May-2019 07:12:32.089 [TRACE] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
13-May-2019 07:12:32.089 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 78<>50 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 06 60 0D 02 00 82 01

[dastrix80 (Kris K)]

Saw this also:

Exception in thread "ZWaveReceiveProcessorThread" java.lang.NullPointerException
        at org.openhab.binding.zwave.event.BindingEventFactory.formatEvent(BindingEventFactory.java:85)
        at org.openhab.binding.zwave.handler.ZWaveControllerHandler.ZWaveIncomingEvent(ZWaveControllerHandler.java:631)
        at org.openhab.binding.zwave.internal.protocol.ZWaveController.notifyEventListeners(ZWaveController.java:558)
        at org.openhab.binding.zwave.internal.protocol.serialmessage.AddNodeMessageClass.handleRequest(AddNodeMessageClass.java:93)
        at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:223)
        at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:191)
        at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager$ZWaveReceiveThread.run(ZWaveTransactionManager.java:609)

[chris (Chris Jackson)]

@dastrix80

@chris do you know why that would be?

The first 1 is the node, the second 1 is the endpoint. This is normal and you shouldn’t worry about it as the binding has a bunch of logic to try and manage associations depending on the different command classes, and versions of the command classes that each device supports…

[dastrix80 (Kris K)]

No worries! Thanks. Any comment on why a binding restart is required to have the node show once included?

Further, once the XML’s are created for the nodes. Can these be copied between systems if the Nodes and Controller stay the same?

[chris (Chris Jackson)]

@dastrix80

Any comment on why a binding restart is required to have the node show once included?

No - I’ve no idea. Nothing has changed in the binding, so I would guess it’s an(other) issue with the core with all the changes that are happening at the moment.

[dastrix80 (Kris K)]

Hm, how would that be possible though if I’m running 2.4 Stable? I assume when you say core, you mean relating to the snapshot 2.5 OpenHab?

[chris (Chris Jackson)]

@dastrix80

how would that be possible though if I’m running 2.4 Stable?

Well, I didn’t know that. Anyway, the bottom line is nothing has changed in the binding, so unless something has changed in the core, including the side that the binding links, I don’t know.

[dastrix80 (Kris K)]

Fair enough! Very odd