This helped me with another device, door/window sensor, which i added a long time ago, but not with this new plug.
As I wrote in my post, I removed and added the thing without any result. I also removed device from network and included it again without security and like new nodeId - also no configuration. BTW, I noticed that device manual also didn’t appeared on page.
The one more problem with this device is present.
Please, see attached screen - Electric_KWH is reported twice, once with -2… value, and once with voltage value. It’s really strange.
Ok, i found the problem - my device is recognized for dbReference 1117 which is marked as deleted…
But the question is - why it uses that device and how change this?
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1117
Update to the latest zwave snapshot binding and delete the Thing and readd it.
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 │ 3.0.0.201912190353 │ 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?
Your type and id definitely points to a valid database entry:
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1014
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 
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=]
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.
2 Likes
Super. Thank you a lot! 
@chris Hello. Sorry for disturbing you in Christmas. 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 
.
Thx, no problem.
I’m expecting a lot of changes for all the zwave christmas presents. 
2 Likes
