# Popp keypad not working with v2.0.10

**URL:** <https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927>\
**Category:** Apps\
**Created:** [September 9, 2019, 3:22pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927 "2019-09-09T15:22:45Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![hluhr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hluhr/32/15371_2.png) [@hluhr](https://community.homey.app/u/hluhr)\
**Post date:** [September 9, 2019, 3:22pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/1 "2019-09-09T15:22:45Z")

</div>

I just received my Popp keypad and added it into Homey with help of the v2.0.10 popp app.  
That part went very smothly…

Then, after adding a pincode for user 1, I wanted to test a flow.  
I created a very simple flow:  
When: “A user verified itself”  
Then: Mobile: Send User verified to User

Adding the correct pincode give my green light in the actual Popp keypad but the flow is not triggered. Do anyone know what problem can be?

---

<div class="post-metadata">

**Author:** ![SamB](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/samb/32/16535_2.png) [@SamB](https://community.homey.app/u/SamB)\
**Post date:** [November 7, 2019, 2:23pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/2 "2019-11-07T14:23:48Z")

</div>

I’m finding the same thing. Did you get this resolved?

---

<div class="post-metadata">

**Author:** ![SamB](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/samb/32/16535_2.png) [@SamB](https://community.homey.app/u/SamB)\
**Post date:** [November 7, 2019, 2:34pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/3 "2019-11-07T14:34:42Z")

</div>

Actually I just resolved this. Turns out the little magnet inside the back cover had moved and was preventing the tamper alarm from being deactivated.

 ![IMG_0182](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/0/20667b5d7f32d02d2ff9e4b60086c5846bc3e330.jpeg)

---

<div class="post-metadata">

**Author:** ![Tangodelta](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tangodelta/32/9471_2.png) [@Tangodelta](https://community.homey.app/u/Tangodelta)\
**Post date:** [November 7, 2019, 3:44pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/4 "2019-11-07T15:44:39Z")

</div>

Have had the same problem for months, also before upgrading, the magnet is in place, still the tamper alarm does not deactivate. Therefore I tried with the tamper alarm on in the card “and”, but flow still does not trigger.

---

<div class="post-metadata">

**Author:** ![hluhr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hluhr/32/15371_2.png) [@hluhr](https://community.homey.app/u/hluhr)\
**Post date:** [November 7, 2019, 5:01pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/5 "2019-11-07T17:01:29Z")

</div>

The solution for me was to upgrade to the beta version (now stable 2.0.12) at that time. After that both the tamper alarm went away and the flows started to work.

However, sometimes (not often) the keypad is not properly functional. When entering the correct code, it does not disarm the alarm. I have done a lot of trouble shooting and these are propably some of the reasons:

1. Z-wave NW problem (Solution: Move keypad closer to Homey + adding Z-wave range extender)
2. Memory problem in Homey (Solution: Restart Homey a couple of times each week)
3. Keypad firmware version (No solution yet)  
See: [Popp keypad firmware version](https://community.homey.app/t/popp-keypad-firmware-version/20246)

Regarding issue 3 above I have contacted Aeotec support and they told me that the only firmware version out there should be 1.0.8.  
However, my Popp keypad has firmware version 263, which is 107 in hex. So, I’m trying to sort out with Aeotec helpdesk how to upgrade to 1.0.8 which should be 264 in decimal.  
Which firmware version have you on your Popp keypad?

---

<div class="post-metadata">

**Author:** ![Tangodelta](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tangodelta/32/9471_2.png) [@Tangodelta](https://community.homey.app/u/Tangodelta)\
**Post date:** [November 7, 2019, 5:04pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/6 "2019-11-07T17:04:04Z")

</div>

Well, #Mapulu did mention core as the probably source of problems. My firmware is 264, 1.0.8. My Homey popp app version is 2.1.0.

---

<div class="post-metadata">

**Author:** ![hluhr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hluhr/32/15371_2.png) [@hluhr](https://community.homey.app/u/hluhr)\
**Post date:** [November 7, 2019, 6:02pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/7 "2019-11-07T18:02:27Z")

</div>

The Popp app version 2.1.0 is the beta version. Isn’t it better if you try the stable version (2.0.12) ?  
It works fine for me, despite the intermittent problem.

---

<div class="post-metadata">

**Author:** ![Tangodelta](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tangodelta/32/9471_2.png) [@Tangodelta](https://community.homey.app/u/Tangodelta)\
**Post date:** [November 7, 2019, 7:33pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/8 "2019-11-07T19:33:03Z")

</div>

Every version has been tried, same results! Works sometimes 🙂

---

<div class="post-metadata">

**Author:** ![hluhr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hluhr/32/15371_2.png) [@hluhr](https://community.homey.app/u/hluhr)\
**Post date:** [November 7, 2019, 7:45pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/9 "2019-11-07T19:45:08Z")

</div>

What do you mean that it works sometimes?  
Do you mean that the tamper alarm only deativates sometimes?

---

<div class="post-metadata">

**Author:** ![Hiato](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hiato/32/14189_2.png) [@Hiato](https://community.homey.app/u/Hiato)\
**Post date:** [September 29, 2020, 7:10pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/10 "2020-09-29T19:10:11Z")

</div>

Sorry to wake up an old feed… Is the keypad working well now without any issues?

---

<div class="post-metadata">

**Author:** ![hluhr](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/hluhr/32/15371_2.png) [@hluhr](https://community.homey.app/u/hluhr)\
**Post date:** [September 29, 2020, 7:33pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/11 "2020-09-29T19:33:31Z")

</div>

Yes it works perfectly. The solution was to move Homey closer to the keypad since the Z-wave signals was not strong enough.

---

<div class="post-metadata">

**Author:** ![cschipper](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cschipper/32/9561_2.png) [@cschipper](https://community.homey.app/u/cschipper)\
**Post date:** [May 28, 2025, 2:58pm UTC](https://community.homey.app/t/popp-keypad-not-working-with-v2-0-10/17927/12 "2025-05-28T14:58:27Z")

</div>

Waking up this topic a bit.

How is the keypad currently working. Still working flawless with Homey Pro?

Would my usecase work:  
2 kids with a (own) code and triggering a flow (to open a garage door)?
