[FEATURE] Add support for Pushover notifications. #70

New Issue

giteasync · 2025-10-09T16:57:29-05:00

giteasync commented

2025-10-09 16:57:29 -05:00

Originally created by @cybrnook on GitHub.

What would you like to see implemented next?

Would be very cool to see Pushover added to the supported notifications api. This is what I currently use from the available notification services in Unraid, so having everything in one basket would be great.

Thanks for the great work!

Originally created by @cybrnook on GitHub. ### What would you like to see implemented next? Would be very cool to see Pushover added to the supported notifications api. This is what I currently use from the available notification services in Unraid, so having everything in one basket would be great. Thanks for the great work!

giteasync added the

enhancement

planned

labels 2025-10-09 16:57:30 -05:00

giteasync commented

2025-10-09 16:57:30 -05:00

@H2OKing89 commented on GitHub:

Hey @cybrnook,

You’re in luck—Apprise is already supported and it plays very nicely with Pushover!

Just use the pover:// URL format with your user key and token. You can even target specific devices if you want to annoy—I mean, alert—your whole fleet.

Examples:

pover://your_user_key@your_token
pover://your_user_key@your_token/DEVICE
pover://your_user_key@your_token/DEVICE1/DEVICE2

(You must specify both your user ID and token, or the Pushover gods will not be pleased.)

If you want more details, check out the Apprise docs here:
https://github.com/caronc/apprise

So, you’re already a basket case—in the good way! No need for any extra plugins.

@H2OKing89 commented on GitHub: Hey @cybrnook, You’re in luck—**Apprise** is already supported and it plays *very* nicely with Pushover! Just use the `pover://` URL format with your user key and token. You can even target specific devices if you want to annoy—I mean, *alert*—your whole fleet. **Examples:** ``` pover://your_user_key@your_token pover://your_user_key@your_token/DEVICE pover://your_user_key@your_token/DEVICE1/DEVICE2 ``` *(You must specify both your user ID and token, or the Pushover gods will not be pleased.)* If you want more details, check out the Apprise docs here: [https://github.com/caronc/apprise](https://github.com/caronc/apprise) So, you’re already a basket case—in the good way! No need for any extra plugins. ![Image](https://github.com/user-attachments/assets/fef551f5-544a-438e-9ad7-8b0dfab5e5b6)

giteasync commented

2025-10-09 16:57:30 -05:00

@cybrnook commented on GitHub:

Attempting to test pushover with apprise is proving unsuccessful. Defining my apprise URL as pover://< pushover user id >@< key for cleanuparr app in my pushover account > yields no notifications coming my way. I am leaving the "key" field blank. I have also tried terminating my URL with /iPhone as well, as that's one of my devices and it's the same thing, no notifications.

@cybrnook commented on GitHub: Attempting to test pushover with apprise is proving unsuccessful. Defining my apprise URL as pover://< pushover user id >@< key for cleanuparr app in my pushover account > yields no notifications coming my way. I am leaving the "key" field blank. I have also tried terminating my URL with /iPhone as well, as that's one of my devices and it's the same thing, no notifications.

giteasync commented

2025-10-09 16:57:31 -05:00

@cybrnook commented on GitHub:

@H2OKing89 Did you leave the key field empty?

@cybrnook commented on GitHub: @H2OKing89 Did you leave the key field empty?

giteasync commented

2025-10-09 16:57:31 -05:00

@Flaminel commented on GitHub:

@cybrnook Cleanuparr needs the Apprise API URL. It does not send the message directly to Pushover, but sends it to your Apprise instance to send it further down the pipe. The configuration key refers to the id of your Apprise config, which tells Apprise where to send the notification (Pushover in your case).

@Flaminel commented on GitHub: @cybrnook Cleanuparr needs the [Apprise API](https://github.com/caronc/apprise-api) URL. It does not send the message directly to Pushover, but sends it to your Apprise instance to send it further down the pipe. The configuration key refers to the id of your Apprise config, which tells Apprise where to send the notification (Pushover in your case).

giteasync commented

2025-10-09 16:57:31 -05:00

@cybrnook commented on GitHub:

@H2OKing89 Saweeeet, testing it now. Had no idea apprise was a consolidated service.

EDIT: All done! Would be cool to see a "test" button in the future, just to spot check it's setup correctly.

EDIT 2: Unfortunately didn't work.

@cybrnook commented on GitHub: @H2OKing89 Saweeeet, testing it now. Had no idea apprise was a consolidated service. EDIT: All done! Would be cool to see a "test" button in the future, just to spot check it's setup correctly. EDIT 2: Unfortunately didn't work.

giteasync commented

2025-10-09 16:57:31 -05:00

@cybrnook commented on GitHub:

In the end, having native pushover support would for sure be "my" preferred method.

@cybrnook commented on GitHub: In the end, having native pushover support would for sure be "my" preferred method.

giteasync commented

2025-10-09 16:57:32 -05:00

@cybrnook commented on GitHub:

So is that something I get just by creating an account with apprise, or something along the lines of a separate docker that needs to be stood up to provide that server functionality? (sorry, out of pocket at the moment so just relying on your feedback)

@cybrnook commented on GitHub: So is that something I get just by creating an account with apprise, or something along the lines of a separate docker that needs to be stood up to provide that server functionality? (sorry, out of pocket at the moment so just relying on your feedback)

giteasync commented

2025-10-09 16:57:32 -05:00

@Flaminel commented on GitHub:

The Apprise API is a separate Docker container indeed.

@Flaminel commented on GitHub: The Apprise API is a separate Docker container indeed.

giteasync commented

2025-10-09 16:57:32 -05:00

@Flaminel commented on GitHub:

No problem! Test it first and let me know how it goes. It might be worth adding support for Apprise without the separate container at some point.

@Flaminel commented on GitHub: No problem! Test it first and let me know how it goes. It might be worth adding support for Apprise without the separate container at some point.

giteasync commented

2025-10-09 16:57:32 -05:00

@cybrnook commented on GitHub:

Thanks! Want me to close this in the meantime?

@cybrnook commented on GitHub: Thanks! Want me to close this in the meantime?

giteasync commented

2025-10-09 16:57:32 -05:00

@cybrnook commented on GitHub:

Thanks! I tried yesterday to get apprise up and running, and started going down a rabbits hole.

@cybrnook commented on GitHub: Thanks! I tried yesterday to get apprise up and running, and started going down a rabbits hole.

giteasync commented

2025-10-09 16:57:32 -05:00