It appears the driver code displays the raw Parse, and is then followed by the decoded message. In other words the message is output via Debug, twice. THEN you get the Warn message wit hthe 3rd interpretation
161 in decimal is 0xA1 and zwaveAlarmStatus:255 is 0xff, etc.
It is probably one of the tamper/break in alarms the Schlage has which HE does not support or do anything with. There may not have been any code attempted, just maybe pounded on the door or lock a bunch.
Interesting, thanks! The noise did not go off so that is confusing. Very weird behavior. There's also no logs of a code even being entered, so I don't know what would cause this bad behavior.
Thanks for the suggestion! Unfortunately there's no lock code manager logs for this button clicking event. I guess the lock alarm mode blocked that from being sent
I dug into this a little more, the alarm command class is deprecated so this can be translated into a notification event using the zwaveAlarmType Event and Status
Type 0x06 is access control and event 0x10 (16) is Keypad Temporarily Disabled