# \[APP\]\[Pro\] Dashboard Alarm Keypad – a code-protected keypad for any alarm

**URL:** <https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154>\
**Category:** Apps\
**Created:** [October 21, 2026, 7:44pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154 "2026-10-21T19:44:54Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [October 21, 2026, 7:44pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/1 "2026-10-21T19:44:54Z")

</div>

Hi all,

I’d like to share a new app: **Dashboard Alarm Keypad**. It puts a proper alarm keypad on your Homey dashboard: one tap to arm, a code to disarm. It works with **any alarm system** you can control from a flow.

**Why I built it:** our alarm is an Aqara M3 hub, controlled through Apple Home. When we go away, our cat sitter looks after Monté (our cat). She needed a way to switch the alarm off from the wall-mounted iPad dashboard. A plain on/off button wasn’t safe, because anyone standing at the iPad could press it. I wanted a real keypad with a code, and I couldn’t find one, so I built it.

 ![IMG_1134](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/1/312f56e68f1a19bfd5326137421f55b3cc31e70a.jpeg)

* * *

## What it does

- **Arm** with one tap, no code needed, so you can arm it on your way out.
- **Disarm** with a 4–8 digit code. Everyone gets their **own code** (e.g. family, cleaner, cat sitter), and the flow tells you **who** disarmed it.
- **Live status ring** around a photo of your choice: Disarmed, Home, Night, Arming…, Armed or Alarm!
- When the alarm is going off, **Disarm turns into a red “Stop alarm” button**.
- **Lockout** after too many wrong codes, with flow triggers so you can get a notification.
- Codes are stored **hashed** , never in plain text, and are checked on Homey, not on the tablet.
- Light and dark mode. English, Dutch, German, French, Spanish, Italian, Danish, Norwegian and Swedish.

## Flow cards

| **Type** | **Card** |
| --- | --- |
| Trigger | **Arm was pressed** |
| Trigger | **Correct code entered to disarm** (tag: _User_) |
| Trigger | **Correct code entered by…** (pick a person from your saved codes, from v1.2.0) |
| Trigger | **A wrong code was entered** (tag: _Attempts left_) |
| Trigger | **Keypad locked after too many wrong codes** (tag: _Locked for (seconds)_) |
| Action | **Set keypad status to** Disarmed / Home / Night / Arming / Armed (away) / Alarm going off |
| Condition | **Keypad status is / is not** … |

The idea is simple:

1. **Keypad → alarm:** use the triggers to arm and disarm your alarm.
2. **Alarm → keypad:** use _Set keypad status_ so the widget always shows what your alarm is really doing, including changes made somewhere else (geofencing, another app, a siren going off).

When the status is set to **Arming** , the keypad switches itself to **Armed** after the exit delay set in the app settings, so you don’t need a delay card for that.

## Setup

1. Install the app and open its **settings** :
  - Add a code for each person.
  - Optional: upload a photo for the widget (it’s cropped automatically).
  - Set the **exit delay** to match your alarm, and choose whether the status after disarming is _Disarmed_ or _Home_.

2. Add the **Alarm Keypad** widget to a dashboard.
3. Build the flows for your alarm (see the Aqara example below, and the notes for other systems after that).

* * *

## Example: Aqara M3 hub (alarm in the Aqara / Apple Home ecosystem)

The Aqara alert system can’t be controlled from Homey directly: it isn’t exposed over Matter. But the M3 has a feature called **Advanced Matter Bridging** that solves this in both directions:

- **Scenes** you create in the Aqara app appear in Homey as **plugs**. Turning the plug on runs the scene.
- **Signals** (conditions you define in the Aqara app) appear in Homey as **occupancy sensors**.

So: scenes let Homey **control** the alarm, and Signals let Homey **see** what the alarm is doing.

### **Step 1: Delays in the Aqara app**

Alert system → **Away mode** :

- **Entry delay:** 60 seconds, time to get from the door to the dashboard and enter your code. The hub beeps during the countdown.
- **Arming (exit) delay:** 30 seconds, time to get out of the door.

Leave Home and Night mode without delays.

### **Step 2: Scenes, so Homey can control the alarm**

Create these scenes in the Aqara app (Scenes → +), with the action **Alert system** :

| **Scene** | **Actions** |
| --- | --- |
| **Alarm Away** | Arm automatically → **Away** |
| **Alarm Arrive** | Disarm automatically → **Away** , delay **3 seconds** , Arm automatically → **Home** |
| **Alarm Silence** | **Turn off alarm** (stops the siren but keeps the current mode) |

Tip: avoid the “switch arming/disarming” (toggle) action. If Homey and the hub ever disagree about the state, a toggle does the opposite of what you meant.

Then share them with Homey: **Profile → Connect to Ecosystems → Matter → Scenes** , add all three, and choose the **M3** as the bridge (the one already paired to Homey). They appear in Homey as plugs. The plugs turn themselves off after running, so they behave like buttons.

Tip: you can edit a scene in the Aqara app at any time (e.g. change the delay), and Homey doesn’t need to know. But if you **delete** and re-create a scene, you get a new plug and have to update your flows.

### **Step 3: Signals, so the keypad knows the real alarm status**

**Profile → Connect to Ecosystems → Matter → Signals → +**

Under **If** , tap **Add → Alert system** , choose the **mode** (Home / Away / Night), then the **event** (_Arm_, _Disarm_ or _When the alarm sounds_). Create these five Signals:

| **Signal** | **If…** | **Notes** |
| --- | --- | --- |
| **Alarm Home** | Home mode → **Arm** | |
| **Alarm Away** | Away mode → **Arm** | |
| **Alarm Night** | Night mode → **Arm** | |
| **Alarm Disarmed** | Home → **Disarm** , Away → **Disarm** , Night → **Disarm** | Add all three with **Add** , then set **Any condition is met** |
| **Alarm Triggered** | Home → **Alarm sounds** , Away → **Alarm sounds** , Night → **Alarm sounds** | Same: three conditions, **Any** |

Make sure “ **Any** condition is met” is selected for the last two. With “All”, it would wait for all three, which can never happen.

The Signals appear in Homey as occupancy sensors. I put them all in their own “Alarm” zone to keep things tidy.

### **Step 4: The flows**

[Upload: docs/flow-keypad.png]

**Alarm keypad → controls alarm**

| **When** | **Then** |
| --- | --- |
| Arm was pressed | **Alarm Away** plug → Turn on |
| Correct code entered to disarm | **Alarm Silence** → Turn on, 1 second delay, **Alarm Arrive** → Turn on. Plus a push notification: “Alarm disarmed by [User]” |
| A wrong code was entered | Push notification: “Wrong code entered on the alarm keypad – [Attempts left] tries left” |
| Keypad locked after too many wrong codes | Push notification: “Alarm keypad locked for [Locked for (seconds)] seconds” |

Disarm runs **Silence** first and then **Arrive**. That way, one code entry stops a sounding siren in any mode _and_ takes the alarm out of Away. With Silence alone, the alarm stays in Away and the next movement sets it off again.

**Alarm status → keypad widget**

| **When (sensor: “The motion alarm turned on”)** | **Then** |
| --- | --- |
| Alarm Home | Set keypad status to **Home** |
| Alarm Away | Set keypad status to **Arming** (the app switches to _Armed_ after the exit delay) |
| Alarm Night | Set keypad status to **Night** |
| Alarm Disarmed | Set keypad status to **Disarmed** |
| Alarm Triggered | Set keypad status to **Alarm going off** |

In the app settings I set **Status after disarm** to **Home** , to match the _Alarm Arrive_ scene.

When you disarm with Alarm Arrive, you’ll briefly see _Disarmed_ and then _Home_. That’s just the scene’s two steps coming back through the Signals.

You can use the same scene plugs in your other flows too. For example, I use **Alarm Arrive** when someone’s phone arrives home, and **Alarm Away** when everyone has left.

* * *

## Using it with other alarm systems

The app doesn’t talk to any alarm itself. It’s purely a keypad with flow cards. If your alarm can be **controlled** from a flow and can **report** its state to a flow, it’ll work. The pattern is always the same:

**1. Keypad → alarm**

- **Arm was pressed** → your alarm’s “arm” action
- **Correct code entered to disarm** → your alarm’s “disarm” action

**2. Alarm → keypad**

- Your alarm’s “armed / disarmed / alarm triggered” triggers → **Set keypad status to …**

Some examples:

- **An alarm that shows up as a device in Homey** (via its own app, Z-Wave, Zigbee or Matter) with a security/alarm mode: use its _set mode_ action for arming and disarming, and its _mode changed_ / _alarm triggered_ triggers to set the keypad status.
- **A Homey-based security app** (e.g. a virtual alarm system built from your sensors): arm and disarm it with its action cards, and use its state triggers to set the keypad status.
- **An alarm only reachable through another ecosystem** (Apple Home, Google Home, SmartThings…): use virtual switches or Matter-bridged scenes, as in the Aqara example above. Homey flips a switch, and the other ecosystem’s automation arms or disarms the alarm.
- **No real alarm at all?** You can still use it as a code-protected button, e.g. to disable a “nobody home” mode, unlock a feature, or log who came home.

If your alarm can’t report its state, you can still use the keypad. Add _Set keypad status_ next to the arm and disarm actions in the same flows. The widget then shows what the keypad last did, rather than the alarm’s real state.

* * *

## Good to know

- This is a **keypad for an alarm you already have** , not a certified alarm system.
- Arming doesn’t need a code on purpose, as on most alarm panels. Disarming always does.
- The lockout applies to the whole app, so it covers every dashboard with the widget on it.
- Requires Homey Pro (dashboard widgets aren’t available on Homey Cloud).

**App Store:** [https://homey.app/a/com.simon.dashboardalarmkeypad](https://homey.app/a/com.simon.dashboardalarmkeypad)

Feedback and ideas very welcome, especially if you connect it to a different alarm system. Let me know how you wired it, and I’ll add it to this post!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [October 25, 2026, 3:43pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/2 "2026-10-25T15:43:23Z")

</div>

**Update: v1.1.0 🔒**

Hi all,

A quick one this time. I’d been out for the afternoon, got home, walked up to the iPad to disarm the alarm and… could I get the code in? Every time my finger slid even slightly between keys, the whole widget scrolled and the press went nowhere, all whilst the entry delay was counting down and the hub was beeping at me! Not ideal on an alarm keypad, and in all honesty something I should have spotted before the first release 🤦🏻‍♂️

So version 1.1.0 locks the keypad in place. The widget no longer scrolls inside itself, swiping on the keypad no longer scrolls the dashboard behind it, and a slightly sloppy tap still counts as a key press.

The one trade-off is you can’t scroll the dashboard by swiping on the keypad any more, so start your swipe somewhere else on the screen. For an alarm keypad I think that’s the right call?

Nothing else has changed, your codes, photo, settings and flows all carry over, just update from the App Store as normal.

As always, let me know if you spot anything else!

**App Store:** [Dashboard Alarm Keypad | Homey](https://homey.app/en-gb/app/com.simon.dashboardalarmkeypad/Dashboard-Alarm-Keypad/test/)

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 3, 2026, 3:18pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/3 "2026-11-03T15:18:59Z")

</div>

**Update: v1.1.1 👆**

Hi all,

Another little fix, and this one comes courtesy of my wife! Over a number of nights we’d come in together, the entry delay counting down, the hub beeping away, and she’d go to put the code in. The key would light up as if she’d pressed it, but no dot would appear, so by the time she hit Disarm there’d only be two or three dots instead of the full code. Not what you want with a siren about to go off!

So what was going on? The keypad was waiting for the iPad to decide each press was a proper “tap”, and if your finger stayed down a fraction too long, rolled slightly or you pressed quickly one after another, the iPad just ignored it. I was lucky, my taps must be lighter and quicker, so I’d hardly seen it happen.

Version 1.1.1 now counts the digit the moment you touch the key, the same instant it lights up, just like the passcode screen on your phone. Angela has been testing it for me and it’s a lot lot better, around 97% by her count. The other 3% is down to her nails, and in all honesty there’s not much I can do about those 💅 Her answer is to use a knuckle, and that works every time!

I’ve also submitted the app for certification, so it should be in the App Store properly very soon. Until then, the test link gets you the latest version, and that’s also where 1.1.0 (no more scrolling keypad) went, so ignore my last post about updating from the App Store, that was me getting ahead of myself 🤦🏻‍♂️

Test link: [Dashboard Alarm Keypad | Homey](https://homey.app/a/com.simon.dashboardalarmkeypad/test/)

As always, let me know how you get on with it, especially if you’ve hooked it up to a different alarm system?

* * *

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 5, 2026, 11:16am UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/4 "2026-11-05T11:16:22Z")

</div>

**Update: v1.1.2 🇩🇰🇳🇴🇸🇪**

Hi all,

So, the first trip through certification didn’t quite go to plan! Athom sent it back, all very friendly and nothing to do with how the keypad works, it was all about how the app looks in the App Store. The readme was too long (I’d listed every Flow card, guilty as charged), the description just repeated the readme, the app image was a keypad on an orange background rather than a proper picture, and the widget preview was a screenshot with text on it, which isn’t allowed.

All sorted now. The readme is down to two short paragraphs, the description is a proper one-liner, “Only the right code turns your alarm off.”, and the widget previews are simple shapes with no text. The new app image is a real photo of the keypad in use on our wall-mounted iPad in the hallway, with my wife kindly lending a hand, literally!

And while I had the bonnet up, I’ve added Danish, Norwegian and Swedish, so the app is now available in nine languages: English, Dutch, German, French, Spanish, Italian, Danish, Norwegian and Swedish. If you’re a native speaker and spot anything that reads oddly, please let me know?

Version 1.1.2 has been resubmitted for certification, so fingers crossed it’ll be in the App Store properly very soon. Until then, the test link has the latest version.

Test link: [Dashboard Alarm Keypad | Homey](https://homey.app/a/com.simon.dashboardalarmkeypad/test/)

As always, let me know how you get on with it!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 12, 2026, 4:51pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/5 "2026-11-12T16:51:11Z")

</div>

**It’s live in the App Store! 🚀**

Hi all,

Good news, Dashboard Alarm Keypad has passed certification and is now in the Homey App Store properly, no more test link needed!

Athom were really helpful along the way, and on approval they asked for one last thing: a support link, so you know where to go with questions. That’s this thread, so version 1.1.3 adds a link straight here from the App Store page. While I was at it, I’ve added a PayPal donate button too, entirely optional of course, but if the keypad saves you a frantic dash to the hallway one night, a coffee is always appreciated ☕

1.1.3 is with Athom for review now, so the support link and donate button will appear once that’s through. Everything else, the scroll fix, the more reliable key presses and the nine languages, is already in the version that’s live today.

If you’ve been running the test version, just install it from the App Store and you’ll stay up to date automatically from now on.

App Store: [Dashboard Alarm Keypad | Homey](https://homey.app/a/com.simon.dashboardalarmkeypad)

As always, let me know how you get on, and thanks to everyone who’s tried it so far!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 12, 2026, 5:15pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/6 "2026-11-12T17:15:47Z")

</div>

**Update: v1.1.4 🛠**

Hi all,

Well, this one was a bit embarrassing! Coming home this afternoon, my wife and I went to stop the alarm and the keypad just wouldn’t take the code. The keys lit up, but slow, deliberate presses weren’t entering a digit, all whilst the hub was beeping at us. Not ideal for an alarm keypad!

So what happened? Back in 1.1.1 I made the keys register the moment you touch them, which fixed missed taps. But the keypad also asks Homey for a little vibration on each press, and Homey only allows that just after a finger lifts. On a slow press your finger is still down, Homey said no, and the digit got lost along with it. Quick typing happened to slip through, which is why I hadn’t spotted it 🤦🏻‍♂️

Version 1.1.4 adds the digit first and simply skips the vibration if Homey won’t allow it, so every press counts however slowly you press. The same goes for the Arm and Disarm buttons.

The fix has been submitted to Athom for review, so it should be with you in the App Store very soon. It also includes the new support link and PayPal donate button I mentioned last time.

As always, let me know if you spot anything else?

---

<div class="post-metadata">

**Author:** ![Rembo038](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rembo038/32/79135_2.png) [@Rembo038](https://community.homey.app/u/Rembo038)\
**Post date:** [November 13, 2026, 8:19pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/7 "2026-11-13T20:19:49Z")

</div>

Hi @Simon_Salvin

Good idea; I’ve been looking for a keypad for my dashboard for a while now.

If I understand correctly, will the issue with entering the code be resolved in the next update? (Currently, when I try to enter the code, I have to press each digit 3 or 4 times before it registers.)

Would it be possible to add an “IF” tile that allows you to specify, for example, “if ‘Remco’ has entered the code”—linked to the codes stored in the app? That way, I could send a notification to myself and see exactly who disarmed the security system using their specific code.

The app looks great!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 13, 2026, 9:02pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/8 "2026-11-13T21:02:54Z")

</div>

Hi @Remco,

Thanks for the kind words, glad it’s what you’ve been looking for!

Yes, that’s exactly the bug the next update fixes. The keypad was losing slow or deliberate presses, which is why you’ve had to press each digit three or four times. It caught us out too, coming home one afternoon with the hub beeping away at us! Version 1.1.4 is with Athom for review now, so it should be in the App Store very soon. We were hoping it would be cleared today, so any day now.

If you don’t want to wait, the fix is already in the test version, so you can install it now from the test link. Once 1.1.4 is through review, you can switch back to the App Store version and you’ll get updates automatically from then on.

Test link: [Dashboard Alarm Keypad | Homey](https://homey.app/a/com.simon.dashboardalarmkeypad/test/)

On the who-disarmed-it idea, good news, you can already do most of that today. The “Correct code entered to disarm” trigger has a **User** tag with the name of the person whose code was used. So in your notification you can put “Alarm disarmed by [User]” and you’ll see exactly who it was.

If you want a flow to do something only when a particular person disarms it, add a Logic condition after the trigger, “[User] is equal to Remco”. That said, a ready-made “Code entered by…” card where you just pick the person from your saved codes would be a lot neater, so I’ll add that in the next update.

Thanks again for trying it!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 16, 2026, 10:40am UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/9 "2026-11-16T10:40:02Z")

</div>

**1.1.4 is live, and 1.2.0 is on its way**

Hi all,

Good news, version 1.1.4 has cleared review and is now live in the App Store! That’s the fix for slow or deliberate presses not entering a digit, so every press counts now, however slowly you press. It also brings the support link and the PayPal donate button I mentioned. If you’ve been using the test version, you can switch back to the App Store version and you’ll get updates automatically from now on.

And @Rembo038, your idea has made it in already! Version 1.2.0 adds a new Flow card, **Correct code entered by…** , where you just pick a person from your saved codes and the flow only runs when it’s their code that disarms the alarm. No more Logic cards needed. Handy for a notification when the kids get home, or to put the lights on for one person and not another?

1.2.0 is with Athom for review now, so it should be in the App Store very soon.

**App Store:** [Dashboard Alarm Keypad | Homey](https://homey.app/a/com.simon.dashboardalarmkeypad)

As always, let me know how you get on with it!

---

<div class="post-metadata">

**Author:** ![Lamkram](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lamkram/32/34405_2.png) [@Lamkram](https://community.homey.app/u/Lamkram)\
**Post date:** [November 16, 2026, 12:21pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/10 "2026-11-16T12:21:22Z")

</div>

Simon,

You’ve created a great app. I think a lot of people will start using it. I’m using a Lenovo Tap M10, and when pressing the keys, I had to press each one twice for it to register. I have no idea if others are experiencing this as well. I thought it would be helpful to let you know.

By the way, I’m using a Homey Pro 2026, version 13.5.4, and now the latest version, 1.1.4, and it works perfectly. Good thing I double-checked that last part.

Best regards, Mark

_Translated with [DeepL.com](https://www.deepl.com/?utm_campaign=product&utm_source=web_translator&utm_medium=web&utm_content=copy_free_translation) (free version)_

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 16, 2026, 12:42pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/11 "2026-11-16T12:42:59Z")

</div>

Thanks for your support and apologies for the initial bug, now fixed in the latest version.

---

<div class="post-metadata">

**Author:** ![Rembo038](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rembo038/32/79135_2.png) [@Rembo038](https://community.homey.app/u/Rembo038)\
**Post date:** [November 17, 2026, 1:40am UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/12 "2026-11-17T01:40:35Z")

</div>

Great work!

I just tested it, and I can now enter the code without any issues! You were quick to update the card to include the code entry feature; I hope Athom approves the update soon.

I previously used a keypad from a different dashboard app widget, but the numbers on that one were packed too closely together. Since I often enter the code while wearing my motorcycle gloves, your version is much better!

Would it be possible to adjust the background color of the keypad? For instance, having a red background when the security system is armed, and a green background when it’s disarmed? That way, you could tell at a glance—whether you’re walking past the keypad or looking from a distance—whether the security system is armed or disarmed. The other app had this feature, and those background colors were really useful.

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 17, 2026, 2:55am UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/13 "2026-11-17T02:55:33Z")

</div>

Hi @Rembo038,

Great to hear the code now goes in first time, and with motorcycle gloves on too! In all honesty that’s not something we thought about when we made the keys big, but I’ll take the compliment.

I liked the background colour idea straight away, so version 1.3.0 adds a new widget setting: **Status colour**. You can choose **Off** , **Coloured header** or **Coloured background**. With the coloured background the whole widget changes colour, and the keys always stay dark grey so they’re easy to see.

Every status has its own colour, so there’s never any confusion: Home is green, Night purple, Arming… amber, Armed red, and it flashes red when the alarm goes off. Disarmed stays neutral. Want to see green once you’ve disarmed? In the app settings, set **Status after disarm** to **Home**.

Coloured header:

 ![status-colour-header](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/a/2aa7651f5fb3b74f184a63c28b752769f1060c6a.png)

Coloured background:

 ![status-colour-background](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/b/2/b226ce5bbf96b5b18b9a83c103dffcb56a22ce25.png)

1.2.0 is still with Athom for review, and 1.3.0 is already waiting behind it, so it’s on its way!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 17, 2026, 3:05am UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/14 "2026-11-17T03:05:03Z")

</div>

And here’s what it looks like when the alarm actually goes off, coloured header on the left, coloured background on the right. The whole thing flashes and Stop alarm pulses, so there’s no missing it! 🚨

![status-colour-alarm](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/3/130595701171db1ffccf7e87ba0d7f5066dd189c.gif)

---

<div class="post-metadata">

**Author:** ![Rembo038](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rembo038/32/79135_2.png) [@Rembo038](https://community.homey.app/u/Rembo038)\
**Post date:** [November 17, 2026, 5:41pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/15 "2026-11-17T17:41:31Z")

</div>

Thanks, you pick up on ideas quickly!

It looks great with the colored backgrounds!

---

<div class="post-metadata">

**Author:** ![Simon\_Salvin](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/simon_salvin/32/144694_2.png) [@Simon\_Salvin](https://community.homey.app/u/Simon_Salvin)\
**Post date:** [November 17, 2026, 10:00pm UTC](https://community.homey.app/t/app-pro-dashboard-alarm-keypad-a-code-protected-keypad-for-any-alarm/161154/16 "2026-11-17T22:00:16Z")

</div>

Are you running the update in the test channel or waiting for the official update?
