The “official” control panel in HA is growing with each release. 2021.4 adds support for viewing and changing device configuration. If you don’t absolutely need to remove a failed node or do a network heal immediately I’d hold out for that functionality to be added to the core control panel.
4 Likes
Yes, it was in the last week or two. In zwavejs2mqtt docker container 2.2.0 you could do it that way on the Inovelli Red dimmer, but their other devices (the switch, and light / fan combo) had it set separately. While it was like that, the max value was lower than it should have been though, so anything set to the “Chase” effect was rejected. It was split apart to be like the others by container 2.4.0. Sorry, I don’t have the zwavejs2mqtt versions to match the containers.
I posted a script to handle it, if that’s helpful:
weren’t we supposed to see the beta for 2021.4 yesterday? eagerly awaiting that functionality 
on another subject, I am on the verge of including a FGS-223 Fibaro Double switch, but read mixed experiences on the device. Is this yet fully supported on the current Z-WaveJS core integration/add-on?
Last Wednesday of the month, so the 31st this month
1 Like
Bummer! you’re right… sorry for that. Another week of anxiety coming up.
1 Like
Quick question - I am starting again from scratch and have a very small ZWave setup using zwavejs, and so far so very good compared to OpenZWave 
My question is this - can anyone recommend a wall based zwave lightswitch/dimmer that has instant reporting and works with zwavejs? I want hass to get updates as soon as the switch is hit rather than waiting for polling. When I last looked into this a few years ago it was very hit and miss, I am hoping that things have improved since …
Is zwave+ a guarantee of this functionality, or do I have to be careful?
Thanks!
1 Like
I’m testing zwavejs also and have three devices. Performance seems better and the system is much easier to setup, but I have trouble with reporting status. I use several Aeotec smart switches and they aren’t updating the GUI after manual presses. I’m still experimenting, going to try the Aeotec Multisensor 6 next.
1 Like
The Inovelli switches & dimmers are great and have instant reporting when the physical switch is toggled.
2 Likes
In my experience, all current generation zwave switches operate very quickly. I have a variety of zooz, ge and sylvania. By new I mean zwave +. Just glancing at my devices, I have at least 10 new ones from various manufacturers.
1 Like
I just upgraded a bunch of my old zwave dimmers to Honeywell UltraPro Z-Wave Plus Smart Light Dimmers. I believe these are basically the same as the GEs, but not as expensive. They work great.
2 Likes
I’d second Charles’s recommendation on Inovelli. Good product and great customer service and engagement. Their company founder is a regular on their discussion forums.
3 Likes
Excellent - sounds like I have a bunch of options which is great news. Thanks for the responses guys!
3rd for inovelli. I have 30 of their red series dimmers. The customizable LED bars are really worth it in IMO. Plus their forums are great too. You can talk directly with their CEO and CTO most of the time.
1 Like
May I ask what your method is for customizing the LED bars? Are you using a script or blueprint? I just switched over to ZwaveJS, so trying to figure out the best way right now. Thanks!
Using a modified script that was posted on the forums:
1 Like
@moto2000 Im writing the full parameter value to parameter 16 via MQTT. I use the ZWAVEJS2MQTT add-on, not the official ZWAVEJS add-on.
I use node red (i dont use HA scripts, automations, etc., everything done through node red)
Right now, the service call to write Zwave parameters is broken up into partial parametes, but heard they are fixing that. Then I may switch over to the service call as opposed to MQTT.
1 Like
Man I hope so, this is driving me crazy keeping up with the changes! Right now setting param 13 I am getting a value error:
service: zwave_js.set_config_parameter
data:
value: 255
parameter: "LED Indicator Color" <-- Also tried 13
target:
entity_id: light.master_bedroom_dimmer_current_value
Hello all … I am having an intermittent issue … about once every 24 hours my whole ZWave network goes down and commands send to ANY node return the following in the log:
Unexpected ZWaveError: Failed to send the message after 3 attempt.
If I restart the add-on then all goes back to normal. I have tried removing all the nodes and reading them and I have not replaced the ZWave controller USB stick. The problem remains.
Am I the only person having this issue? Where can I start troubleshooting?
Thanks!
Currently you have to use partials if partials are provided. You cannot set the full param. You’re most likely running into that issue because that expects a partial. Anyways @raman325 fix the partial issue, hopefully it makes the beta & 2021.4 release.
Also, that’s not an error?
we’d need to see the full error, not just the center chunk of the error. Please copy/paste the full error and format it, do not use a picture/screenshot. Also, that error is most likely the result of another error seeing that’s the 3rd attempt.