This is also v1.0.1 release for the Virtual Basic Keypad. Instructions in post 1 have been updated to reflect this change. Clearly I understand the lag time implications in that single press scenes would experience (ie a half a second plus processing/communication time of RA2 and Hubitat). if you currently use the iFrame child device, you will need to update the url in the main Keypad device configuration, and update any dashboard you include the iFrame on to point at your main keypad device. This new version brings the iFrame setting into the main Keypad Device. This will automatically remove all child devices not set in the app after saving. You will want to open the app for each keypad after updating and configure it for your use case. allEventHandler .Event48d0c864 name: securityKeypad value: armed away data: null allEventHandler .Event1173747c name: securityKeypad value: disarmed data: null. This new version adds the ability to select which button children get created for your keypad device. After the Keypad Child is saved, it will automatically create the Keypad. They work fine however if I push the buttons in the keypads, the virtual buttons do not reflect the current state. Codes are managed directly in the Keypad Device, or by using Lock Code Manager. Good day everyone, I have created tons of virtual buttons which control lights in my Lutron RadioRA 2. There are now 2 options for the Virtual Keypad. The Child app has basic settings for how you want this Virtual Keypad to operate. Virtual Keypad Create Virtual Keypads to help manage HSM and Mode changes from any dashboard. This will need to be updated if you use this option after updating. Add the custom app 'Virtual Keypad Manager', and create a new Keypad Child. We no longer need the iFrame child device, or iFrame child driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |