Duplicating Z-Wave DB entries?

I have started with openHABianPi (great!) and am looking at Z-Wave devices which are missing from the DB.

Looking at the Z-Wave DB for openhab2 with search term “FGRM222”, I see that there are already multiple entries for the same device.

Q1: is this considered normal ? Would it not be better if the same device can have multiple device IDs and firmware versions ?
Q2: how would I create another copy ?

thanks, Kai

Yes.

Yes, but it becomes VERY difficult to control. Different versions of devices may have different parameters, or the same parameters with different sizes or ranges, or different association groups or command classes. So, while I can understand where you’re coming from with this question, it’s difficult to manage changes between versions, so we treat them as separate devices (which I know has its own difficulties).

There’s a copy function in the database - it asks you for the source device, and will copy the parameters (associations and parameters) into the current device. Note that it won’t work if there are already parameters configured (to avoid an accidental mess! :wink: ).

Oh, I was looking for that and couldn’t find it. After Reating The Fine Manual, I now know that this copy function is after the upload of the XML file … which was what I wanted to avoid in the first place.

Sorry, but I seem to have more questions on the Z-Wave DB site …
Do I need to have a login ?
If so, where do I get one ? There doesn’t seem to be a way to sign up.
Is there any way in the web UI of Openhab2 to get the xml file that is required for the DB upload?
Or is there a way to click a button in openhab2 and it automatically sends it to the DB, so that I don’t have to go fishing for that file ?
What is supposed to happen after I uploaded the XML file ? I was looking at an empty page, it didn’t look right.
How is the complete process from noticing a device that is not recognised in your paperUI inbox until the point where it starts working like the other ones?

Thanks for all your help!

I’m not sure that it’s exactly necessary to load the XML first - you could probably create a database entry manually. However, the XML is automatically created by OH, so it’s easy and safer to load it and safer than trying to add stuff by hand.

Yes - you need to register first, then email me so I can give you write access. It’s effectively open to anyone, but I need to stop robots hacking stuff…

I think you just click on the big Login sign at the top of the site -:

Yes, it’s created by OH and stored in the /etc/zwave folder in OH1, and the /userdata/zwave folder in OH2.

Sorry - that’s not possible (nice idea though :wink: ).

You get the database entry with the basic information filled in - from there you can add parameters, or copy them from a previous device and modify them.

  • If everything works well, then OH creates the nodeX.xml file
  • Upload this to the website
  • Create or copy the parameters and associations
  • Click the “Request Review” button
  • I review and export to github
  • The binding is generated
  • You update the binding, and it should all work.

Oh, one more:

[quote=“chris, post:2, topic:16007”]

kai-bcn:
Would it not be better if the same device can have multiple device IDs and firmware versions ?

Yes, but it becomes VERY difficult to control. Different versions of devices may have different parameters, […][/quote]
Understood … but in my case, it is just another Reference (Type:Id), because the firmware matches that of this entry:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/413

And I just realized there are indeed multiple Type:Id entries possible for the same DB entry. So maybe I can add 0301:1001 to the 2 existing entries of 0302:1000,0302:3000 ? Seeing that they have the same firmware version (24.24), I am hoping this would be OK. Thoughts?

Ok - simple then. Just add the type:id to the database.

Absolutely - this is perfectly ok.

1 Like