Any Tutorials or Guidance on adding unsupported ZWave devices to ZwaveJS?

Configuration Z-Wave
1

Update: It turns out the root of my problem is the fact that the manufacturer’s ID is incorrectly programmed into the device. I have no idea how HomeSeer was able to add and use it. I’ve reached out to Zooz so hopefully they can either help me fix the programming or replace the device.

Thanks again for the help.

Sorry for another noob question. I’m slowly building a new Z-Wave network with “almost” entirely 800LR devices, but I have a few “older” devices that I’d like to remove from an old network and add to my new network.

They are not in the ZWave JS device database, but after doing a lot of reading, it appears that I can add them, maybe???

However, the instructions for doing this are rather vague. Any guidance or tutorial, particularly, step-by-step, would be much appreciated.

2

I have never heard of an unsupported zwave device, TBH…

2 Likes
3

The official docs are pretty detailed, which part is vague? https://zwave-js.github.io/zwave-js/#/config-files/contributing-files

There are hundreds of existing files, a good start is to copy a similar one.

4

See. I told you I was a noob. By unsupported, I meant a device that is not in the device database and is therefore not properly identified. At least that’s what I think I meant. Looking at the official docs now.

5

This is where I feel really dumb. I’m looking for the device config files that are supposed to be at packages/config/config/devices/… but I can’t find packages anywhere. I’m ssh’d in and running HAOS. What am I missing?

6

They are on GitHub. https://github.com/zwave-js/zwave-js/tree/master/packages/config/config/devices. Well they are also in the add-on container buried in a node modules directory.

You can also find them at the online device DB: https://devices.zwave-js.io/

Use the editor setup as described at https://zwave-js.github.io/zwave-js/#/config-files/contributing-files?id=editor-setup to configure a development environment to add the new files.

You’ll need to use Z-Wave JS UI to test, as the core Z-Wave JS add-on does not support custom config files. https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files

If that’s all too much for you, then consider just submitting a missing device and maybe someone will add it for you. https://github.com/zwave-js/zwave-js/issues/new?template=device_config.yml

It’s surprising to find old devices still not listed in the DB (of course, still possible). Are you sure they are not there already, just with different IDs?

7

Thanks for the quick reply. “Well they are also in the add-on container buried in a node modules directory.” This is the part that is tripping me up. I would think that I could/should create a config file and test it out before submitting to Github. I’m very new to this architecture so please excuse me. How do I get to the add-on container? Again, I’m running HAOS on a Pi400.

8

If you’re using Z-Wave JS add-on, then you don’t.

Switch to Z-Wave JS UI if you want to test config files.

1 Like
9

I “think” I’m using the Z-Wave JS integration along with Z-Wave JS UI, which is an add-on right?

10

Then you follow the instructions at https://zwave-js.github.io/zwave-js-ui/#/device-support/custom-device-files

You can access the Store directory from the Z-Wave JS UI web UI. Create a config directory and add the files there.

image
image894×792 31.6 KB

11

Thanks for your patience with me. It’s sinking in now.