Help with Pushover Notifications
Posted: Mon Apr 12, 2021 12:20 pm
First, I just have to thank the stars for such a great program and everyone involved for making Mylar a reality! I wish I'd been smarter and found out about this sooner. I'm still organizing my collection (and tracking down missing issues). Just think, Mylar could have helped me with that years ago!
As I start to explore more options, I noticed the Pushover notifications settings. Something like this is what I was wanting and finally got around to noticing the different options. I tried setting it up, but failed. However, I did get Pushover settings working for SABnzbd and Sonarr, so I'm pretty sure it is me not setting this up correctly. I created the API key, but I think my problem is not knowing how to set up the API code for Mylar to push notifications. I then searched the Mylar boards and came across this:
curl -s -F "user=${USER_KEY}" -F "token=${API_KEY}" -F "message=${BODY}" https://api.pushover.net/1/messages.json
I think I can figure out the user key and api key, but is the message body what I want the notification to say? With SABnzbd/Sonarr, I checked some settings and then it would tell me the release that I was grabbed for me. I guess I'd just put a generic message here--hey, an issue was post-processed for you. But more importantly, where does that curl code go? Do I run it as a git command from within mylar? This is probably above my pay grade, but I was hoping to get it working.
Once again, thanks. Once I get this working, hopefully, I still have some questions about file names because every once in awhile, I am stumped for why some files are recognized...I'm looking at you Elves!
As I start to explore more options, I noticed the Pushover notifications settings. Something like this is what I was wanting and finally got around to noticing the different options. I tried setting it up, but failed. However, I did get Pushover settings working for SABnzbd and Sonarr, so I'm pretty sure it is me not setting this up correctly. I created the API key, but I think my problem is not knowing how to set up the API code for Mylar to push notifications. I then searched the Mylar boards and came across this:
curl -s -F "user=${USER_KEY}" -F "token=${API_KEY}" -F "message=${BODY}" https://api.pushover.net/1/messages.json
I think I can figure out the user key and api key, but is the message body what I want the notification to say? With SABnzbd/Sonarr, I checked some settings and then it would tell me the release that I was grabbed for me. I guess I'd just put a generic message here--hey, an issue was post-processed for you. But more importantly, where does that curl code go? Do I run it as a git command from within mylar? This is probably above my pay grade, but I was hoping to get it working.
Once again, thanks. Once I get this working, hopefully, I still have some questions about file names because every once in awhile, I am stumped for why some files are recognized...I'm looking at you Elves!