Something not ringing? Pick where it is happening. If the answer is not
there, write to us — a person reads it.
This deployment · last updated 31 October 2026
Getting the extension
| Browser | |
|---|
| Chrome |
On the Chrome Web Store. Pair it with a code from
Devices in the console — there is no sign-up in the
extension and it never asks for a password. |
| Firefox |
Not published yet. It is built and working; the
addons.mozilla.org review is still to come. |
A browser is the weakest receiver we offer, and it is worth knowing why
before you rely on one. It cannot wake a sleeping computer, cannot ring
through Do Not Disturb, and stops when the browser does. Two browsers are
not better than one. Keep a phone or desktop client for anything you
cannot afford to miss — the extension says so in its own popup when it is
the only receiver on an account.
Where is it happening
| Where | |
|---|
| Chrome extension |
Pairing, the alert, the chime, and what a browser cannot do. |
| Firefox extension |
Answering from the popup, late alarms, and the same browser limits. |
| Phone and desktop apps |
Its own page is coming. If alarms arrive during the day but not
overnight, allow the app to run in the background and exclude it
from battery optimisation. |
Writing to us
support@alarmsender.com. Four
things make an answer much quicker, and you will usually have them already:
- which device — phone, desktop app, Chrome, Firefox
- roughly when it happened, and your timezone
- what you expected and what happened instead
- whether the alarm shows in Activity in the console
That last one splits the problem in half. An alarm in Activity reached the
service and the question is about delivery; nothing in Activity means
whatever was meant to raise it never did.
Please do not send us a trigger URL. Anyone holding one can ring your
alarms, and it never expires. The trigger's name is enough.
A trigger that does not ring
-
Press Ring beside the trigger in the console. If that
rings, the trigger and your devices are fine and the problem is with
whatever was supposed to call it.
-
Open the trigger URL in a browser tab. It is an ordinary GET, and the
reply says what happened.
-
Check Activity. An alarm there that reached no device
means a delivery problem; nothing there means the request never arrived.
Email triggers only accept whole addresses on the allowlist. A whole domain
cannot be allowed, deliberately — anyone who can forge a sender on that
domain could ring your alarms.
Is it us or is it you
Both hosts answer a health check with no sign-in, so you can tell the
difference without waiting on us:
curl https://alarmsender.com/health
curl https://alrm.sh/health
If those answer and your alarms do not, the problem is in delivery or
configuration rather than the service being down — say so when you write
and it saves a round trip.
Your account and your data
The privacy policy says what is stored and for how
long. You can clear your alarm history, or close the account entirely, from
the Account tab in the console; if you cannot sign in,
the deletion page does it without one.
Alarm Sender is operated by Single Breath LLC.