![]() In the app you can configure the chime option before saving. Seconds between chime triggers are configurable in the appĪfter the update, you should go into the keypad child app, and save it. Added optional child Chime device, which is a switch trigger (turns on) for a RM/etc rule to send chime/sound/tone/beep/etc to your chosen speakers.Added option to cancel count down timer by entering an approved code and pressing any command button (not number, clear, or panic buttons) to cancel the timer. ![]() Pincodelength required (NUMBER) - Maximum pin code lentgh for this lock Name optional (STRING) - Name for this lock code Pincode required (STRING) - Numeric PIN code Link: Driver Capability List - Hubitat Documentation LockCodesĬodeChanged - ENUM Ĭodeposition required (NUMBER) - Code position number to deleteĬodeposition required (NUMBER) - Code position number here is the hubitat documentation for the Lock Codes capability, which shows how it looks on my end, and how it was implemented in the driver: what HE version are you on? im still running 2.2.3.148, so I cannot comment on 2.2.4.xx yet as far as if something changed with the built in Lock Codes capabilityĮdit2. (at least this could be used until the root issue is resolved).Įdit. ![]() I wonder if trying to use the Lock Code Manager app to set/manage the pins would work as that should format the data correctly for the function to handle. the "virtual keypad" (with the app to manage settings) or the "virtual basic keypad"? was this installed from HPM or installed manually? Which version of the virtual keypad are you using. The function that sets the code needs those parameters in a specific order (code position, pin code, name), like seen in my screenshot, which would be reasonable that you are getting the error because its expecting an integer and its getting a string. the input fields are in a different order in your screenshot compared to my install: They can allow you to add pretty much any functionality that can be triggered by a switch to the keypad, including alexa/google home routines by exposing the custom child switch to those services. Let me know if you need any more help getting the custom commands setup. Using Rule Machine, you can use the Custom-GarageDoor child device switch as a trigger (when switch turns on) to run a rule to open/close your garage door. When it executes after a successful code entry it will turn its switch value on, then off (momentary on switch). This app/driver is definitely not the easiest to setup, so I know it can seem frustrating to get it to do what you want if you have little experience with the rest of Hubitat, but its easy to learn with enough motivation and help from the community.įor other commands you want to have keycode protected, use the app to create custom commands.Īfter saving the app, it will create a new child device for your keypad: Custom-GarageDoorīy default, this button will require code input before pressing like the hsm commands. The Virtual Motion Sensor driver can automatically reset the device back to inactive, so it would be effectively momentary (like a momentary switch or button.but a bit of an awkward way to get there).Welcome to the community, I'm sure this will all make more sense after you have played with it for a bit. ![]() So, I'm surprised that you see the button device at all (are you sure it's the Hubitat one? does anyone know if something changed recently?), but this would be my workaround if this is all still true: you'd need a virtual motion or contact sensor, then something that calls open() or active() or whatever (custom command you could do from a rule, for example) on your virtual sensor, which you could set to "trigger" the Alexa routine when it becomes open or active. (You could make it effectively momentary by using the "auto off" option on the virtual switch.) But, last I knew, Alexa also couldn't trigger automations from switches, only sensors. Unless something changed recently, buttons aren't supported from Hubitat to Alexa-you'd need to make it something like a virtual switch, as Alexa can see switch devices.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |