<parameter name="config_duration" type="integer" min="1" max="254">
<description><![CDATA[Sets the dim rate speed<br>Values from 1 to 127 are defined in seconds,
while values from 128 to 254 are defined in minutes.]]></description>
<option value="255">Device Default</option>
<option value="0">Change Instantly</option>
This is the config parameter that the error relates to, but this definition looks ok to me so I’m not sure what it’s complaining about unless the value is outside the allowable range of less than 0, or greater than 255. Can you check this to see what it’s set to? The default is 255 so this should be ok unless it was changed.
The problem relates to the rigorous checking introduced in 3.3M2. Since this is handled by the core, it is not a zwave issue. What needs to change is this in the DB? (edit: Actually I do not know where this needs to be changed) (change 254 to 255)
The 254 is being picked up by the checker as max, even though the default is 255. I had a similar problem with a different device where the default was outside the range the checker checked. (if that makes sense?)
Can you link to the file where this definition is made. In case 255 has a special meaning (and is outside of the defined range 1 to 254 it should be added as <option />. If this is the case and the check fails, it’s a bug in the checker.
$ sudo apt update
Hit:1 http://ppa.launchpad.net/mythbuntu/31/ubuntu focal InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu focal InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease [108 kB]
Get:5 http://us.archive.ubuntu.com/ubuntu focal-security InRelease [114 kB]
Err:6 https://openhab.jfrog.io/artifactory/openhab-linuxpkg testing InRelease
502 Bad Gateway [IP: 126.96.36.199 443]
Fetched 336 kB in 10s (33.7 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch https://openhab.jfrog.io/artifactory/openhab-linuxpkg/dists/testing/InRelease 502 Bad Gateway [IP: 188.8.131.52 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
If there is the “handler” message, it is related to the last 24 hours of posts directly above yours. The quickest thing will be to edit the channel to 254 step duration (edit: based on subsequent posts setting to 254 would fall into the “bad idea” category ), pending either a validator change or binding change.
You might not want to use 254 - this will set a dim rate of 254 minutes - 4 1/4 hours
Additional checks were added in the core, but if I remember correctly this was in the previous milestone a few months back, so I’m not sure why this has just started now. I assume this is a bug in the core, but again, I’m not sure what changed, but this config definition hasn’t changed for 6 years according to GitHub.