Review request for 76592/ZWN4016 Enbrighten Z-Wave 800 Series In-Wall Smart Switch

Add-ons Bindings
1

I would like to request a review of the 76592/ZWN4016 Enbrighten Z-Wave 800 Series In-Wall Smart Switch that I have attempted to put in the database. Info is here. Type 4952:3438

Not sure if I added it properly, but it’s a start. @apella12, maybe you can take a look?

thanks

2

LGTM except I zapped the min Firmware since it is the only device with 4952:3438. Usually reserve that when multiple devices with the same type:id. The manual doesn’t give a lot of information about the parameters, so assumed they were ok.

Not sure when Chris will have time for official review, but you could download and add to your jar to test/use.

3

This is just the kind of thing Thing Type File Provider [4.1.0.0;6.0.0.0) was created for. If you install this add-on from the marketplace, you can put the generated XML file under conf/thingtypes and test it straight away. No manipulation of JAR files needed.

2 Likes
4

Thanks - this worked. Loaded up the File Provider, added my xml, and my switch works fine.

1 Like
5

There was a major backport for the OH zwave binding, primarily to get the “thing actions” (like remove node, heal node, remove devices, etc. working again. A DB update that included this device was also backported. If you are running release versions, I’d recommend the OH5.1.2 patch release. You can just use the included binding. The only remaining issue is the network map action, but I have an open PR to fix for 5.1.3.

6

Interesting. That means that I really have no confirmation that the File Provider is doing anything, since I have recently also updated to 5.1.2. I guess it doesn’t matter much either way - the device is working fine for me. Thanks for the update.

7

I wouldn’t recommend providing the same ThingTypeUID using the File Provider and bundled with a binding. Not that some “big crisis” could arise, but there’s no telling which version will be used or if that is even consistent. Therefore, if the XMLs are a little bit different, the system could “randomly” see on or the other, which might not be ideal :wink: