The answer is a bit of “kind of”.
The current path forward for HA is ZwaveJS Server (Websocket) → ZwaveJS HA Integration. Right now the ZWave JS integration does not have a UI that can modify parameters, but it is on their path.
There is a second ZwaveJS2MQTT add-on that can be spooled up after taking down the ZwaveJS Server (however you are hosting) and using the same usb stick/network key, it can read in the nodes and DOES have a UI that can make changes. It can be used to serve the HA integration via websockets OR MQTT, but this is not the path forward for HA.
So what I currently do (again we are talking maybe a few months of this before HA integration has a UI) is:
- Take down ZwaveJS Server
- Spool up ZwaveJS2MQTT
- Change parameters, test, etc.
- Take down ZJS2M
- Spool up ZJS
Whole process takes about ~10 minutes to make changes, which, yes, admittedly is a pain, but it’s a workaround for MAYBE a few months for a MUCH better future outlook.
All of that said, they are ALSO working on a service that would allow automations to perform parameter changes based on events. The old integration you could program it to say “zwave.set_config_parameter”, send a snip of code, and it would change the parameter. That is ALSO in development and forthcoming, but is not currently available.