Ah, yeah, seems like protection was enabled. I’ve tested setting local and rf protection via z-wave command and it works well, but I haven’t tested it with open-zwave so maybe something funky happened there. With the protection command class there are two types and they each have 3 levels.
8x tap on the config button toggles local protection between 0 & 1. The local & rf command to change the setting (via z-wave) are in the same packet to the device. It is possible that open-zwave sent the wrong values which sounds like it might have happened.