I have a simple app I used in ST allowing the keypad to be used for various automation functions based on the pin code. Since I'm unable to view the source for the HE Keypad DTH I need some assistance with these two questions:
Will these subscribes function with the HE keypad DTH
subscribe (thekeypad, "codeEntered", pinHandler)
subscribe (thekeypad, "armMode", armModeHandler)
When an undefined pin is entered, and assuming "codeEntered" is a valid subscribe, will it receive the invalid pin entries?
If armMode is a valid subscribe, will a valid evt.value be "exitDelay"
Setup a simple app to monitor all events on a simulated keypad device, and "securityKeypad" events, All events works, did not receive "securityKeypad" events when tapping/clicking the buttons in the device display
Doing this does not get you a functioning "simulated" device. The driver is only going to process commands coming from a real keypad. It's parse method is looking for Zigbee messages, which you cannot send it. So you don't know what events it would send.
Drivers for virtual devices all have names like Virtual Dimmer...
I'm aware the virtual device is non functional. What I don't understand is why my app is posted with securityKeypad when tapping on a device status such as Disarmed from
subscribe (thekeypad, allEventHandler)
I have most devices moved to HE, except for keypads, repeater and siren that are waiting for the forthcoming update with Entry Delay/ Exit Delay support. Using hybrid system with ST and HE, Hublink, and Other Hub app. When that update is released, one keypad (Iris V2) moves to HE for evaluation.
Not sure what is meant by "app status page", but maybe it's this?