I’m not sure - the easiest way is to use HABmin or PaperUI. Go to the extensions menu, uninstall ZWave, wait 5 or 10 seconds, then install it again. This will pick up the latest version - assuming you’re using the online version and not the offline, and you’re using the snapshot version and not the ‘beta’ versions.
Probably the karaf command does the same thing, but I’m not sure.
The update works, it is now a know device 
Been meaning to ask you, in stead of retrieving the complete build through cloudbees, would this work to update the zwave binding in karaf?
openhab> bundle:list | grep -i zwave
188 | Active | 80 | 2.0.0.201609222252 | ZWave Binding
openhab> bundle:update 188
it does. I’ve started using that method as well vs. the uninstall/reinstall
Nevermind, I thought it had worked for me recently but now it doesn’t seem to be updating. So back to uninstall/reinstall.
Hi guys,
Did you guys ever resolved this?
Mine is showing up as:
Z-Wave Node 4
Unknown Device
and in openhab.log:
2018-10-11 11:47:09.157 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-10-11 11:47:09.162 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:controller:node4' to inbox.
Im on Openhab 2.3.0
That is a pretty old version. If your device was added to the database recently it won’t be available. You need to upgrade to the snapshot 2.4 binding.
Be aware that there are breaking changes, so follow that post exactly:
The device is not fully initialised. Until real values are shown here, the database will not be searched anyway. Normally when this happens it is caused by not waking up a battery device, or some other communication issue between the controller and the device.
yeah, i cannot seem to get this done, it always comes back as unknown device, even if i wake it.
it shows offline/online when i wake it in the things list in paper ui, i will try to reinclude it, maybe thats the problem?
It’s possible that it didn’t include properly - this can happen, and the controller can still think that the device is included, when it’s not.
If it still doesn’t work after re-including, then please get a debug log so we can see what is happening.
That seemed to work 
now it says:
Z-Wave Node 4: WALLC-S Wall Controller
WALLC-S Wall Controller
Wall Controller
Now lets see if i can control my fibaro double switch with it
well, seems to work ok, only thing i cannot seem to get is the battery level.
items
Number switchHallWayNumber "HW Number" (gDebug) { channel="zwave:device:controller:node4:scene_number" }
Number switchHallWayBattey "HW Switch Battery[%s %%]" <battery> (gBattery) { channel="zwave:device:controller:node4:battery-level" }
sitemap
Frame label="Verlichting" {
Text item=switchHallWayNumber
Text item=switchHallWayBattey
}
Did you try a decimal instead of a string format?
"HW Switch Battery[%d %%]"
yes, didn’t change.
Are you sure the battery item is being updated? Check for occurrences of switchHallWayBattey in events.log to verify that it is being set.
no, its not being set.
Now the parameter says this:
Size: 1 Byte, Default Value: 1
| Setting | Description |
|---|---|
| 0 | No |
| 1 | To same node as Wake Up Notification |
| 2 | Broadcast to neighbors |
so does that mean it only reports the battery report on wake up?
Cause the wake up interval is 604800 seconds.
The binding should poll the battery level when the device wakes up.
Two points:
hmm when i do it manually it doesn’t update, so maybe i am doing it wrong, will set the polling to a few minutes to test and see what that brings back then.
Good idea.
You also could put the zwave binding into debug mode, then check that the battery-level channel is being polled.
Note that the battery is only polled once per hour if I remember correctly. I’m not sure if this can be changed. Of course, it will only actually perform the poll after the device wakes up as well.