Hi, new to Hubitat. Roughly once a day (I notice at night when going to turn the alarm on), the keypad will not respond. Hitting partial will result in a sad/failed tone and the mode won’t change. Usually after one or two tries punching my pin and hitting off I will get the usual happy/success tones, then I can arm it as usual.
Using HSM with nyckelharpa, native lock code manager, and Centralitex keypad driver.
Any thoughts?
First thought is the keypad is having trouble communicating with the zigbee mesh.
Do you have zigbee repeater devices (pretty much all plugged-in zigbee devices)?
I have 3 Iris V1 outlet switches.
Maybe fresh batteries. I've had keypads act weird with a very small voltage drop.
Thanks, batteries brand new a week ago (and has been happening since i put the system together at that time). I guess stranger things have happened so might try swapping them out.
Open to other ideas!
If this means the batteries need changing every couple of weeks or less, then that points to either a weak zigbee signal at the device, or perhaps an incomplete device pairing that sometimes shows itself by the network icon being constantly illuminated. Are all the keypad lights off when the device is idle?
If possible, move the keypad close to the hub for a few days and see what happens.
My working Iris V3 keypad shows "Iris V3 Keypad battery was 64% 5.5 volts". It will probably need a battery refresh soon. It's been a while since they were changed. What your device showing?
Battery reading 100% (not sure where to find voltage, I'm getting battery % from the device page). The lights only come on when I am near (motion) or pressing buttons; I will keep an eye out for the network light lighting up. It is about 15 feet from the hub.
Ahh found a battery reading. Front Door Keypad battery was 93% 5.9 volts
Also, it seems relevant that I can get it to respond again by plugging in a PIN and hitting off (even though the system is disarmed). And then it will arm fine.
When the quirky V3 keypad's arming status is out of sync with the HSM arming status, the keypad acts as you describe, it's part of the device's firmware. So when the V3 shows armed, it only accepts disarm requests, and vice versa. The Iris V2 and Centralite keypads don't do this.
It's either not getting the arming status messages--network, or not reacting to all them-firmware.
Try moving the keypad close to the hub, unplug the V1 repeaters, arm and disarm the system a few times. If it works, it just may be those V1 repeaters, although they are supposed to work with HE. If it's a firmware issue 
[Update] There is also a possibility it's the software, or a combination of software and firmware.
Also please confirm you are using the latest versions of the Nyckelharpa app and Keypad driver
Appreciate your help on this. Sorry I haven't had too much time to devote to it this week. And I really only get one shot at it per day - once I get it back responsive again, it seems to work as expected for a while. This week it worked as expected one night, and the other days took punching in the off codes a few times to get it back "synced" up.
I am using Nyckelharpa 1.2.1 and Centralitex 1.0.5
I tried tonight unplugging the V1 repeater/switches and moving the keypad close to the hub; this was while it was out of sync; it didn't get back in sync, until I punched the off codes, then worked as expected.
For better or worse (I guess worse while I am trying to test it) once it gets back in sync it seems to work as expected for a while, perhaps 24 hours.
Any other debugging ideas?
When the keypad is out of sync with HSM, moving the keypad closer to the hub does not reset the keypad's arming status. That requires an arming or disarming request from the keypad, or perhaps some other method.
When successfully arming/disarming exclusively 100% from the Iris V3 keypad, does it remain synchronized with HSM?
When the keypad gets out of sync, how is the HSM app being armed/disarmed, or does the keypad change on it's own?
Please list all methods you use to arm and disarm HSM, and how they impact the keypad's synchronization.
Literally only using the keypad to arm/disarm. Right now trying to keep the system very simple until I get the bugs worked out. Arm (partial for "home" mode) every evening on the keypad, disarm every morning on the keypad. Disarming in the morning on the keypad works 100% of the time. Attempting to arm via "partial" on the keypad at night results in me discovering it is out of sync 80% of the time.
That is very strange.
Are there any errors in the log?
Does your system have a exit/arming delay coded for Night mode, assuming Partial sets Night mode. If so, what is the delay?
When you discover the out of sync is it immediately after arming? If it occurs after a period of time it likely means the keypad has fallen off the zigbee network (or maybe temporarily lost power), then reconnected. Falling off when the system is disarmed, likely would not hurt anything since it reconnects as disarmed. Please check the device's Events for any strangeness.
One other question that may seem really odd. Is the keypad mounted on a wall, or sitting on the bottom edge, vertically on a surface? If on a surface it may act weird or burn out batteries due motion sensors being constantly active, lay it flat on its back.
Forgive me I misinterpreted this statement in my prior post. Does this mean when you attempt to arm, HSM is disarmed and the keypad is already armed?
When disarming in the morning does the Partial key shut off, then the Off key light? Is HSM truly disarmed?
Does the keypad follow when HSM is armed/disarmed by a method other than the keypad?
Quick update. After your last suggestions of unplugging the repeaters (outlet switches), 4 nights ago, and ultimately plugging them back in - I have had normal arming behavior. However, your questions made me investigate further, and it seems the keypad is not following HSM, and maybe this is the problem.
I am not sure about this, but will double check. If the keypad is armed, partial should be lit? I don't believe this was the case, but haven't been able to replicate as it has been working better.
I believe so - HSM is definitely disarmed, confirmed when checking the app (or opening the door). I believe the off key lights, and HSM shows as disarmed.
It seems the keypad isn't following correctly. I normally don't disarm via the app/dashboard, however when testing this this evening, the keypad does not seem to follow correctly. Specifically: if HSM armed, and I disarm via app, the keypad still lights partial, and hitting partial again results in the "sad trombone" failed tone that I had been getting. (I can type a PIN, hit off, and it will disarm on the keypad and be synced up, which seems like the behavior that had been occurring before, albeit spontaneously) Meanwhile, changing the status via the keypad seems to change HSM status on the dashboard correctly.
Light the keys by waving your hand over the motion sensors at the bottom of the keypad.
I continue believing the out of sync conditions are a Zigbee network issue. Hope you can figure out the problem.
Got it, thank you. Will keep working on it. Out of curiosity, do you think if I got ahold of an Iris V2 keypad, these issues would go away?
If I remember correctly the Iris V2 firmware does not care about the current arming state, it sends whatever is entered by the user. So...it will likely "make these issues go away", but no guarantees. It's a workaround, does not fix why it's happening, and it may recur.
Download the Hubitat app
