How ever many HSM or Mode command buttons you want ie button 5 should have "button number" 5 set, etc.ġ (InputDisplay) set to use attribute: InputDisplayġ (Clear) button, I set this to use the refresh iconġ (Panic) Button, I set this to 'he-siren_and_alarm' icon You can manually build each keypad dashboard, or use the below template json and css as a baseline to get setup quickly.įor manually creating the dashboard, you will want to add the following Keypad child devices to the dashboard:ġ0 "number" buttons, with the "button number" set to the value of that button. Creating the Keypad DashboardĬreate a new dashboard for each custom Virtual Keypad. They all have a switch capability that will turn on (and auto off) when any of the command buttons are used. The command buttons (HSM and Mode) all operate as a push button when used on a dashboard, but they also act as a trigger for custom external functions. #VIRTUAL KEYPAD CODE#Codes are managed directly in the Keypad Device, or by using Lock Code Manager.Īfter the Keypad Child is saved, it will automatically create the Keypad device and all child devices. The Child app has basic settings for how you want this Virtual Keypad to operate. #VIRTUAL KEYPAD DRIVERS#Manual installation by grabbing the above listed files from my github here (install all apps and drivers with title Virtual Keypad): Īdd the custom app "Virtual Keypad Manager", and create a new Keypad Child. Set how many failed attempts between notifications Installation:Īvailable in HPM (Hubitat Package Manager) Set device(s) you want to be notified on if bad code entries are used When enabled, any disarm commands (mode name has disarm in it,hsm disarm, or custom-disarm) are issued, it will also run HSM cancelAlerts ie: before Away is set, switch to Disarmed then wait for the delay to execute Away mode.Ĭhange HSM directly or just issue the switch trigger so RM or another automation can manage your HSM state Set a default mode that will be switched to first, before executing specific other modes. ie: 30 second delay before executing Mode-Away after successful code authorizationĮxclude commands from requiring a code: ie: HSM-Arm doesnt need a code entered before it will executeĬhange modes directly, or just issue the switch trigger so RM or another automation can manage your modes Options:ĭelay: Set a time delay for specific commands. Each keypad can have its own codes and command button options which control who can access and what Modes or HSM options they can change.Īdd Virtual Keypads dashboards to any/multiple existing dashboards using an included iFrame function built into the main Keypad Device. Use the App/child app to create however many custom keypads you need. #VIRTUAL KEYPAD FULL VERSION#If you want the Virtual Keypad to control Modes, HSM, and custom triggers, use the full version outlined in this 1st post below: Components:Īpps: Virtual Keypad Manager and Virtual Keypad Childĭrivers: Virtual Keypad, Virtual Keypad Button Child, Virtual Keypad Input Display Child Use: Since this doesnt have children devices, the Virtual Basic Keypad does not offer triggers for RM or other apps. There are limited options, but this only uses 1 device and no children devices. The Virtual Basic Keypad operates more similar to a hardware keypad, and only interacts with HSM. This results in a single device with no child devices that only works with HSM commands, and has no external trigger options. #VIRTUAL KEYPAD DRIVER#The Virtual Basic Keypad is a limited version which has a single driver component. Skip this post if you are using the main Virtual Keypad app/driverĪvailable via Hubitat Package Manager and through my github drivers section linked in the first post for manual install.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |