I don't know what I did, if anything. But now the proximity seems to be off. Maybe it just takes awhile........
1 Like
This keypad is starting to get on my nerves.
In my mode app I send commands to the keypad, arm Home, Disarm, etc. When testing it works fine. The keypad lights up and tells me what state it is in. Then it sits for several hours.
When the next time my mode changes the keypad doesn't respond. But I look at the events and logs and it says it did. But the keypad itself says otherwise.
Hmmm... 
Coincidentally, shortly after I got the community driver working.
I am still curious as to what that actually means. Did they just update their driver with the same stuff you did or did they fix the Indicator command class. or anything else.
I would guess a similar fix as to what I did.
None of the command classes have been touched since release except maybe one or two quick fixes right out of the gate.
If the indicator class was fixed, then it should get rid of the error using this custom driver as well.
I took my Ring G2 Keypad and smashed it with a sledgehammer after months of torture. It was absolutely the right decision. I replaced it with a wall mounted tablet that works flawlessly as a keypad and so much more.
Seems to work both ways again now... Thanks for the work!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.