What are /r/pushover's favorite Products & Services?

From 3.5 billion Reddit comments

Looks awesome! If you want to write up a blurb about it and attach a high-res icon, I can list it on the open clients page. Just e-mail it to .

If you have paid for a desktop license, we don't really care if you use an unofficial client so long as it doesn't hammer our API.

However, looking at this code, it pretends to be an Android device which is wrong for a few reasons. First, it means we're going to try to send any new messages to Google's servers for the bogus provider id that this client generated which is wasteful, but more importantly it will cause our servers to disable your device because Google will reply to us saying your device id is bogus. And since it has no "push" mechanism, it just polls our API every 5 seconds looking for new messages. At that point, why bother using our push API?

Anyway, to implement a proper client, ~~it should register as a desktop/browser device (like an os value of "F" for Firefox)~~ see our Open Client API documentation. This will stop us from trying to send your messages to Google, but also allow you to connect to our websocket server and actually listen for new notifications which will show up as soon as we get them. This way it's not wasting bandwidth polling every 5 seconds.

We will try to get some formal client API documentation up soon so all of the various 3rd party clients can act like our desktop client rather than trying to reverse engineer our mobile apps.

Lots of other apps and services integrate directly with Pushover, so if you use any of those or want to send your own notifications, then having both is useful. If not, just using IFTTT is probably what you want.

You can set it for all e-mail to that address by editing it on your dashboard or creating a new alias that is a certain priority.

You can change it per-email by e-mailing xxxxxx+p= for priority 1.

The amount of messages shouldn't matter as it only pulls the newest 15 or so, but it's not surprising that there's problems with WatchOS 1.

If it happens again, you can try uninstalling the app from the watch (through the Watch app on the iPhone) and reinstalling it. If that still fails, drop us a line and we'll try to diagnose more in depth.

Obviously we would much rather have users report abuse to us so we can stop the sender from sending out junk in the first place, but you can more or less have throwaway keys now by creating a group with just your user key in it and then using the group key instead of your user key. When you no longer need it, you can just delete the group.

They are a little help. They sent the second half; https://ifttt.com/pushover/actions/glance

I just need to figure out how to generate a count now. A count that will update with my acknowledging/deleting events on the phone. That's going to be hard.

Send a support request at https://pushover.net/support while logged in so I can check your account logs. On your wife's device, open the settings menu in the app and tap Resolve a problem, then tap the icon in the upper right corner to send debug logs.

Once Debug Logs are enabled, when the next push notification is supposed to send, it will log data which is visible in the 'Logs' tab of the Pushover Notifications for WordPress settings screen: https://cloudup.com/cbsXfBoNOzI

You can login to https://pushover.net/, select the application at the bottom that you used for SharpTools notification, and click Edit at top. Then you will see the application editing page where you can choose a app icon in "New Icon" field.

priority - send as -2 to generate no notification/alert, -1 to always send as a quiet notification, 1 to display as high-priority and bypass the user's quiet hours, or 2 to also require confirmation from the user

https://pushover.net/api

That is definitely not allowed, and is why we have the 10-device limit.

https://pushover.net/faq#overview-fees

Every device owned or primarily operated by a different person needs to be on its own account. If you need centralized management of multiple accounts, check out Pushover for Teams:

https://pushover.net/teams

I'm assuming you are using PHP. If so, you need to add the CURLOPT_RETURNTRANSFER option to the curl call.

You can send URLs with notifications that open in apps, and then enable the "Auto-open URLs" option.

Please see https://pushover.net/faq#overview-fees

This has been fixed in the newest beta. I'm trying to get it approved through App Review as soon as possible but Apple are rejecting it for stupid and unrelated issues.

Did you see this?

https://pushover.net/faq#ios-customsounds

I know that's ios specific, but might give you a clue why you can't have your own sound play.

If you keep getting those e-mails about your phone being unreachable, then there is something wrong with the phone and most likely you'll need to uninstall the Pushover app and reinstall it. We don't send those e-mails about the watch being unreachable, only the phone, but since we process glance API updates through the device the watch is attached to (your phone), if your phone is disabled at the time you call our glances API, it won't process the update.

As for the watch not updating otherwise, Apple puts very strict limits on the frequency of updates to complications, as we mention in our API documentation. It's up to you to throttle those, and if you send out glance updates too frequently, the watch complication will stop processing updates in order to save battery life.

If you're still having issues, please contact us while logged in so we can check your account.

The name is cached on the client side, so it may not update properly even if we change it on our side.

Create a new application with the name you want, then e-mail us with the two API keys and we'll swap them on our end, giving the new name to your old API key. That will allow you to keep using the old key but have a new application record that clients will see and cache properly.

You will get an e-mail when your application is nearing its capacity.

You can also check the headers of the response from our API each time you send a message, which let you know the number of messages remaining. https://pushover.net/api#limits

Try this: https://pushover.net/faq#technical-email

It has formatting instructions for setting the priority. Well, never mind, just noticed that emergency isn't supported, likely because the send by email method doesn't have a way for the sender of the push to be notified that it is acknowledged.

View your app on our website, and it will show you per-day stats as well as how many license credits are remaining (if any). It is also reported in the API response when assigning a license.

A whole bunch of stuff has been changed under the hood with this release, so we'd like to get as much testing as we can before we push it out to everyone.

Feel free to post feedback here or contact us directly.

Are you part of our TestFlight beta program? I'll get a beta release pushed out so you can get the fix.

If you are not part of it, send us a note at https://pushover.net/support with your e-mail address and we'll send you a beta invitation.

In short, these are not easily changeable just to make them consistent as they are used in the iOS and Android clients. Any parameters in the response that are not documented (such as "user" that you are having to work around) should be ignored.

Length and valid character sets for input parameters are documented at https://pushover.net/api#identifiers and anything not documented should not be limited in your client. Just send it to the server and if it's invalid, it will come back with an error. It's better than hard-coding limitations that we change later in the API but never get updated in your client.

As I understand it, the "desktop" client is web-based and does not require any special installation. There are a few caveats:

1. Unless it is being used in Safari for Mac OS X 10.10 or newer, it will require the Pushover web page to be open in order to receive notifications.
2. Like all Pushover clients, it requires a license to be purchased for $5 if it's going to be used for longer than a week. (Doesn't matter whether you buy it or the end user buys it, but someone has to buy it. I think a volume discount is available if you are buying in bulk.)
3. The desktop license is specifically for the web-based app, as well as the "open," third-party apps not developed by Pushover. It cannot be used with the iOS or Android apps. Otherwise, it is a per-user license (i.e., one user can use a single license for the web app and any third-party clients).

We have a beta program going for our next release to hopefully fix these crashes (and we have already fixed the 'All Messages' problem). If you're interested in joining, just drop us a message with your e-mail address and we'll send you a TestFlight invitation.

If you have a list of users you want to buy licenses for, you can use our Volume License Tool: https://pushover.net/licensing/volume

If you want to buy a bunch of license credits and then assign them to users in the future one by one, you can use our Licensing API: https://pushover.net/api/licensing

That is correct. Priority 2 is not available through the e-mail gateway (for reasons explained in the note at https://pushover.net/faq#technical-email) so you would need to send those over our HTTP API.

There is no existing feature like that.

You could use priority 2 messages and have them repeat every 30 seconds for 15 minutes, and store the receipt id. If the condition changes and you want to cancel the retry, just cancel the receipt and it will stop retrying. Though it won't delete the original notification (which is not possible on iOS anyway).

I'm not sure if iOS' built-in URL detection will pick up a URL like "teamworkpm://" in the message and turn it into a clickable URL.

You can supply an actual URL if you talk to our API (see the documentation) but there isn't a way to do it through our e-mail gateway.

If the messages are all the same, you can create a delivery group and add each user's key to it. Then from the dashboard you can just select your delivery group, enter a title/message, and send them off.

You'll need to register an app, and then send the messages on behalf of your own app using its token.

$opt_fields = array( "token" => 'Your-app-token-goes-here', "user" => $channel->channel_string, "title" => $notification->title, "message" => $notification->message, );

$meta = unserialize($channel->channel_meta); if (array_key_exists('device', $meta )) { $opt_fields['device'] = $meta['device']; } if (array_key_exists('priority', $meta)) { $opt_fields['priority'] = $meta['priority']; }

curl_setopt_array($ch = curl_init(), array( CURLOPT_URL => "https://api.pushover.net/1/messages.json", CURLOPT_POSTFIELDS => $opt_fields, ) );

curl_exec($ch); curl_close($ch);

You'll need to get their user id (long un-readable string) and use it as user. They can optionally choose a device and you set it as device.

For more details: https://pushover.net/api#messages

Pushover doesn't send emails. Maybe IFTT is something for you. Or Tasker.

Those are programming / automatization tools.

IFTT works with pushover: https://ifttt.com/pushover

Tasker: https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm, Tasker you can program to do almost anything on Android. Can have a deep learning curve.

Maybe start with IFTT