Zwave OH3 Config Parameters

robmac · April 27, 2021, 2:00pm

I noticed a couple of Fibaro devices that have out of range parameters. I thought it was a UI handling issue as they used to be correct but possibly now I see this it is wrong in the database. Is it possible a few were changed during migration?

If I can have access to the new database I will fix as I come across them.

Bruce_Osborne · April 27, 2021, 2:07pm

It is doubtful that happened during migration.

I personally did not do the migration but worked on the backend scripts, primarily for creating new entries and for the device documentation that appears on the OH site.

shorty707 · April 27, 2021, 2:18pm

This is true for many devices I have.
I think it is related to

github.com/openhab/openhab-webui

Unable to use config control with INTEGER, options, and LimitToOptions=false

opened 08:19PM - 01 Apr 21 UTC

cdjackson

bug main ui

## The problem It is currently not possible to control most Z-Wave and many Z…igbee devices, and possibly other bindings as well as the UI incorrectly renders configuration parameters that have options defined, and also allow other values to be specified (ie `LimitToOptions` is `false`). @ghys stated on the forum -: ``` The combination of type: INTEGER, limitToOptions: false and options defined is not supported by the config parameter control at the moment. ``` https://community.openhab.org/t/zwave-oh3-config-parameters/119789/22 This is quite a major issue and affects around 875 ZWave things. I would suggest that if the control is not able to handle this for integers, that the UI instead renders a simple integer input both. This is probably better, but since the values defined in the options may be outside of the `min` and `max` values allowed for integers, it will still mean that some values cannot be defined. Often for example we may have an option `Disable` of (say) `255`, but the `min` and `max` are defined as `0` and `100` - so just rendering an integer input of `0 to 100` will still mean that the user cannot select 255.

Since “Options” are not correctly shown/handled on the UI. Those out of range values could possibly come from such a Option?

That was at least my interpretation why so many devices have this atm.

sihui · April 27, 2021, 2:52pm

Sure, done.

sihui · April 27, 2021, 2:53pm

Same here …

That was/is my assumption, too.

Bruce_Osborne · April 27, 2021, 2:56pm

Thanks. Sorry to bother you.

sihui · April 27, 2021, 2:56pm

No problem, I am still alive

Kellermeister · November 5, 2021, 8:08pm

hi
is the problem with writing the parameters for zwave devices via the ui fixed? does anyone know? if so, from which version? thanks

robmac · November 11, 2021, 9:57am

Setting multiple associations in a group can get in a bit of a mess. Z-Wave Association Settings not displayed and settings of multiple endpoints makes a mess · Issue #1194 · openhab/openhab-webui · GitHub