Hubitat virtual keypad11/9/2023 The debug file has a better change of containing information that may be useful to help isolate issues. There is no user options to add or remove controls. The HS device properties are based upon the hubitat capability being modeled. I believe the plugin will create a new HS device for any capabiltiy reported by hubitat when a sync or restart is done. Going to device settings I can press home away disarm and the keypad gets the event. When you delete the HS device then you have broken the relationship between hubitat and HS. It does not need to match the name in hubitat. If you change the name you do not change the ID so from the plugin's perspective there has been no change made. I use Virtual Keypad on an old 7 Amazon tablet as my main. The ID is what identifies a hubitat device to HS. Im thinking about using a centralite keypad to lock/unlock a door without a built in keypad. And, the keypad can't change mode, only HSM state. HSM can respond to mode, but mode can't respond to HSM. Seems like when I have a keypad, and HSM driving that keypad, that the state/mode change is backwards. Otherwise I need to figure out how to at least recognize the device without a driver. When HSM goes from armed to disarmed then mode manager uses the time settings to pick the mode. I have 2 more, Ill try the others to see if its the same. The device did say it was the US version, dont believe that to be the issue. Switches still function underneath the keypad if I ever need to turn the power off. Not sure of the next step, off to the custom device drivers community. With use of virtual switches I am able to control the devices in Hubitat. What are you expecting HS to have to model the Virtual Button of Hubitat? I go into z-wave inclusion Hubitat doesnt respond. The hubitat capability being modeled is Virtual Button. It creates a selector for the user to enter 1 to 5 and when a value is selected then it sends the command push/value to Hubitat. When I use the JSON posted I see one Device created in HS We will get it sorted out.I forgot to respond to this thread earlier. Not at the moment, but later this morning, I will be able to be by my test setup with these keypads, and I could reproduce the steps you take, and see (hopefully) the same things you are seeing. And again, please let me know of anything not right as you progress. The HSM UI page will need to be refreshed to see it's most recent state after any step you take. Again, have both HSM UI and keypad device page open in tabs, and check them as you go. These Picos are not programmed in Ra2 to the device in question, but are general use Picos only controlling Hubitat automations. The no mode version of this simply ties a Pico button and a Keypad button together with Alexa for toggle use. I'd start with no pin required for arming, with code required for disarm. There is also an Alexa virtual device created, and the app keeps all of the state information straight. The next phase would be to move to arm/disarm from the keypad. The Virtual Basic Keypad operates more similar to a hardware keypad, and only. The full version which is explained in this first post, and a Virtual Basic Keypad which is outlined in post 2. image There are now 2 options for the Virtual Keypad. If you encounter anything not right in those first two steps, please let me know. Virtual Keypad Create Virtual Keypads to help manage HSM and Mode changes from any dashboard. Next, pull up the device page for the keypad in a separate tab, and see if it is doing the right thing when armed/disarmed from the HSM UI. First, see if HSM is responding correctly for arming and disarming from its user interface. My suggestion is to walk through this like a troubleshooter. Keypad device handler for models: Centralite/Xfinity 3400, Centralite 3400-G, Iris V2, Iris V3, and UEI. As I worked on it, I did discover a couple of minor issues in the Centralite driver. There are some fixes and upgrades for HSM and the Centralite Keypad coming in the next release (the stuff I've been working on). I must say, they are a hot mess of a device. I've been messing with these keypads and HSM for the past few days (author of HSM).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |