ZWave binding updates

Chrishab · September 24, 2018, 6:33pm

Wow, thank you! I started thinking it was me

chris · September 24, 2018, 6:41pm

This was removed - the marketplace binding was exactly the same as the dev binding - ie the link was to exactly the same location. Once the development binding was merged, I removed the marketplace binding to avoid confusion.

This is the snapshot binding.

scurrier03 · September 26, 2018, 4:21am

Can someone clarify? If I upgrade from OH2 2.3.0 release to the latest milestone build, 2.4.0.M4, will I be able to seamlessly upgrade to future releases such as 2.4.0 release with minimal hackery? And only go through the breaking changes of Z-Wave once? Or would it be more complicated than that?

chris · September 26, 2018, 6:45am

Yes the M4 build has the updated ZWave binding and you will only need to perform the upgrade once.

chris · September 26, 2018, 7:47am

Absolutely none - sorry. I don’t think it’s related to the ZWave updates and you might be better to ask in the other thread on the M4 update?

sihui · September 26, 2018, 8:00am

Take a look at

zynex · September 26, 2018, 8:03am

I just tried to add POPP Z-Weather to my fresh installation, but it’s just shown as a unknown device. It seems this has been an issue before to. I migrated from Domoticz about 4-5 days ago, and it worked there (except that the old device broke so this is a brand new one).

This is the properties i have for it now;

|zwave_beaming |true|
|---|---|
|zwave_class_basic |BASIC_TYPE_ROUTING_SLAVE|
|zwave_class_generic |GENERIC_TYPE_SENSOR_MULTILEVEL|
|zwave_class_specific |SPECIFIC_TYPE_ROUTING_SENSOR_MULTILEVEL|
|zwave_frequent |false|
|zwave_listening |false|
|zwave_neighbours ||
|zwave_nodeid |19|
|zwave_routing |true|
|zwave_secure |false|
|zwave_version |0.0|

chris · September 26, 2018, 8:03am

Yes.

chris · September 26, 2018, 8:05am

Try waking the device up - the binding needs to discover the device and interrogate it to determine all the services it provides (and determine what the device actually is!).

zynex · September 26, 2018, 8:05am

I tried that, but I give it ago again.

[EDIT] Took a couple of tries, but i finally got it identified

Chrishab · September 26, 2018, 8:27am

Hi Chris,

Do you already have an idea when the binding will be updated? So far I only have binary sensor channels on the window sensors so I am looking forward to the update.

chris · September 26, 2018, 8:31am

I will likely do an update tonight - I normally do 2 or 3 updates a week (normally Friday/Sunday and sometimes another day…).

robjkamp · September 27, 2018, 1:12pm

I have waked up one of the devices and that worked. The other one showed that it woke up but the backend did not show any signs of recognition. I removed the node and reinserted.

Now it all works like a charm!

Masssssy · September 29, 2018, 4:14pm

So has anyone managed to get this running on 2.3? 2.4 breaks another binding of mine and my older Z-wave development w/ security binding lacks a new Z-wave device in the DB. I.e can’t really upgrade to 2.4 right now and it would be great if it was possible to get this running on 2.3 so I can install my new device.

chris · September 29, 2018, 4:47pm

Yes - it should work ok under 2.3, but you obviously need to install manually if you’re on the stable branch.

muere · October 4, 2018, 8:23am

Installation: openhabian on Raspberry 3B
Update: openHAB 2.4.0 Build # 1380
Aeotec Gen5 USB stick
Things about PaperUI installed.

Update process as above.
If I remove those things, then delete the zwave binding, cache and temp empty, reboot OH and then reinstall the zwave binding,
things are automatically transferred to the inbox.
Is that correct?
My problem is that all power devices are working properly and all battery devices are not working. e.g .:
With the Fibaro Motion Sensor FMGS001 zw2.7, the motion detector only works with the channel alarm_tamper!

chris · October 4, 2018, 10:04am

You need to wake the battery devices up -:

muere · October 4, 2018, 10:06am

I woke up at least 100 times

chris · October 4, 2018, 11:18am

Then please check the debug logs to be sure that the device is waking up - this is the only thing that should stop battery devices initialising.

muere · October 4, 2018, 11:24am

Where do I see this?

2018-10-04 13:20:56.280 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 13 00 49 84 19 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84 D5

2018-10-04 13:20:56.289 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0&lt;&gt;128 : Message: class=ApplicationUpdate[73], type=Request[0], dest=25, callback=132, payload=84 19 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84

2018-10-04 13:20:56.294 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationUpdate[73], type=Request[0], dest=25, callback=132, payload=84 19 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84

2018-10-04 13:20:56.296 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2018-10-04 13:20:56.298 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 0

2018-10-04 13:20:56.300 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: null

2018-10-04 13:20:56.304 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=ApplicationUpdate[73], type=Request[0], dest=25, callback=132, payload=84 19 0D 04 A1 02 30 9C 60 85 8E 72 70 86 80 84

2018-10-04 13:20:56.306 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 25: Application update request. Node information received. Transaction null

2018-10-04 13:20:56.308 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: resetResendCount initComplete=true isDead=false

2018-10-04 13:20:56.310 [DEBUG] [essage.ApplicationUpdateMessageClass] - NODE 25: Application update - no transaction.

2018-10-04 13:20:56.312 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-04 13:20:56.314 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-10-04 13:20:56.563 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: Is awake with 0 messages in the queue

2018-10-04 13:20:56.567 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: Start sleep timer at 1000ms

2018-10-04 13:20:56.569 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveNodeStatusEvent

2018-10-04 13:20:56.602 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 25: Node Status event - Node is AWAKE

==&gt; /var/log/openhab2/events.log &lt;==

2018-10-04 13:20:56.613 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node25' has been updated.

==&gt; /var/log/openhab2/openhab.log &lt;==

2018-10-04 13:20:57.069 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: WakeupTimerTask 0 Messages waiting, state DONE

2018-10-04 13:20:57.568 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: WakeupTimerTask 0 Messages waiting, state DONE

2018-10-04 13:20:57.570 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: No more messages, go back to sleep

2018-10-04 13:20:57.572 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 25: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION

2018-10-04 13:20:57.574 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: SECURITY not supported

2018-10-04 13:20:57.576 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured

2018-10-04 13:20:57.578 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@1c4594d

2018-10-04 13:20:57.581 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: Bump transaction 430 priority from Immediate to Immediate

2018-10-04 13:20:57.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: Adding to device queue

2018-10-04 13:20:57.587 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: Added 430 to queue - size 7

2018-10-04 13:20:57.589 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-10-04 13:20:57.593 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 19 02 84 08 25 41 16

2018-10-04 13:20:57.596 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 25: Sending REQUEST Message = 01 09 00 13 19 02 84 08 25 41 16

2018-10-04 13:20:57.598 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT

2018-10-04 13:20:57.600 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 65

2018-10-04 13:20:57.601 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06

2018-10-04 13:20:57.604 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0&lt;&gt;128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-10-04 13:20:57.606 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=

2018-10-04 13:20:57.613 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 65

2018-10-04 13:20:57.613 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8

2018-10-04 13:20:57.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK

2018-10-04 13:20:57.616 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0&lt;&gt;128 : Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01

2018-10-04 13:20:57.617 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-04 13:20:57.620 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-10-04 13:20:57.622 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01

2018-10-04 13:20:57.625 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 65

2018-10-04 13:20:57.627 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-10-04 13:20:57.627 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 41 00 00 03 A9

2018-10-04 13:20:57.629 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 430: [WAIT_RESPONSE] priority=Immediate, requiresResponse=true, callback: 65

2018-10-04 13:20:57.632 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0&lt;&gt;128 : Message: class=SendData[19], type=Request[0], dest=0, callback=65, payload=41 00 00 03

2018-10-04 13:20:57.635 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Response[1], dest=255, callback=0, payload=01

2018-10-04 13:20:57.637 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: sentData successfully placed on stack.

2018-10-04 13:20:57.639 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 430: Advanced to WAIT_REQUEST

2018-10-04 13:20:57.641 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: TID 430: Transaction not completed

2018-10-04 13:20:57.644 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=SendData[19], type=Request[0], dest=0, callback=65, payload=41 00 00 03

2018-10-04 13:20:57.646 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 430: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 65

2018-10-04 13:20:57.647 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1

2018-10-04 13:20:57.649 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 430: [WAIT_REQUEST] priority=Immediate, requiresResponse=true, callback: 65

2018-10-04 13:20:57.651 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 430: (Callback 65)

2018-10-04 13:20:57.653 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!

2018-10-04 13:20:57.655 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 430: callback 65

2018-10-04 13:20:57.657 [DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=SendData[19], type=Request[0], dest=0, callback=65, payload=41 00 00 03

2018-10-04 13:20:57.659 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 25: SendData Request. CallBack ID = 65, Status = Transmission complete and ACK received(0)

2018-10-04 13:20:57.661 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: resetResendCount initComplete=true isDead=false

2018-10-04 13:20:57.663 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 430: Transaction COMPLETED

2018-10-04 13:20:57.665 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: Response processed after 65ms

2018-10-04 13:20:57.667 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: TID 430: Transaction completed

2018-10-04 13:20:57.669 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 25: notifyTransactionResponse TID:430 DONE

2018-10-04 13:20:57.671 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 25: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent

2018-10-04 13:20:57.673 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-04 13:20:57.671 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 430: Transaction event listener: DONE: DONE -&gt;

2018-10-04 13:20:57.675 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2018-10-04 13:20:57.677 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 25: Went to sleep COMPLETE