So after using my Vera Plus for Z-Wave for a while, I decided to go back to my USB stick. Feels great so far. But Zwave JS does not update my config params. I don’t get an error or something, but as soon as I retrieve the value again, it is back to the default value. More people experiencing this?
Wow. This worked perfectly for me a while ago but right now (ZwaveJS 0.1.49) it is not working. Changing a parameter does not stick. Have you filed a bug report on this?
I don’t see this problem. If they are battery devices, they must wake up before the setting is applied. You won’t see the change in HA until then.
The device I am testing on is an in-wall Fibaro device.
What I’ve found is that switching a parameter shows the parameter update being sent in the ZwaveJS log, and appears to update the HA webpage. If I reload the page, then the change is gone.
However, I believe it is updating the device. If I re-interview the device it then shows the correct value.
Interesting, calling the zwave_js.refresh_value service does not update the value.
So it looks like the problem is in the ZwaveJS–HA connection, not the ZwaveJS–device connection.
I’ll try updating to the latest ZwaveJS (0.1.52) and see if it makes a difference.
@freshcoast What version of ZwaveJS and HA are you running? What device did you test on? (And how did you verify that the change actually stuck?)
The refresh_value service only operates on entities, it does not refresh configuration parameters.
Latest of everything. Changed a config param on a wall switch. Refreshed the page in HA, it was the same as applied. Watched the value update immediately in the z2m control panel. Watched the driver logs showing the value being set and refreshed.
Interesting. I see this when I change a config parameter:
2022-01-27T19:42:17.018Z DRIVER » [Node 009] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 165
└─[ConfigurationCCSet]
parameter #: 54
reset to default: false
value size: 1
value format: UnsignedInteger
value: 0
2022-01-27T19:42:17.035Z DRIVER « [RES] [SendData]
was sent: true
2022-01-27T19:42:17.090Z CNTRLR [Node 009] Scheduled poll canceled because value was updated
And the page shows “The parameter has been updated.”
But when I reload the page the parameter is back to where it was before.
If I re-interview the device I see the right value on the page.
I’ll have to try updating over the weekend and see if it fixes it.
Ah, your version is very old and is known to be broken. Yes, you need to update.
Or just not set parameters. 
Each version I’ve used has been better than the last, and any update that breaks things results in a lot of frustration for the family. As a result I tend to be conservative unless something important isn’t working. I do check the change logs, but so far none of the fixes have struck me as particularly relevant.
The problem is not specific to config parameters. Turn on a light and the state won’t update. Maybe you just aren’t noticing?
If your devices always return a state update for a command, so a refresh is not necessary, then you might not see any problems. Config params usually require a refresh, so it’s more visible.
Turning on/off a light updates the state in the UI right away, so I haven’t noticed any problems. I can say that config updates worked fine when I switched to ZwaveJS, though. So, almost everything is working just fine with this version. Just not config parameters updates.
@dbs I think the problem must be somewhere between what @freshcoast and you are saying. But there must be a way to update the config param immediately right? Maybe, since the most battery powered devices are portable, keep the device awake by pushing the button on it every 10 sec? Idk, I still have to try that but I’m at work right now.
Also sorry for my late response, apparently I had notifications off 
No worries. I’ll try updating this weekend and see if it fixes it. My devices are not battery powered, so that shouldn’t be the issue.
So I think I had a little succes here. I took a motion sensor, kept pushing the button every 5 sec and tried to send a configuration param update. And when I refresh the config now, the new value shows…
When HA says: Value updated or api write succesful it has updated
Hello everyone,
i have the same issues with zwave js 2 mqtt / zwave js
Yesterday my aeotec z-stick 7 has arrived and i directly flashed the latest firmware.
i set up HASSOS (latest version in a Qnap VM) as guided on the aeotec help and added some fibaro motion sensors for testing which worked without any issues.
But when i want to reconfigue the wake up time, or other parameters like led brightnes or temperature report, debug shows that the new value is submitted to the node, but here is never a positive feedback if this is successfull. After some time (also waited till the next day) the old values appear again.
It neither works while pressing the wake up button every second. it only updates the paramenter when i re-interview the node while setting it in inclusion mode again.
it seems to me the write command is sent to a queue which never is beeing processed, because when i exclude the node (while i send some parameter changes before) debug then shows, writing of the new parameter was not successfull. but this is the only time where a negative feedback is shown.
Its also strange, that pings are also not successfull. When trying to ping a node, i press the wake up button on the sensor every second, but debug tells me ping is not successful. also the asleep icon only changed one time to a smiley, while the node was freshly added. when doing manual wakups via button, it will never show as awake.
are these issues with the fibaro motion sensors, or maybe the z-stick 7? finally i ordered a z-stick 5 too to see if this will work better.
or do you have any other tipps or tricks?
thx a lot in advance.
Hey! Is your issue resolved? Because the latest version of ZWave JS is awesome
Have you been able to update config params without keeping pressing the button on the sensor eg every 5 seconds?
My Zooz XS Sensor ZSE44 (firmware 2.0.0) is seen and sends temperature values but values are reverted back to defaults if I dont’ push the button.
More info:
Looks like the paremeter update works best if I change the parameter values then remove the battery for a second and then update the paremeter pages in Home Assistant.
Zooz 800 Series Long Range USB Controller (firmware 2.0.0).
Yes with the update since than everything is working fine