Just because being an engineer can at times give us fat heads, I published the driver you posted to my ST account, fired up my hub, and my sniffer and attempted to join the device, the join never completed as far as the keypad was concerned, nor did ST ever present a default device, or any device for that matter.
It received its 16 bit address, and the transport key but never completed the IAS cluster sequence...
So I don't know how this keypad can work perfectly on ST since I was unable to even get it joined, much less test the functionality of the reference driver that was posted.
Unfortunately I've removed everything I can from ST and reset the hub (put it up for sale). Didn't mean any offense by posting the link, just wondered if doing things the way they specified allowed the device to join and work properly.
I'm curious why no manufacturer has tried to make a readily available and compatible zigbee or z-wave keypad as I think they would sell quite well on the various smart home systems.
Ive got the lame firmware v2 version working without leaving the lights on when armed from the keypad when an exit delay is set, however to do this it uses a non accelerating beep cycle, there is no getting around this.
I'm also going to split these drivers up, the three different models I have work differently enough that trying to jack them all into one is not doing anything for my attitude...
Or the Ring Alarm keypad? It's zwave. I have one brand new. @mike.maxwell if I ship the Ring keypad to you, could you get a driver? Then ship back the keypad? Actually I have the motion and the repeater, never used them.