I have seen that error too but it creates the entry. The website still has some “gremlins” to be worked out.
The entry was created and is here.
Thanks Bruce and Sihui -
Solution was to create a new DB entry
Good to know about the creation of DB entries even if it throws an Error. Once clicking your link I saw the validation error on the Manufacturing in the Label -> I guessed that might have been the issue and retried with just the device name -> potentially it was already created and errored out for that reason the second time.
DB entry updated, xml exported, and installed on my OpenHAB instance. Everything Works. I’ve submitted it for review in the DB.
You are right. One should never give support in this forum when in a rush, sorry.
1 Like
Unfortunately I do that all to often too. Age gives both wisdom & impatience 
1 Like
I am having the same unknown device issue with my ZW4103. I am running OH 2.5.11 release build. The device is not listed under supported things in the z-wave binding. I see the database entry on OpenSmartHouse and that it has an approval date followed by an OH-3.0.0 tag. Does this mean I need to upgrade to OH3 to pick up the supported thing or can I somehow upgrade the binding?
Welcome
The easiest way would be to manually install a snapshot version of the binding. This script should make it easier. The manual instructions are in the README file.
Zigbee and Z-Wave manual install script - Tutorials & Examples - openHAB Community
Thanks, I’ll give it a go.
1 Like
17 months later, I’m circling back around to this topic.
Recently purchased the Jasco 28169 ZW4103 and I think it is not in the Zwave DB… at least for openhab3.
Should I search for and follow the correct approach to have this created in the OH3x version DB?
Thanks,
Todd
It is in the database - there is no “openhab 3 database”
You device has a slightly different device id though so the question is if yours i s the same - if so, it just needs adding to the list in the database.
Actually, on further investigation, yours is a different manufacturer than this, so it will in fact require a completely new entry.
Thanks Chris,
I’ll try to get this figured out and let you know.
Todd
So I finally opened up the sheet that came with this device…
It is JASCO
28172-3
ZW4104
I MUST have fat-fingered this initially.
I don’t see this in the DB, either.
Thanks
You may be able to go back to @chris original suggestion.
There is a device that looks close
Your reference numbers (20562:12345) are 5052:3039 in Hex and MFG is 99 (63 in hex). Take a look to see if that device has all the parameters in your manual
Bob
Thanks Bob.
I’ve been trying to find a viable way to locate the device XML in my installation to no avail.
I believe this is what is required for this new device: (added manually to this post)
Manufacturer: Jasco Products
Manufacturer ID: 0063
Label: Jasco 28172-3
Category: Power Outlet
Description:Plug in Smart Switch
Device Type: NODE_TYPE_ZWAVEPLUS_NODE
Device ID: 12345
Firmware version: 5.22
ZW4104
This is what I copied from the device in the OH3 GUI:
zwave_class_basic BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic GENERIC_TYPE_SWITCH_BINARY
zwave_frequent false
zwave_neighbours 2,3,4,6,7,8,9,11,14,15,16,18,21,26,30,31,35
zwave_listening true
zwave_plus_devicetype NODE_TYPE_ZWAVEPLUS_NODE
zwave_version 5.22
zwave_deviceid 12345
zwave_nodeid 34
zwave_lastheal 2022-06-12T08:18:01Z
zwave_routing true
zwave_plus_roletype ROLE_TYPE_SLAVE_ALWAYS_ON
zwave_beaming true
zwave_secure false
zwave_class_specific SPECIFIC_TYPE_POWER_SWITCH_BINARY
zwave_devicetype 20562
zwave_manufacturer 99
So, is this just something that can be updated somehow? 
Let me know my next steps.
Thanks
Todd
If I were you I would go to the database and check out the parameters and endpoints of the device I pointed out versus your manual. If they match you can simply add 5052:3039 to the list of references.
If not, you will need to find the XML it should be in openhab-userdata/zwave, but that depends on how you installed OH.
If you do not have Db access follow the guide provided above.
Bob
I’m using openhabian on PI.
I’ll look again for the XML.
Thanks again!
Todd
This one has a different manufacturer ID I think, so it’s not possible to just add the new device type unfortunately.
Well, looking in the OH GUI, it shows:
- zwave_manufacturer 99
which I think are all the other JASCO devices Manufacturer ID (HEX 063)
I think you had first looked at Honeywell.
But I have other versions of this same switch that are GE/Jasco.
They have this id as follows:
zwave_class_basic BASIC_TYPE_ROUTING_SLAVE
zwave_class_generic GENERIC_TYPE_SWITCH_BINARY
zwave_neighbours 2,3,4,6,7,8,11,14,15,18,21,29,30,31,32,34,35
modelId GE 28169 / Jasco 28168
zwave_plus_devicetype NODE_TYPE_ZWAVEPLUS_NODE
zwave_version 5.23
versionMin 5.0
defaultAssociations 1
vendor Jasco Products
zwave_routing true
zwave_beaming true
zwave_secure false
zwave_class_specific SPECIFIC_TYPE_POWER_SWITCH_BINARY
zwave_devicetype 20562
zwave_frequent false
zwave_listening true
manufacturerId 0063
manufacturerRef 5052:3037,5052:3038
dbReference 1045
zwave_deviceid 12344
zwave_nodeid 9
zwave_lastheal 2022-06-09T08:50:03Z
zwave_plus_roletype ROLE_TYPE_SLAVE_ALWAYS_ON
zwave_manufacturer 99
So I’m wondering if THIS device (above) can be referenced.
I’m just not sure where to put that REF. ```
5052:3038
Exactly - so the manufacturer is different - right?
You have the hasco - hex 63 - but the database reference for this device that I linked above is the honeywell - hex 39.
No - as I said earlier, you have a different manufacturer than what is in the database. Or maybe there is another entry for the ZW4103 that I didn’t find that is a Jasco version? At least you cannot just add your device type/id to the database entry I referenced above.
There are three devices with the same reference ID, two Jasco (063), One Honeywell (039) and appear to be the same (same picture, same parameter and same endpoints). Two versions also have the same association groups. What we do not know at this point is how they compare to the device @toddwevans possesses.
The device owned by @toddwevans needs to be compared to the existing devices and added in someway to the DB (either as additional reference IDs or as a new device), requiring @toddwevans to register, then open a ticket for write access. Then compare the parameters and endpoints. If adding reference numbers, the MFG need to be the same
Try either/both for the XML that is needed for a new device
a) srv/openhab-userdata/zwave or
b) var/lib/openhab/zwave
Bob