I don't use lock code manager and my keypads and lock are working as expected.
I have the beep tone for arm/disarm etc.
I understand @mike.maxwell knows about it. Hopefully it will make the next release of Hubitat. I am happy with @arnb and his code.
Are you able to add codes and arm disarm the keypad from the driver page?, if not then you have a communication issue between the hub and the keypad.
I can use the device page to arm and disarm, send beeps, but nothing with codes. I hit the GetCodes button, and the SetCode button, and neither seem to do anything.
This is with BOTH the native Centralite driver as well as with CentraliteX driver provided by Arnie.
The Lock Code Manager app doesn't do anything, either. Arnie's Nyckelharpa User app works great.
I have a different problem with the 3400 keypad. Arming works fine when all doors/windows are closed. But when one of them is open when arming, then HSM notifies me by text and sound and does not arm the system, BUT my keypad still remains in armed mode, thinking the alarm is activated.
Anyone else experiencing the same thing? Any solutions?
I can confirm this issue. I noticed it while testing the Beta version of my Nyckelharpa app..
The Beta version resolves the issue you reported, and also allows
- using the Hubitat System keypad drivers
- using Lock Code Manager Pins
- Forced arming with the system keypad driver or Centralitex keypad driver
- and more
2 Likes
Thnx for replying and sorry for my late respons (I haven't been able to put any time into my hubitat setup lately 
).
Anyway, I want to update to your latest beta version, to check if my issue with the keypad is resolved. What's the easiest way to do that? Just update the Nyckelharpa app-code and driver-code? Or do I have to uninstall everything and reinstall from scratch?
For the life of me, I can't seem to get Rule Machine to recognize the code entries on this thing. Logs show arm/disarm and code name, but rule machine does nothing. Been toying for months on this. Seems there's no custom attribute that really helps. Lastcode isn't what I need, and the "lock code" trigger in RM doesn't work. What are y'all using? Might need a different driver.
Hi all. I picked up 3400-G keypad a while back, although it's been sitting in my todo-box. Here's the idea I'm contemplating, now that I've moved to HE and added it with the default Centralite Keypad driver. Would love some thoughts as to if the following is possible
-
2 different codes configured, one for the poolguy to open the sidegate (maglock in place already) and one to open the garage (switch already in place). It goes without saying that the keypad would be mounted in a weatherproof enclosure.
-
I understand the keypad is basically a toggle between disarmed and 3 different arming states. I don't really have a need for those for this application, thus I'm wondering if it's possible to automatically re-arm the keypad after a period of time? It looks like there's a command for arming each of the states.
-
Hoping to trigger a piston in Webcore by the disarming event in Webcore and being able to read by which code/user it was disarmed. Then do something (like triggering the maglock on the gate), and then re-arming the keypad a few seconds thereafter.
Any thoughts on this? Thanks!
Where do y'all "pick these up"? As far as Google tells me, these aren't available for purchase anywhere on the globe...and neither is the Iris keypads that are supported by Hubitat. Amazon.com currently has one (and only one) Centralite 3400-X, but that one isn't listed as supported in the Hubitat docs (SecurityKeypads - Hubitat Documentation).
Any ideas?
Could you use an alternative keypad like the Ring Keypad 2nd Gen?
It is in the list of compatible devices..
https://docs.hubitat.com/index.php?title=List_of_Compatible_Devices
Oh! I guess the documentation page I linked is outdated. Thanks for the tip! However, the Ring keypad requires C7, which I don't have. My C5 works great and it seems wasteful to toss it just because I need a keypad...
At least it seems like the Centralite 3400-X is also supported, which is good because it seems to be possible to get a used one of those at least.
Of course what you really need to do is go to a multi-hub configuration!
C-5 for Zigbee and maybe network stuff..
C-7 for Z-Wave.
(I have 3 hubs - a C-7 for Z-Wave, a C-5 for network/cloud apps and a C-5 for Zigbee devices)
Of course you could also do it by location and spread out the area of effect of your setup + reduce overhead!
Soo many excellent ways to spend far too much money and time!
Hmm... interesting...what's the purpose of that? Can you still do automations with rule machine that involves both ZigBee and z wave devices in the same rule?
Short story is my original C-4s I had in place by location were experiencing issues like memory leaks and one straight up died on me. I had some C-5's on hand. When I made the change the C-7's had just come out so decided to use that exclusively for Z-Wave since my understanding was the zigbee radio was the same as in the C-5. The extra C-5 for network / cloud stuff was just on a whim - I had one in hand so decided to incorporate it. I really like the idea of isolating the cloud stuff from my main system though.
To share the devices between hubs I use HE's HubMesh system. Works great.
I also use Node-RED for all my rules and "apps" in order to keep the hubs as lean as possible. Node-RED connects to all my hubs so most of my sharing via HubMesh is for the network/cloud hub - like making devices available for the Alexa Skill, Flume Water monitor etc..
1 Like
Soo...could anyone provide some bright ideas on why they commands and preferences are not working? My Centralite 3400 requires pin to arm even though I set the preferences to not require pin to arm.
Also, the configuration of "Set code length" doesn't seem to work. The command is sent, but the logs show that the original value is set again shortly after sending the command to change it.
AFAIK the 3400 hardware always requires a 4 digit pin
for arming: tap key home, away, or night night then enter 4 digit pin
for disam: enter pin
Iris V2 and Iris V3 may be set to arm without a pin
1 Like
Oh, ok! And then they just use the same driver, so that's why there are settings for things that aren't really supported on my model? Thanks for the insight! Do you know if there's any way for me to disable settings/commands that aren't supported? Can I find the driver code for built-in drivers somewhere?
Thanks!
The HE drivers are proprietary, although the IRIS V3 logic is on their Github account. The Nyckelharpa Centralite driver sets model number. If the model number is wrong it may malfunction. The Centralite driver must be used with Nyckelharpa, does not work directly with HE/HSM
On device page using the Centralite driver scroll down to DATA, Model should be 3400. If not enter 3400 into Commands model field, then tap/press the Model command, refresh the page.
1 Like
