Pushover Notifications Driver [Slightly Enhanced]

[bgav]

Quick question. I'm a new Hubitat owner coming from an ISY994i w/Insteon and a Revolv hub prior to that.

I was able to add the driver code above. What do I need to do to add my API and user key? I can't for the life of me find where to do it. Thanks! There's a bit of a learning curve coming from the ISY994i.

I'm glad to see Pushover support in Hubitat as I used it extensively in my ISY994i setup.

[ogiewon]

@bgav

I was able to add the driver code above.

Welcome! First thing... There is no real reason to add the Pushover Driver code above to your Hubitat Hub. The Hubitat team added this driver to the Hubitat Firmware, so it is already included as a native device driver.

@bgav

What do I need to do to add my API and user key? I can't for the life of me find where to do it.

In your Hubitat Hub's web interface, select Devices. In that page, select Add Virtual Device. You will be presented with a window where you can select a name, label, and network id. You can simply type in "Pushover" for each of these. (Note, if you add more than one device, the network ID needs to be unique!) Also select the Pushover Device Driver from the list. Then click SAVE.

Now you can edit the Device's user preferences and enter in your Pushover keys. Once you enter those and click save, additional preferences will be shown that allow you to customize the device.

[marktheknife]

@ogiewon any reason to think it’ll cause a problem if I switch from the custom driver to the built-in one?

When I first installed it, I didn’t notice that they had already added the driver to the firmware, so I used the custom one.

[ogiewon]

Should not be a problem. I believe they are the same. On my production hub, I am still using the custom one that @stephack and I wrote. On my development hub I am using the native version. They appear identical to me.

[bgav]

Thanks for the prompt reply @ogiewon I'll give that a try when I get home!

[stephack]

@marktheknife

When I first installed it, I didn’t notice that they had already added the driver to the firmware, so I used the custom one

The only difference "may be" support for emergency notifications with the [E] prefix that was added back in April. I alerted @bravenel of the change so it might have been incorporated in the official driver since then.

See:

Request: Pushover Emergency Priority

I’m using Pushover since the last update (thanks for the tip!), and I like it! The ability to specify L, M or H for each message is great, and a nice way to differentiate between different notifications. I noticed that in the API description (Pushover: API) additional levels are described, among them “Emergency”. To me it sounds perfect for alarms, leaks and that kind of more serious “threats”, as it continues to notify until user action is taken. So, TL;DR. Would it be possible to add [E] for…

[marktheknife]

@stephack

The only difference "may be" support for emergency notifications with the [E] prefix that was added back in April

Thanks, that was gonna be my next question, actually .

I kinda like the persistent notification every 30 seconds until acknowledged, in case of a true emergency.

[bgav]

@ogiewon up & running with Pushover, thanks again!

[toby]

@ogiewon

This allows Rule Machine to 'Speak' a notification via this Pushover Driver

I might be missing something but how do I get PushOver to actually speak the message? Right now I'm just getting double push notifications but no TTS

[ogiewon]

@toby

I might be missing something but how do I get PushOver to actually speak the message? Right now I'm just getting double push notifications but no TTS

'Speak' was in quotations for a reason... Pushover cannot audibly speak anything. Pushover provides push notifications only.

Some applications support the 'Speech Synthesis' Capability, but not the 'Notifications' Capability. Since both capabilities simply expect text to be passed to the respective commands, it was trivial to allow the Pushover Driver to implement both commands.

This way, if you have an App that only supports one or the other capability, your Pushover device will appear as a valid device. But the end result will still just be a Pushover Push Notification on your phone or tablet.

Hope that helps to explain it.

I have updated the original post to hopefully make this clearer for others as well.

[stephack]

Just an FYI for everyone using the custom driver.....

The bad news:
The latest firmware 1.1.2 breaks this driver because of changes to httpPost.

The good news:
This custom driver is no longer needed because this same update added [E] emergency support that makes it essentially the same.

Please update all your pushover devices to use the built in driver or you won't get any notifications

[tsviper]

I have also notice that we are unable to select a particular device in the "Device Name" drop down box since the update.

[marktheknife]

@tsviper

I have also notice that we are unable to select a particular device in the "Device Name" drop down box since the update.

I just changed from the custom to stock driver after updating hub firmware, and I have noticed the same thing.

So at this time, I can’t tailor my push notifications because the two pushover devices I installed are defaulting to “all.”

[stephack]

Didnt realize that myself. I can update the custom driver with the new httpPost method but let's see if this can be fixed by @mike.maxwell or @bravenel first.

[stephack]

@marktheknife, @tsviper
If you both are comfortable editing the driver code you can do the following:
At line 74 insert the following 2 lines of code

contentType: "application/json",
requestContentType: "application/x-www-form-urlencoded",

So it looks like this

Add the same 2 lines at ~ line 173 so it looks like this

It should work fine until the built in driver is updated.

[tsviper]

Thanks for temporary fix...much appreciated!

[marktheknife]

Thanks, @stephack.

[bravenel]

This will be fixed in the next release.

[ogiewon]

I have added @stephack 's changes to the version in my GitHub repository.

[stephack]

Hot fix that was released today seems to have fixed the issue with the built in driver.