Hi
I’m trying to change some parameters for my Aeotec ZW100 Multisensor 6, but it does not seem to stick.
In the “old” ZWave integration, there was a Set Parameters button, but i cannot see a similar button in the OpenZWave web gui.
Thanks
i think you have to do it via the daemon VNC UI instead. and dont forget to wake up the device when you send the command !
It doesn’t work with the UI, there seems to be a bug in the frontend, I reported it on Github.
@Dal I posted how I got it to work here. Let me know if you need some help.
1 Like
Another option is through Developer Tools / Services /ozw.set_config_parameter. You provide the YAML for the parameters e.g.
node_id: 36
parameter: 21
value: 1
So many smart people in these forums, never seizes to amaze me 
I tried the Developer Tools / Services / ozw.set_config_parameter way.
I found the values by looking through the OZW log file.
I can see the parameters change in real time as I change them through Developer tools.
But it doesn’t seem to help much.
I try to change the On Time label 90 (I’m assuming that’s seconds)
Enable Motion Sensor is set to Level 5
Command Options is set til Binary Sensor Report
But according to debugging in Node-RED:
After receiving an “on” in binary_sensor.zw100_multisensor_6_home_security_motion_detected, it receives an “off” after just 5 seconds.
And then it don’t bother to listen for another motion detection (I have waited 10 minutes now)
Am I still missing some kind of apply button?
A simple node setup should not be this hard, IMO
Doesn’t work for the Aeotec multisensor, or at least it didn’t for me for changing the values to be included in a group report.
Looking at the config list ( Product Configuration Capabilities (z-wavealliance.org)) it made me wonder if the issue is the parameter size in bytes being sent correctly and if that can be an issue. I never thought to trace this somehow, or look at source.
There is a new version of OpenZWave (beta) out now (v 0.8.0).
Maybe it works better. I will try later today.
Thank you