This is probably in the ZWave catalog, but the site is misbehaving for me: "There are over 0 interoperable Z-Wave products throughout the world" and returns no search results.

zooz.txt
Debug info attached.

+1. I was having an issue and then found this issue for the sensor not currently being present in zwave-js on HomeAssistant

Just purchased this and noticed it is not listed in the database or in Zwave JS (device: 0x027a 0x0004-0x0006). Operational, however, in Home Assistant as is.

Because of the large amount of Z-Wave devices, we cannot write all configuration files ourselves.
Help from the community is required, so we can focus our time on improving Z-Wave JS itself. 🙏🏻

This issue has been labeled "Help wanted", meaning we kindly ask anyone who wants to help out for support. Here are a few resources to get you started - don't hesitate to ask if you are having problems:

• Contributing configuration files
• Importing from other sources
• Configuration file format
• Style guide

We may get around to doing it ourselves at some point, but community support will speed up this process immensely.

Thanks!

The device was added to the Z-Wave Alliance DB 4 days ago. I'd be interested in helping to add this (I own four of these). I haven't done this before though so I'll have to spend some time to get up to speed on how to generate.

@zwave-js-bot import config 5150 from zwa

🔨 I created a PR at #7381 - check it out! Usually, I'm going to need some help from a human to make sure the configuration matches the style guide.

If anyone feels compelled to help out, please follow these steps:

• Fork this repository if you haven't already. If you have, synchronize your fork so you get a copy of the new branch.
• Make the necessary changes in the branch import-config-1731057890 in your fork
• Create a pull request with your branch import-config-1731057890 as the source and our branch import-config-1731057890 as the target.

Thanks!

@hceuterpe if you are going to do this, I really can't stress enough editing the files in VSCode, like the documentation states. We have an extension for that, which allows you to see a preview of the parameter definitions and which highlights common errors:

I finished up the revisions. That modified file passed the config linting command with no errors or warnings. It really wasn't that difficult. I always wondered if there was a way to convert the Z-wave DB XML files into the json config files. Glad to know where it is now :)

I'm testing it out now in my system. If someone else here has a devices and they want to test it out, let me know and I can attach it so you can try out.

My only question is this: The majority of the 800LR devices Zooz has released do not distinguish the 800LR in either the device label or filename (actually it seems all but one, ZEN37). ZSE70 also hasn't existed before the 800LR chipset revision. Do we want to just shorten the filename and label to ZSE70?

One other thing, in the zse44 config file, the manual URL incorrectly points to the zse43. Probably better to deal with that in a different PR though...