[SOLVED] NEO Wallplug (NAS-WR01ZE) is in the database but is shown as Unknown Device

Do you still have a zwave binding manually installed through your addons folder?

Please check via Karaf and

bundle:list|grep -i zwave*

Do you still have a zwave binding manually installed through your addons folder?

I installed z-wave binding through paperUI, it was updated to 2.5.0 together with openhab.

bundle:list|grep -i zwave*

276 │ Active │ 80 │ 2.5.0 │ openHAB Add-ons :: Bundles :: ZWave Binding

Will try now to update to latest snapshot version

What was done:

  • Updated version ZWave binding using script. It became next:

286 │ Active │ 80 │ │ openHAB Add-ons :: Bundles :: ZWave Binding

  • Removed Thing from openhab
  • Removed it’s xml file from /var/lib/openhab2/zwave/
  • Restarted openhab
  • Added device again through inbox in paperUI

dbReference is still 1117, pointing to deleted device in database.

BTW, the release version of zwave binding had place 4 days ago - i don’t see any changes since that time, which can result in this issue. From my point of view, the possible solution will be to somehow corrupt this device in database (f.e., set non-existing manufacture, device id etc…).
And, one more, binding shows me 4 such devices, while in device database only 2 are active.

Could you please post your xml file for that node?

Sure. Here it is. node6.xml (9.7 KB)

Your type and id definitely points to a valid database entry:
The only explanation I have that some old config is cached on your installation.
Please clear the cache, then again delete the Thing and readd it.

Still the same :frowning: Cache was cleaned using openhab-cli, then i manually checked the content of /var/lib/openhab/ - no cache or tmp directories exists, directory .cache also was empty.

Started openhab2 again, removed added device and again that 1117 without config.

2019-12-19 17:03:59.515 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from ONLINE: Node initialising: REQUEST_NIF to ONLINE
2019-12-19 17:04:28.716 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from ONLINE to REMOVING
2019-12-19 17:04:28.732 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from REMOVING to REMOVED
2019-12-19 17:04:28.758 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from REMOVED to UNINITIALIZED
2019-12-19 17:04:28.924 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-12-19 17:04:54.720 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Rule ‘co2_notification’: Could not cast NULL to java.lang.Number; line 23, column 44, length 32
2019-12-19 17:05:01.905 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:7e178d6a:node6’ to inbox.
==> /var/log/openhab2/events.log <==
2019-12-19 17:05:01.908 [home.event.InboxAddedEvent] - Discovery Result with UID ‘zwave:device:7e178d6a:node6’ has been added.
2019-12-19 17:05:08.184 [me.event.InboxRemovedEvent] - Discovery Result with UID ‘zwave:device:7e178d6a:node6’ has been removed.
2019-12-19 17:05:08.208 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from UNINITIALIZED to INITIALIZING
2019-12-19 17:05:08.241 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-12-19 17:05:08.243 [hingStatusInfoChangedEvent] - ‘zwave:device:7e178d6a:node6’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-12-19 17:05:08.251 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:7e178d6a:node6’ has been updated.
2019-12-19 17:05:08.309 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:7e178d6a:node6’ has been updated.
2019-12-19 17:05:08.320 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:7e178d6a:node6’ has been updated.
2019-12-19 17:05:08.327 [me.event.ThingUpdatedEvent] - Thing ‘zwave:device:7e178d6a:node6’ has been updated.
2019-12-19 17:05:08.346 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]

Then I am out of ideas and we need to ping @chris

No problem. Sorry for disturb. Let’s wait for Chris.

I checked also the github repo for z-wave binding and found, that this device with id 1117, which is marked as deleted, is present in repo, was added 3 months ago to master branch.

I’ll need to do a complete database update to purge the current device from the system. When a device is deleted in the database, the github repo doesn’t get updated to remove it there, so I need to delete and generate the complete database.

I will try and do that this weekend if I can - if there’s not too many problems I’ll publish it, but if there are many issues, it may need to wait until Christmas as I’m away for a couple of days from Sunday.


Super. Thank you a lot! :slight_smile:

@chris Hello. Sorry for disturbing you in Christmas. :slight_smile: Do you have any news about DB update and device remove?

I’ll trigger that now.

@sihui FYI this will probably update most devices as the database now uses a different XML reference (removing the ESH references). This was changed a month or so back, but after the last full export. That will make it hard to see changes as we’ll have near on 2000 updated files :roll_eyes:.

Thx, no problem.
I’m expecting a lot of changes for all the zwave christmas presents. :grinning:


@chris @sihui - thank you a lot! :slight_smile:
I installed version:

297 │ Active │ 80 │ │ org.openhab.binding.zwave

And now switch configuration is available, item is discovered with dbReference 1014


Hello, I have same CoolCAM Power Plug and same issue with 2.5.0 Z-Wave binding. Where can i get newer version?


Thank You! Can You share some tips how to update existing binding? I’m little confused with this. I’ve tried use script but it doenst work on my RPI. I’ve tried to login to openhab console and do binding:update URL but it didnt work.

Script didn’t worked for me too.

I did next steps and, at least, it works for me now. Before executing them, please, read all of them and make sure, that you understand each of it and you know how to execute it.

  1. Download all needed jar files ( org.openhab.binding.zwave-2.5.1-SNAPSHOT.jar) and (xstream)
  2. Login to karaf console in raspberry (you should be already logged in to your RaspberryPi, ther execute the command ssh openhab@localhost -p 8101, password habopen)
  3. Remove zwave bundle using next command bundle:uninstall org.openhab.binding.zwave
  4. Go to paperUI and Uninstall Z-wave binding if it’s shown as installed (Addons -> Bindings -> Z-wave 2.5.0).
  5. Logout from karaf and copy both jar files to directory /usr/share/openhab2/addons
  6. Login back to karaf and install transport-serial feature:install openhab-transport-serial
  7. Check list of installed z-wave bundles list -s | grep zwave - there should be only one zwave binding with new version
  8. Remove your thing (Neo plug) and add it again in paperUi - then it should work. If no, restart OH2 and clean the cache (openhab-cli stop, openhab-cli clean-cache, openhab-cli start). Also, it’s recommended to remove (not exclude from network!) and add all things, except the controller, which are z-wave devices. In my case this was not needed.