This is also v1.0.1 release for the Virtual Basic Keypad. Instructions in post 1 have been updated to reflect this change. 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 can add a Virtual Device of Type Virtual Contact Sensor using Hubitats built-in drivers. You will want to open the app for each keypad after updating and configure it for your use case. keypad comes back to life and everything works fine. This new version adds the ability to select which button children get created for your keypad device. This will need to be updated if you use this option after updating. We no longer need the iFrame child device, or iFrame child driver.

Moved the iFrame preference setting into the main Keypad device.(you will want to open the app, and configure each keypad again after this update) Added ability to choose which HSM/Mode/Custom buttons get child devices created, and will remove child devices that are no longer specified in the app.