I read though this thread, but I didn’t see anyone mention this yet. Since this device uses the SECURITY Command Class, which is not included in the 2.2 release version of the binding, you will need the development version of the binding…
You’ll need to uninstall the 2.2 version first, then drop the jar from the first post into your addons folder. Or you can install it though Eclipse Marketplace. The opener will need to be excluded, and then I usually do a reset (5 presses of the button, and it will give you a few short beeps and then a long shrieky one). Then reincluded the device using OH (not the button on the stick) from close proximity to the controller. It sounds like you are familiar with the inclusion process, since you got it done the first time. You’ll also need to delete all of your Things and rediscover to pull in the updated ThingTypes. Not excluded/reinclude… just delete the Thing.
And FYI, I recently added the second channel, alarm_raw to test it out. There are only a very few occasions when this would get a value. I haven’t gotten it to report anything yet, but haven’t put much time into it. From Zwave Command Class Specification…
4.17.1.1 Error Handling
The device MUST stop if any safety issue is detected.
If the requested operation is overruled by a safety mechanism, the device MUST notify the requester via
a Notification Report (Notification Type: “Access Control”, Event: “Barrier unable to perform requested
operation due to safety requirements”). The Notification Report command is a member of the Notification
Command Class.