According to the OH 3.3 milestone discussion (see the entries around March 10th) a stricter check for configuration parameters was introduced in the core with milestone 2. Flaws in the Z-Wave database used in OH are now “visible” in the way you encountered. Note that this is not Z-Wave specific, other bindings are affected as well.
The best way forward is to correct the device definitions in the database, following the database user guide.
1 Like