Just made a switch from SABnzb to NZBGet, and out of curiosity I decided to finally give Pushover notifications a try from within NZBGet. I do realize this is also a feature of NzbDrone to push notifications using a variety of built-in push services, but never really activated this feature until now. After setting this up, all I can say is Pushover notifications are awesome… not sure how I went this long without them!
So putting some more thought into this, I decided that I would rather get the Pushover notifications from NzbDrone than my downloader (NZBGet). Reason being, NzbDrone will only push the notification after the file has been moved to its final destination, and renamed appropriately (after post processing if you will). These notifications from NzbDrone go out about 1-2 minutes after the push notification would go out from NZBGet, but are more accurate being that the file has already been renamed and moved.
One problem however that’s occurring with the Pushover notifications from NzbDrone is that the URL field is not being passed through to the notification. I’m choosing to put my local NZBGet web admin URL into the notifications, for ease of being able to quickly look at download history, etc… And those push notifications coming from NZBGet do pass the URL, but those coming from NzbDrone do not.
Here are some screenshots (photoshopped slightly to mask my downloader URL):
NzbDrone Pushover Setup:
Screenshot of Pushover notification from NZBGet:
Screenshot of Pushover notification from NzbDrone:
The only difference in setup being that NZBGet has Pushover variables (including URL) which get set directly from within the program. Where with NzbDrone, the URL variable is set on the Pushover side.
Any thoughts/suggestions would be greatly appreciated.
I could be mistaken, but I don’t believe the URL field within the configuration on pushover.net actually gets passed along with the notification–I think it’s for reference purposes (hence why they use the git page as an example). With NZBGet, (I believe) the URL of the download is passed as part of the notification.
You could make a feature request to add additional configuration options to the pushover notification from within NzbDrone. This does seem to me, however, to be an uncommon use case.
Just trying to rack my brain on some other options… If you use Plex, one way you could go about doing this would be to install PlexWatch (it’s a script designed to provide notifications for shared users watching your media, but one feature is the ability to send notifications on new additions to the library). It’s pushover configuration is very configurable. At the very least, you may be able to review the code and see how to create your own implementation of pushover. But ultimately if you want that nzbget link, you’re probably best keeping it simple and sticking with nzbget notifications.
@sdjaime Yeah, thats exactly it, the URL set on the Pushover App (on their site) do not get pushed with the alerts.
drone leaves the URL blank when pushing a notification. Nzbget must be setting it though.
It would be a feature we would have to add to include it, but I don’t see a huge advantage (assuming we just included the nzbdrone URL), I guess having it assignable would make sense, but at the same time, why, if it imported to drone then the download was successful.
Thank you for the responses and information. I fooled with a couple different URL’s to pass through when setting this Pushover variable on NZBGet, and the only one that made sense is linking directly back to the web admin. So it’s not necessarily hard-set in NZBGet to link back to itself, but I did choose to link it that way (while passing along the username/pass to the web admin).
I don’t have port forwarding enabled in my router, so I’m really only able to reach the web admin of NZBGet when I’m on my local network anyway.
Just thought I might have had something set incorrect, or not set at all. But again, thank you for the clarification and for a fantastic program!