node-zwave-js VS open-zwave

There's also the Z-Wave JS command-line flash utility (same code used by ZUI). Still requires node.js, but easier than installing ZUI, if the latter is not in your plans. https://github.com/zwave-js/node-zwave-js/tree/master/packages/flash

First, it's not in the ZWaveJS database yet, so I can't reconfigure anything for it (via Home Assistant). The dimmer/on/off all work, but I'm unable to change the device settings (like dim time, scene triggers, etc). I've opened a request about it, but have no idea what that time frame looks like. I've pinged the company about this and they're going to look into it.

I found the solution, the problem was with z-wave-js and the device, here is the resolved issue in GitHub for future reference https://github.com/zwave-js/node-zwave-js/issues/5599

Responding to a merch message related to Z-Wave problems. If they are using a 700 series stick then that is your network problem. You'll need to update the firmware to fix it https://github.com/zwave-js/node-zwave-js/issues/3906

Be careful using RGBGenie z-wave stuff. I have one of their touch panels, and it doesn't work in Home Assistant with zwave-js. Likely never will unless RGB Genie releases a firmware update for it. It works fine in Hubitat though, where a custom driver was written.

The Z-Wave JS author is on Reddit sometimes, so maybe he'll see this, but you'd get a better answer on GitHub. https://github.com/zwave-js/node-zwave-js/discussions

I checked the zwavejs device database, and it looks like the device doesn't have anything configured.

I just checked this thread - not sure if Aeotec has a different firmware then the 700 series zooz, but looks like the new firmware is markedly better but still has some issues as of 10 days ago: https://github.com/zwave-js/node-zwave-js/issues/3906

I second this - I've been doing it for the last 4 years in a library with over 10k active users. Node.js might not be as fast as C for some tasks, but when the hardware you're talking to is the limiting factor, it just doesn't matter that the driver could be 4x as fast.

OpenZWave seems to not use NIFs, instead working off hand maintained equivalents. When they added the HD200.xml files, they specifically left off Supervision on these switches, and even then seem to have had to patch in verifyOnChange later.

Researching this a little more, it appears there is a Homebridge plugin for Openzwave (https://github.com/shnhrrsn/homebridge-openzwave#readme), which would require installing OpenZwave itself (https://github.com/OpenZWave/open-zwave) - possibly through these instructions (https://github.com/OpenZWave/node-openzwave-shared/blob/master/README-raspbian.md). Does that look like it would work?