I think the first thing would be to verify you’re really on the right version. Could you run the following in Karaf console and post the output?
bundle:list|grep ZWave
Yes - it is included.
Did you delete all the things? This error normally occurs if the database definition is wrong - ie it’s an old definition. What device is this, and what channel are you trying to command?
Here it is:
openhab> bundle:list|grep ZWave
237 │ Active │ 80 │ 2.4.0.M2 │ ZWave Binding
I’m guessing M2 means milestone 2.
Yep. And milestone 2 was released before this was committed into master, so you don’t have the new stuff 
OK, Thanks.
I did the uninstall/reinstall of the binding through Paper UI but I see from sihui’s comment above that that might not work. I’ll try another method tonight.
I got stuck on the Milestone build and followed the instructions here to get back on the daily builds.
As soon as I did that the new z-wave binding was installed.
That was the easiest way I found to update to the new zwave binding. Plus, I wanted to get back to the daily updates.
Try Mark’s solution, that should work in either case.
I’m snapshot 1361 and my zwave binding shows:
210 │ Active │ 80 │ 2.4.0.201809112011 │ ZWave Binding
I could swear that a few of my devices don’t have the same list of parameters and configuration settings.
For instance, I thought I used to have settings to allow the update of display (in paperui and habpanel) for the NZW39. And I can’t seem to get the metering output on my NAS-WR01ZE. The NXW36 Device Configuration lists only Polling Period, Command Poll Period and Switch All Mode; Configuration list nothing.
Am I just remembering wrong? (I’ve been know to do that from time to time 
)
Just to be sure, if we were already using the test version, we shouldn’t need to delete and re-add Things upon switching to the merged snapshot version?
Yes, that’s correct - unless a thing definition has changed, but it’s safe to assume that’s not the case.
Hi All,
I’m new completely new to openhab. I was testen openhab 2.3 with my zwave devices, which was working very well until i discovered that the Quibino ZMNHAD devices had an issue with sending there l2/l3 status. So after much reading, I’ve decided to install the 2.4 Z-Wave Binding and also the Openhab 2.4 snapshot.
So completely new install of openhab 2.3 on an RPi 3 with openhabian (No Zwave configuration done, what so ever). Then i did the upgrade to the Openhab 2.4 snapshot which now comes with the 2.4 Z-Wave snapshot.
Inserted the Aeotec z-stick gen5 installed the zwave binding via PaperUI and my zwave devices where discovered. Added only 1 ZMNHAD, then made an item for the switch.
But when i trigger the switch from the control page nothing happens. Looking at the config of the Thing, i don’t see associations for the lifeline, nor cant i set it.
openhab> bundle:list|grep ZWave
202 x Active x 80 x 2.4.0.201809142025 x ZWave Binding
When toggle the switch i get java erros:
2018-09-15 14:34:57.630 [.ItemChannelLinkAddedEvent] - Link ‘LT03_Switch-zwave:device:512:node4:switch_binary’ has been added.
2018-09-15 14:35:03.398 [ome.event.ItemCommandEvent] - Item ‘LT03_Switch’ received command ON
==> /var/log/openhab2/openhab.log <==
2018-09-15 14:35:03.400 [ERROR] [nal.common.AbstractInvocationHandler] - An error occurred while calling method ‘Ev entSubscriber.receive()’ on ‘org.eclipse.smarthome.core.thing.internal.CommunicationManager@b5dc9’: null
java.lang.NullPointerException: null
at org.eclipse.smarthome.core.thing.internal.AutoUpdateManager.receiveCommand(AutoUpdateManager.java:141) ~ [?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.receiveCommand(CommunicationManager.java: 266) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.receive(CommunicationManager.java:145) ~[ ?:?]
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHand ler.java:153) [100:org.eclipse.smarthome.core:0.10.0.201809111909]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [100:org.eclipse.smarthom e.core:0.10.0.201809111909]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
2018-09-15 14:35:03.472 [ERROR] [me.core.internal.events.EventHandler] - Dispatching/filtering event for subscriber ‘org.eclipse.smarthome.core.events.EventSubscriber’ failed: null
java.lang.NullPointerException: null
at org.eclipse.smarthome.core.thing.internal.AutoUpdateManager.receiveCommand(AutoUpdateManager.java:141) ~ [?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.receiveCommand(CommunicationManager.java: 266) ~[?:?]
at org.eclipse.smarthome.core.thing.internal.CommunicationManager.receive(CommunicationManager.java:145) ~[ ?:?]
at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
at org.eclipse.smarthome.core.internal.common.AbstractInvocationHandler.invokeDirect(AbstractInvocationHand ler.java:153) [100:org.eclipse.smarthome.core:0.10.0.201809111909]
at org.eclipse.smarthome.core.internal.common.Invocation.call(Invocation.java:53) [100:org.eclipse.smarthom e.core:0.10.0.201809111909]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
I think this is probably fixed - it looks like an error in the framework and it has been closed -:
It’s probably not in the latest OH yet though as it looks like it was only closed yesterday.
Thanks Chris, I will check it out and let you know.
Hi,
thank you for all your effort you’re putting into this binding!
I have just upgraded to the latest snapshot version and have a problem with my Z-Wave.Me Wall Controller device. I can see in the logs that the action (button press) is received by the binding, but it doesn’t seem to be forwarded to the item? Any idea what’s wrong here?
My item:
Number WallCSceneNumber { channel="zwave:device:a367f17a:node10:scene_number" }
Logs:
2018-09-15 18:56:46.133 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Received SOF
2018-09-15 18:56:46.144 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 0A 04 2B 01 0B FF 21
2018-09-15 18:56:46.152 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Creating new SerialMessage from buffer = 01 0A 00 04 00 0A 04 2B 01 0B FF 21
2018-09-15 18:56:46.155 [TRACE] [wave.internal.protocol.SerialMessage] - Calculated checksum = 33
2018-09-15 18:56:46.165 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 255: Checksum matched
2018-09-15 18:56:46.170 [TRACE] [wave.internal.protocol.SerialMessage] - NODE 10: Message payload = 00 0A 04 2B 01 0B FF
2018-09-15 18:56:46.174 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Message is valid, sending ACK
2018-09-15 18:56:46.177 [TRACE] [WaveSerialHandler$ZWaveReceiveThread] - Response SENT 6
2018-09-15 18:56:46.184 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 04 2B 01 0B FF
2018-09-15 18:56:46.190 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 04 2B 01 0B FF
2018-09-15 18:56:46.197 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-09-15 18:56:46.203 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:DONE)
2018-09-15 18:56:46.207 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: resetResendCount initComplete=true isDead=false
2018-09-15 18:56:46.213 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_SCENE_ACTIVATION, endpoint 0
2018-09-15 18:56:46.216 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported
2018-09-15 18:56:46.222 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_SCENE_ACTIVATION V0 SCENEACTIVATION_SET
2018-09-15 18:56:46.225 [DEBUG] [ass.ZWaveSceneActivationCommandClass] - NODE 10: Scene activation: Scene 11, Time 255
2018-09-15 18:56:46.229 [TRACE] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-09-15 18:56:46.233 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-09-15 18:56:46.238 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SCENE_ACTIVATION, value = 11
2018-09-15 18:56:46.242 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.
2018-09-15 18:56:46.246 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1bcd506.
2018-09-15 18:56:46.248 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-15 18:56:46.253 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-09-15 18:56:46.255 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-09-15 18:56:46.259 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2018-09-15 18:56:46.262 [TRACE] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false
2018-09-15 18:56:46.266 [TRACE] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!
2018-09-15 18:56:46.269 [TRACE] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: listening == false, frequentlyListening == false, awake == false
2018-09-15 18:56:46.273 [TRACE] [nal.protocol.ZWaveTransactionManager] - NODE 7: Node not awake!
Also, the discovery processes find a ZWave controller, even though one is already available and working (maybe a different issue?):
Can you provide the link to the database for your device please? Or provide the device type/id so I can be sure what the device is.
I suggest to just ignore this.
Hi,
this is the device: https://products.z-wavealliance.org/products/1086 (don’t know if you still maintain your own database, but on cd-jackson.com I am getting a 403).
Yes - it is where all the openHAB database is derived.
I had to do a server restart - it should be back up in a couple of minutes.
I think the issue is that your device is configured to send the scene_activation command, rather than the central_scene command that the binding uses. The scene_activation is an old class and we use the newer one.
1 Like
Is it just me or is it difficult to see when the fix is/will be merged with the OH?
Anyone got some pointer to navigate github or check the OH builds?
If you are talking about
That is a ESH fix and you need to watch this page:
https://hudson.eclipse.org/smarthome/job/SmartHomeDistribution-Stable/changes
So as of now fix #6201 is not yet included in openHAB snapshot 2.4