Pushover HTTP 429 error
-
- Donor
- Posts: 53
- Joined: 24 Apr 2014, 19:30
Pushover HTTP 429 error
Hey Noah,
Pushover recently tonight started generating an HTTP 429 error code (too many requests). Is this due to filebot hitting its monthly quota or something else?
Thanks,
Tweak
Pushover recently tonight started generating an HTTP 429 error code (too many requests). Is this due to filebot hitting its monthly quota or something else?
Thanks,
Tweak
Re: Pushover HTTP 429 error
Yep. Looks like it's hitting the 7500 messages per month limit.
I highly recommend using PushBullet instead.
I highly recommend using PushBullet instead.

Re: Pushover HTTP 429 error
7500 for all filebot users? Or is this an individual limit. I received 49 push notifications so far.
- mrbucket101
- Power User
- Posts: 36
- Joined: 02 Jul 2014, 00:25
Re: Pushover HTTP 429 error
Thank you for the advice, I have just switched over. In the past 10 minutes I've used it, it is better, and I like that it provides full reports.rednoah wrote:Yep. Looks like it's hitting the 7500 messages per month limit.
I highly recommend using PushBullet instead.
I am curious though, is there any sort of push limitation like the one pushover has?
Re: Pushover HTTP 429 error
Nope. PushBullet is superior in every way. 

- mrbucket101
- Power User
- Posts: 36
- Joined: 02 Jul 2014, 00:25
Re: Pushover HTTP 429 error
Actually, I think I might have found the one and only difference.rednoah wrote:Nope. PushBullet is superior in every way.
pushover notifications contain the original file name in the base notification, so you can glance and see just what was processed, without opening the app. All of my pushbullet notificaitons just say "file: FileBot finished processing X files". Then I have to open the app to view the original file name, and/or the full report.
Is there anyway to include the original file name, or new file name, in the base notification for pushbullet? That would easily make it superior in every single aspect.
Not a huge deal, I can run pushover and pushbullet, but if i can switch to a unified notification system, I'd rather do that.
Re: Pushover HTTP 429 error
Hi All,
Before I found this forum post, I had actually submitted a support ticket with Pushover thinking the problem was on their side. The support person was very helpful and said he raised the limit and that it should work for me again. I asked a few more questions and I thought I would share his response.
----
Filebot's Pushover integration is pretty old, and all users share
one key which can result in this type of problem. In the past year
or so we've changed our recommended way of doing things so that each
user clones the app on our website and gets their own API key. This
way one user sending out a ton of notifications won't affect any
other users.
https://pushover.net/faq#technical-distribution
I've doubled Filebot's monthly limit to accommodate them so this
shouldn't be an issue for a while, but going forward they should
probably switch to requiring users to register their own API token.
Before I found this forum post, I had actually submitted a support ticket with Pushover thinking the problem was on their side. The support person was very helpful and said he raised the limit and that it should work for me again. I asked a few more questions and I thought I would share his response.
----
Filebot's Pushover integration is pretty old, and all users share
one key which can result in this type of problem. In the past year
or so we've changed our recommended way of doing things so that each
user clones the app on our website and gets their own API key. This
way one user sending out a ton of notifications won't affect any
other users.
https://pushover.net/faq#technical-distribution
I've doubled Filebot's monthly limit to accommodate them so this
shouldn't be an issue for a while, but going forward they should
probably switch to requiring users to register their own API token.
- mrbucket101
- Power User
- Posts: 36
- Joined: 02 Jul 2014, 00:25
Re: Pushover HTTP 429 error
I appreciate this, thanks!tijiez wrote:Hi All,
Before I found this forum post, I had actually submitted a support ticket with Pushover thinking the problem was on their side. The support person was very helpful and said he raised the limit and that it should work for me again. I asked a few more questions and I thought I would share his response.
----
Filebot's Pushover integration is pretty old, and all users share
one key which can result in this type of problem. In the past year
or so we've changed our recommended way of doing things so that each
user clones the app on our website and gets their own API key. This
way one user sending out a ton of notifications won't affect any
other users.
https://pushover.net/faq#technical-distribution
I've doubled Filebot's monthly limit to accommodate them so this
shouldn't be an issue for a while, but going forward they should
probably switch to requiring users to register their own API token.
Maybe add a --def pushoverapi="<API KEY>" to the amc script.
Then we can all register our own application and get 7500/month/person
Re: Pushover HTTP 429 error
I've requested a clone URL for FileBot.
- mrbucket101
- Power User
- Posts: 36
- Joined: 02 Jul 2014, 00:25
Re: Pushover HTTP 429 error
Nicerednoah wrote:I've requested a clone URL for FileBot.
Do you know if there is a way to include some info about the file being processed in a pushbullet notification?
I like the full report pushbullet provides, but would like the pushover style notification instead of simply saying "file:Filebot processed 1 file"
Right now I'm running both and I just turned the pushbullet alerts off so I can view reports of needed
Re: Pushover HTTP 429 error
Pushover shows title and parts of the message in it's notification. PushBullet only shows the title. So that can't be fixed right now, but you could send a feature request to PushBullet. 

Re: Pushover HTTP 429 error
Here's the Pushover Clone URL for FileBot
https://pushover.net/apps/clone/FileBot
What happens if you clone your own app that way? Do you still only need the access key? Or will you need to pass your own api key as well as the access key?
https://pushover.net/apps/clone/FileBot
What happens if you clone your own app that way? Do you still only need the access key? Or will you need to pass your own api key as well as the access key?
Re: Pushover HTTP 429 error
You can now specify your own application key / API authentication token.
Please use -script dev:amc to test the changes before they're merged into the stable branch
Code: Select all
--def pushover={USERKEY}:{APPKEY}
- mrbucket101
- Power User
- Posts: 36
- Joined: 02 Jul 2014, 00:25
Re: Pushover HTTP 429 error
I love that filebot is constantly being updated with new features. This one especially.rednoah wrote:You can now specify your own application key / API authentication token.
Please use -script dev:amc to test the changes before they're merged into the stable branchCode: Select all
--def pushover={USERKEY}:{APPKEY}
I switched to the dev branch of AMC, and added the API key to my notifications, and so far so good. I've got 7499 notifications left this month

I'll leave it like this for the next week and let you know of any problems
thanks!