Invalid configuration for Fortrezz Mimolite

[digitaldan]

I'm running a snapshot version of OH3 from March 25th, and i noticed that my Mimolite is no longer working with the following error which has to do with the configuration validation in core that was recently introduced. I was not sure where to report this as i know the device DB is generated elsewhere, so starting here. I went ahead and modified the /org.openhab.binding.zwave/src/main/resources/OH-INF/thing/fortrezz/mimolite_0_0.xml file to match the default values to what is in the config description options (so 187 instead of -69 for config 4_1 among others), which seems to have at least prevented the error message from happening. Let me know how i can help, thanks!

 Attempt to apply invalid configuration 'Configuration[{key=config_11_1; type=BigDecimal; value=0}, {key=group_5; type=EmptyList; value=[]}, {key=group_4; type=EmptyList; value=[]}, {key=group_1; type=EmptyList; value=[]}, {key=group_3; type=ArrayList; value=[controller]}, {key=group_2; type=ArrayList; value=[controller]}, {key=config_2_1; type=BigDecimal; value=0}, {key=config_7_1; type=BigDecimal; value=-2}, {key=config_8_1; type=BigDecimal; value=3}, {key=config_9_1; type=BigDecimal; value=3}, {key=config_3_1; type=BigDecimal; value=0}, {key=config_4_1; type=BigDecimal; value=-69}, {key=config_5_1; type=BigDecimal; value=-85}, {key=node_id; type=BigDecimal; value=51}, {key=config_6_1; type=BigDecimal; value=-1}]' on thing 'zwave:device:512:node51' blocked. This is most likely a bug: {config_7_1=The value -2 does not match allowed parameter options. Allowed options are: [ParameterOption [value="254", label="Default (0xFE)"]], config_4_1=The value -69 does not match allowed parameter options. Allowed options are: [ParameterOption [value="187", label="Default (0xBB)"]], config_5_1=The value -85 does not match allowed parameter options. Allowed options are: [ParameterOption [value="171", label="Default (0xAB)"]], config_6_1=The value -1 does not match allowed parameter options. Allowed options are: [ParameterOption [value="255", label="Default (0xFF)"]]}

[cdjackson]

If the database is not configured correctly, then with the latest changes to the core, the device won't start. All data was changed to be signed values to avoid problems since this is the requirement for ZWave. I'd suggest to check the database to see if this is configured correctly.