Connect Pushover
Who acts: an administrator with sudo on the MMHotline server, or that
person's coding agent, with whoever holds the team's Pushover account.
Then each person on the team, on their own phone.
When to use this page: to have MMHotline wake people through the Pushover app on their phones, or to replace the team's Pushover token.
What this page does: you create a Pushover application for the team, connect it to MMHotline, add each person's phone as a contact method, and test that an emergency alert wakes them, also in silent mode.
Terms:
- An SOS is the urgent alert that wakes the person on call. Pushover sends it at emergency priority, which repeats until the person acknowledges it.
- The application token identifies the team's MMHotline application at Pushover, the sender. A person's user key identifies that person, the receiver. Each is 30 letters and digits, with upper and lower case, and both are private.
- A contact method is one place where a person gets notifications, here one person's user key.
Choose the route
- Connect Pushover for the first time: follow Steps.
- Pushover is connected, and a person adds their phone: start at step 3.
- Replace the token or remove Pushover: see Change or remove the setup.
Before you start
- MMHotline is installed, and you can change its settings file, as Change the settings says.
- The server can reach
api.pushover.netover HTTPS. - Each person has a Pushover account and the Pushover app, signed in on
their phone, and is listed in
peoplein the settings file.
Steps
-
Create the team's application at Pushover. Sign in at pushover.net, create an application named MMHotline, and copy its API token.
Check: the token is 30 letters and digits.
-
Connect it to MMHotline. Add the token to the settings file, under
sending_services:sending_services: pushover: application_token: YOUR_30_CHARACTER_APPLICATION_TOKENThen apply the file:
sudo mmhotline settings applyCheck: among the lines it prints are:
sending_services.pushover: applied. sending_services.pushover: Next step: Add your own Pushover user key under Contact methods. Saving the Pushover contact method sends an emergency test alert.MMHotline checked the token with Pushover, and saved the application's monthly message limit, without sending a notification.
sudo mmhotline sending-services listnow saysPushover: set up by the settings file ... Checked with Pushover: monthly message limit 10000. -
Add each person's phone. Each person copies their own User Key from the main page of pushover.net after signing in. Then, in MMHotline, they open Contact methods, paste the key into Pushover user key under Add Pushover notification, and choose Add Pushover notification.
An administrator can add it for a person from the server instead, with that person's sign-in email address from
people:sudo mmhotline contact-methods add --sign-in-email-address barbara@example.com \ --contact-method-type pushover_notification --pushover-user-key-file -The command waits for the key: paste it, press Enter, then Ctrl-D. A coding agent pipes the key in instead. Reason: a key on the command line would stay in the shell history.
Use a personal user key, never a Pushover delivery group's key. Reason: acknowledging an SOS claims the incident as the key's owner, so MMHotline must know whose key it is.
Check: the command, or the page, says the contact method is saved and a test is queued:
Contact method saved. A test message for the contact method is queued. Inspect the last test result to check delivery.The new contact method gets SOS, Warning, and Info alerts at once, because Pushover is often a person's only contact method. A person can change that on its card, or an administrator with
--alert-severities. Like every personal contact method, it skips times the person is unavailable, unless the card's Send even when I'm unavailable is on, and team mute always stops it. Links in the notifications open MMHotline, where Cloudflare Access signs the person in with their sign-in email address frompeople. -
Check that the test arrived. The person's phone shows MMHotline test message at emergency priority, repeating until they acknowledge it in Pushover. Acknowledging a test claims no incident.
Check: the card's Last test on the Contact methods page says Accepted by Pushover, and
sudo mmhotline contact-methods listsays:Send while unavailable or muted: false. Last test message: accepted (queued at 2026-11-15T05:08:44Z).Accepted means Pushover took the message. It does not prove the phone sounded; step 5 does.
-
Make an emergency alert wake the person. A notification that arrives silently does not wake anyone. Without Critical Alerts, an emergency alert arrives silently on a muted iPhone, and Pushover's default sound is a soft bell.
On an iPhone:
- In the Pushover app's settings, turn on Critical Alerts for emergency priority, and accept Apple's permission prompt. Nothing needs changing in the iPhone's own Settings. Critical Alerts for high priority can stay off: MMHotline sends nothing at high priority.
- In the app's sound settings, choose an alarming sound and raise its volume. Pushover plays Critical Alerts at the app's volume, not the phone's.
- Turn on Silent Mode. On MMHotline's Contact methods, press Send test on the Pushover card, and acknowledge the alert when it sounds.
- Turn Silent Mode off and Do Not Disturb on, and press Send test again.
On Android, follow Pushover's Overriding Do Not Disturb on Android, which differs by phone maker, choose an alarming sound, and run the same two tests: muted, then with Do Not Disturb on.
An administrator can send a test from the server too:
sudo mmhotline contact-methods send-test --contact-method-id ID, with the ID thatcontact-methods listprints. Wait at least a minute between tests, also after the automatic test when the contact method was saved. Send test sends at emergency priority, like an SOS, and acknowledging it claims no incident.Check: in both tests, the phone sounds loudly enough to wake the person. A test that arrives silently, or too quietly, fails.
What MMHotline sends through Pushover
| Message | Pushover priority | Repeats |
|---|---|---|
| SOS | Emergency | Every 30 seconds, for up to 25 minutes per message |
| Test | Emergency | Every 30 seconds, for up to 10 minutes |
| Warning | Normal, which respects Pushover's quiet hours | None |
| Info and resolved alerts | Low, without sound or vibration | None |
The 30-second repeat is Pushover's shortest. A test ends after 10 minutes, so a test nobody acknowledges stops by itself. Each person chooses the sound in Pushover.
- Acknowledging an SOS in Pushover claims the incident for the contact method's owner, the same as Claim on the incident's page. It never takes over another person's claim. MMHotline checks for acknowledgements at most every five seconds.
- Repeats stop when the incident is claimed or resolved, the person becomes unavailable, the incident moves on to someone else, the contact method is removed or its user key changed, or an administrator mutes the team. Team mute stops even the repeats already sounding.
- The 25-minute limit comes from Pushover, which repeats an emergency at most 50 times. If the SOS still needs the person after that, MMHotline sends a fresh one.
- Several SOS alerts due at once may arrive as one notification; acknowledging it claims every listed incident that can still be claimed.
- Long alerts are shortened to Pushover's limits of 250 characters for the title and 1,024 for the text, keeping the claim instruction and the Open in MMHotline link. A link longer than Pushover's 512 characters is not shortened into a broken address; the message fails instead.
- Each person can have up to three Pushover contact methods, and a key only once, so one alert does not reach many copies by mistake. A Pushover contact method belongs to one person, cannot be shared with the team, and only its owner changes it on the page.
Change or remove the setup
Replace the token when someone who knew it leaves the team, or when it may have leaked. A person's user key works with any application, so every contact method stays.
-
Create a new application named MMHotline, and copy its token.
-
Put the new token in
sending_services.pushover.application_token, and apply the file. A coding agent that has the token in a file puts it in without showing it, as step 3 of Get started does for a secret.Check: the line says
sending_services.pushover: applied. -
Send yourself a test with Send test, or
sudo mmhotline contact-methods send-test --contact-method-id ID, and check that it arrives from the new application. -
If the MMHotline-down alarm is set up, its held messages use the new token within 5 seconds;
sudo mmhotline down-alarm send-testsends a test through it.
MMHotline stops using the old token at once, but cannot revoke it at Pushover: anyone who still has it can send through the old application.
If the apply says
sending_services.pushover: did not apply: wait for MMHotline to close the open Pushover emergency messages before replacing or removing the application.,
an emergency is still repeating on someone's phone, a test or an SOS, and
MMHotline needs the old token to stop it. The rest of the file applied,
and the old token keeps sending meanwhile. Apply again once each one is
acknowledged, cancelled, or expired: a test expires within 10 minutes, an
SOS within 25. So replace the token at least 10 minutes after the last
Send test.
Remove Pushover: remove every Pushover contact method first, then
delete the pushover section and apply. While contact methods still use
it, the apply keeps the setup and says
cannot remove the Pushover setup: 2 Pushover notification contact methods use the sending service setup.
If something is different
- The check says
sending_services.pushover.application_token: must be one line of exactly 30 letters and digits, as Pushover shows the application's API token: copy the whole token again, keeping upper and lower case. - The apply says
sending_services.pushover: did not apply: Checked with Pushover: Pushover answered HTTP 400: application token is invalid. The earlier setting, applied at ..., stays.Pushover does not know the token. Copy it again from the application's page at Pushover. Nothing changed: if Pushover was connected before, the old token keeps sending; if it was not, the line endsIt stays not set up, as before. - Adding the contact method says
Pushover user key must contain exactly 30 letters and digits: copy the whole user key again. - Adding it says
you already added this Pushover notification contact method: the person already has that key; use the existing card. - The last test says
failedwithPushover answered HTTP 400: user identifier is invalid: the user key is wrong, or is the application's token. Remove the contact method and add it again with the person's own user key. - No test arrives, but nothing failed: check that the person is not marked unavailable and the team is not muted, since tests follow the same rules as alerts.
- Any other message: the Pushover messages table says what each one means.
This page is docs/how-to/connect-pushover.md in the MMHotline repository.