Closed billfor closed 1 year ago
Falling back to the 3.2 binding does not fix the problem.
This is caused by changes that were made in the core a couple of versions ago. You either need to edit your configuration to change this to 1, or wait for the next release (hopefully in a few days time).
Thank you Chris. I see that the modbus change in 3.3 probably broke some stuff. It is not urgent I just wanted to make sure you were aware. I will read up on how to edit the configuration if I need it to work now.
Any changes to modbus shouldn't impact the zwave binding. A big change was made to the core a little while back that added more checks to parameters in config files. This caused issues with a lot of bindings, and revealed some configuration issues in the database.
It should, hopefully, be fixed in the snapshot, and there should be a new milestone release this weekend.
Confirm fixed in org.openhab.binding.zwave-3.4.0-20220815.034709-15.jar. Thanks Chris.
No problems with this device on openhab 2.x to 3.2, until updating yesterday to 3.3.
HANDLER_CONFIGURATION_PENDING {config_15_1=The value 0.0 does not match allowed parameter options. Allowed options are: [ParameterOption [value="1", label="Factory Reset"]]}
In order to ensure we have the best information to deal with the issue, please fill in the following information (delete as necessary depending on the issue).
If the problem is associated with a device, please provide the following -:
Device name: Z-Wave Node 005: YRD446 Yale Real Living Key Free Touchscreen Assure Lock with Z-Wave and Bluetooth
Link to database: https://www.opensmarthouse.org/zwavedatabase/624
Provide a full debug level log of the problem. Preferably, you should try use the log viewer to see if you can identify the problem.
If a device will not initialise, ensure the log is provided from the time OH starts.
Thank you.