We’ve released version 1.4 of our Android and iOS apps today, which now support setting and receiving messages during “quiet hours”.
Quiet hours are periods of time during which Pushover notifications should not generate sounds or vibration, but should still notify your device. On Android, notifications will still appear in the notification bar, and on iOS, the Pushover app icon will display a badge with the number of unread notifications.
Messages sent through our API with the “priority” flag set to 1 will override quiet hours and always generate sounds. This is useful for network monitors and other high priority applications that always need to generate notifications.
You can adjust your quiet hours from the Pushover website, or through the Settings in our apps. Quiet hours affect all devices on your account.
In addition to supporting quiet hours, our Android app now uses the notification enhancements that came with Android 4.1 (Jelly Bean), such as larger text areas, per-application icons, and a button that will open a message’s supplementary URL (if supplied) right from the notification.
Pushover 1.4 for iOS is available in the App Store now, and Pushover 1.4.1 for Android is available on the Google Play Market.
IFTTT is a web service that lets you create powerful connections with one simple statement:
Using IFTTT’s library of triggers (the “this” part), you can create simple-but-powerful recipes to automatically perform actions any time certain things happen. For instance, every time you post a photo to Instagram, IFTTT can automatically save it to your Dropbox.
Earlier this week, IFTTT announced a new Pushover channel, enabling you to easily send Pushover notifications when your recipes trigger. Users have already created hundreds of recipes using the power of Pushover’s instant notifications, such as:
- If the front door opens, send a Pushover notification
- Notify me when I’m tagged in a Facebook picture
- Send me a high-priority notification when new e-mails arrive from VIPs
- Get notified of new Gold medals in the Olympic Games
We’re excited to see these new creative uses for Pushover, and we’d like to welcome all of our new users from IFTTT. If you’ve never used IFTTT before, signup and start making recipes. If you’re new to Pushover, check out some of the other applications that are Pushover enabled, or integrate it into your own application.
(Note: for most of our users, this change will have no effect and will not require any changes on your part.)
Our previous SSL certificate issuer for api.pushover.net and our pushover.net website is currently experiencing a DDoS attack on their OCSP servers, which browsers and other SSL clients use to check whether a given certificate has been revoked.
The result of that attack is that when a web browser or other SSL client with OCSP checking enabled tries to establish an SSL connection to api.pushover.net, it will stall for about 10 seconds while waiting to get a response from the OCSP server being attacked.
We’ve switched to a new SSL certificate provider with more robust OCSP servers, as well as registered new certificates valid for 2 years.
For most of our users, this change will not require any intervention and will not be noticeable. Our Android and iOS clients are working fine with the new certificate and most HTTP/SSL libraries/frameworks sending notifications through our API will not need to be notified of the new SSL certificate. However, some users using Java or other environments where a manual key store is needed may need to adapt to the new certificate provider.
We would have liked to have been able to give more notice before this change but due to the problems that the DDoS is causing on the SSL provider, we had to act quickly.
We’re happy to announce that all Pushover applications now have realtime API usage statistics, viewable for the past 45 days.
When viewing your registered application’s details, you will now see an interactive graph showing how many messages were sent each day, along with the current month’s total.
You can see usage statistics for your applications now by visiting the Applications & Plugins page while logged in.
makes it easy to integrate notifications into a wide variety of applications and services. Today we’re announcing an e-mail gateway that makes it possible to receive Pushover notifications from devices and services where API integration is not possible, such as with embedded devices, SAN servers, routers, and websites.
Our new e-mail gateway provides every Pushover user with an e-mail address that will turn any e-mails received into Pushover notifications. To get started, just send an e-mail to Your-Pushover-User-Key@api.pushover.net. By default, all notifications will be sent to all active devices on your account, just like other Pushover notifications. To have messages sent to only one particular device, use the e-mail address Your-Pushover-User-Key+Device-Name@api.pushover.net.
For example, if your user key were abcdefg12345 and you wanted to send a notification to your device iPhone, you would use the e-mail address abcdefg12345+iPhone@api.pushover.net.
HTML e-mails received by our gateway will be converted into plain-text with URLs preserved to enable them to be tapped on in the iOS and Android Pushover clients. Just like other Pushover notifications, e-mail notifications are limited to 512 characters and long e-mails will be truncated.
A new feature has been added to our API and is now supported by version 1.3 of our Android and iOS clients: supplemental URLs.
As before, all URLs included in the Pushover message body will be automatically turned into tappable links when viewed on our device clients. Sometimes, however, it is useful to include a URL that is not the actual content of the message, may be too long, or may use a custom URL scheme that is not recognized.
For example, an application using Pushover to send Twitter messages to devices may include a supplemental URL of “twitter://direct_message link?screen_name=someuser” and a URL title of “Reply to @someuser”. When the message is expanded in the Pushover client, the user will be given the option of opening the supplemental URL, which in this case would launch a Twitter client installed on the device and send a direct message to “@someuser”.
For more information on using this new feature, check out our API documentation.
Please note that supplemental URLs require version 1.3 of our iOS and Android clients, both released today.
Github Service Hook
The first plugin is a Github service hook that sends a Pushover notification each time a commit is made to your git repositories. This plugin has been integrated into Github’s website so there’s nothing to install other than adding your Pushover user key.
- To get started, view one of your repositories on Github. Click the Admin button in the upper right corner.
- Next, click “Service Hooks”.
- Scroll down and select Pushover.
- Finally, enter your user key (available by logging into the Pushover website) and an optional device name (to restrict notifications to a single device on your account). Click “Update Settings” and you should start receiving notifications whenever a commit is made to that repository.
Next up is a plugin for the Weechat IRC client, written by Pushover user James Turnbull. This plugin forwards private messages and highlights to your Pushover devices. To install, see James’ Github repo.
Puppet Report Processor
And finally, another plugin by Pushover user James Turnbull, a report processor for the Puppet automation tool. See the puppet-pushover repo for usage information.
Pushover has an official plugin for Adium that lets you forward instant messages to your mobile devices that were received on your computer while you are away.
To get started, install the Adium plugin from the Adium Xtras site. Once the plugin is installed, open the Adium preferences and click on the Events tab.
Double click on “Message Received” to expand it and then click the “+” button at the bottom of the preferences window. If the Pushover plugin was correctly installed, you’ll see a “Forward to Pushover” entry in the “Action” drop down.
Enter your Pushover user key (viewable at pushover.net or from the Settings of the client on your phone) and optional device name.
To receive all messages while your account is away, check the “Away” option. If you are frequently away but only want to receive messages while you’re actually away from your computer and the screen saver has started, check the “Screen is locked” option.
You can apply this action to other types of events, such as only when certain contacts send messages.
Pushover makes it easy to send push notifications from your servers, apps, websites, and anything else.
Clients are now available for Android and iOS in the Android Market and App Store.