Is the OpenSmartHouse Z-Wave Device Database still active, I opened a ticket to get editor access but am getting no answer…
Regards,
Maxime
The native Zwave developer does a lot of international travel, so that could be the reason. The ZWDB is still used and there was an update on 5/18/2026.
I think it’s a “challenge” that write access is needed to export the XML files. I wish we could extract that to some standalone tool of some sort, but I’m not sure exactly how that would look. The repo doesn’t look like it’s in use though, it can’t be that nothing has been done to the web page in 6 years..?
There was some discussion on one of my PRs on this repository. There were untracked changes after the initial creation and the plan to update the repository wasn’t able to be completed. I now just open a ticket in the ZWDB if there is something I need changed.
It is probably possible to export an XML file without write access, although this seems of limited use IMO. If the XML is already in the binding, it could be pulled from that repository (and modified if needed) without any special access. Interestingly, the ZW-JS has a feature to extract the OH ZWDB information into a JSON format without needing access. I’ve used that to contribute several config files that were not in their DB.
As to the OP issue, I don’t want to take away anybody’s fun, but if you post the XML that the device generates in the openhab/zwave folder, I could get you going with something to test.
Yes, it’s just that it requires that you know how all this is connected and where to find the files, that can be done. But, it’s much easier for people to find the device, or a similar device, in the DB than in the GitHub repo. In some cases, if you get your hands on an almost identical ThingType definition to what you need, you can probably modify a few details manually in the XML and get something working.
That would be my preferred way to do it even though I have write access. Because, I’d want to test that everything is correct in my definition before adding it to the database. But, even if it’s just to get some unsupported thing working, I think it would make things easier if you didn’t need write access to export the XML.
That is interesting, and something I should probably look into. My goal is that the Z-Wave binding shouldn’t be allowed to “die” because of lack of attention/updates. The easier it is for people to figure this out, the easier it is to get devices working and thus keep the whole thing “alive” instead of everybody transitioning to ZW-JS.
@Nadahar
That would be nice! Here is the XML file from one of them (I have 3 identical)
network_c4723d6a__node_84.xml (12.9 KB)
It was good you posted the XML. Before this can be added to the ZWDB (by anyone) SmartWings needs to be added as a new manufacturer. Modify your ticket for write access to include asking for the new manufacturer SmartWings (0x046a) to be created.
I’ll still see if I can create a test file later today. What version of OH are you on?
Ok, thanks for the advice!
I’m on 5.1.4
I did validate that the mfg is needed to create a ZWDB entry. Instead, I marked this up manually from similar device. Also used this as a reference. Hopefully no mistakes.
wm25lv_0_0.xml (10.6 KB)
For testing now;
One option is to use the @Nadahar process. He can provide guidance I’m assuming it can handle a device XML without a manufacturer folder. I haven’t used it, but others have.
There is another option here if that doesn’t work but is a little trickier because you need to add a smartwings folder and need the JDK installed. I also did it with 7-zip as a test (without the JDK), but not sure what you are comfortable with.
If you do get it into the binding, simply delete (do not exclude) your current thing and Inbox-Zwave-Scan to pick it up with the parameters and channels.
The manufacturer folder is just a way to organize the definitions in the binding I think, I can’t see that there’s any “functionality” in the folder itself? As far as I can tell, it should work just fine.
The add-on can be installed using the marketplace, and the use instructions are very simple. Just install the add-on, place the file in the designated folder (you must first create it) and restart OH. It should be detectable by the Z-Wave binding if you do a new scan.
Unfortunately, because of a shortcoming in the Z-Wave binding, it doesn’t “see” if the file is modified, so you must restart OH after every modification you make to the file.
Don’t know why, the Thing Type File Provider did not work… Even after rebooting OpenHab.
Ended up adding the xml to the binding jar with 7-zip.
That worked!
@apella12 Everything seems fine in the xml. Thanks again!
Now the waiting game to get it in the official release…
Glad that got you going!
I would suggest that you add your device as soon as you have write access and the new MFG is added to give it the best chance for the 5.2 release in July. Two other tips;
-
After the XML is successfully added, use the gear icon to copy device data from Device 1628. As noted above it is a close match but from a different MFG. It will save a lot of time, even though it is tedious to find the device (there is no order that I can decipher in the dropdown). You will need to add the battery alarm channel, if that doesn’t appear.
-
Don’t forget to mark as ready for review on the first tab after you are done.