Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Zooz ZSE70 Outdoor Motion Sensor #7123

Open
3 tasks done
jhmartin opened this issue Aug 25, 2024 · 13 comments · May be fixed by #7381
Open
3 tasks done

Add Zooz ZSE70 Outdoor Motion Sensor #7123

jhmartin opened this issue Aug 25, 2024 · 13 comments · May be fixed by #7381
Labels
config ⚙ Configuration issues or updates help wanted Extra attention is needed

Comments

@jhmartin
Copy link

jhmartin commented Aug 25, 2024

Checklist

Which device is missing?

Zooz ZSE70 Outdoor Motion Sensor

Manufacturer ID

0x027a

Product Type

0x0004

Product ID

0x0006

Firmware Version

1.20

Is the device listed on the Z-Wave Alliance website?

No response

Do you have a manual?

https://www.support.getzooz.com/kb/article/1726-zse70-outdoor-motion-sensor-specs/

zooz-zse70-800lr-manual.pdf

@jhmartin jhmartin added the config ⚙ Configuration issues or updates label Aug 25, 2024
@jhmartin
Copy link
Author

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.

@jhmartin
Copy link
Author

zooz.txt
Debug info attached.

@NellicusLabs
Copy link

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

@MichaelStruck
Copy link

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.

@AlCalzone AlCalzone added the help wanted Extra attention is needed label Oct 30, 2024
@zwave-js-assistant
Copy link

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:

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

Thanks!

@hceuterpe
Copy link

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.

@AlCalzone

This comment was marked as outdated.

@AlCalzone

This comment was marked as resolved.

@AlCalzone
Copy link
Member

@zwave-js-bot import config 5150 from zwa

@zwave-js-bot zwave-js-bot linked a pull request Nov 8, 2024 that will close this issue
1 task
@zwave-js-bot
Copy link
Collaborator

🔨 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!

@AlCalzone
Copy link
Member

@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:
grafik

@hceuterpe
Copy link

hceuterpe commented Nov 8, 2024

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?

@hceuterpe
Copy link

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config ⚙ Configuration issues or updates help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants