Pushover Notifications Driver [Slightly Enhanced]

[moh]

Hi Steve,
thank you for your help but sorry that I am still a little confused.

In the screenshot of my Global Variables above, what is the exact syntax I would use to get the Value for the GV Object-IPC Backyard 4K into my Pushover notification (in the current state [person])?

I have tried %Object-IPC Backyard 4K%
I have tried %variable-Object-IPC Backyard 4K%
I have tried %global-variable-Object-IPC Backyard 4K%
I have tried %variable-name%

As well as other variations.

I can get the triggered motion device (IPC Backyard 4K) to show in my notification by using %device% as well as the date and time triggered by using %date% %time%, but I cannot get the triggering Object into the notification. I am obviously missing something here that I can’t get my head around, lol. Sorry for the newbie questions. Thanks for any help.

[ogiewon]

I would remove the spaces and "-" from global variable names to see if that helps. Keep variable names simple text for best results.

[moh]

Ogiewon,
Thanks for your quick response. I will try this later after work.

[guarddog13]

That would be my suggestion, as well. HE uses %% for variable names. When you add spaces to an HTML link it adds %% instead of spaces. I'm assuming that this is just a Get link sent to Pushover. Adding any special characters in a link will always throw it off. That was my experience when I used to use Autonotification instead of Pushover. I assume this works similar to Autonotification, albeit a bit more user friendly, which is why I enjoy it quite a bit.

Any time I make a variable I never add special characters or spaces.

[moh]

Hi Ogiewon and Guarddog,
Thank you both for all your help. Getting rid of the spaces did the trick! Global variable strings now show up properly in notifications! Appreciate the two of you taking the time to help out.

[mbrown1880]

Sorry, this is probably a stupid question, but I can't find how to bring up this Pushover Device Configuration screen. Loaded the Device Code and looked in RM. I'm new to Hubitate so I'm a bit confused, any help is appreciated. thx.

[ogiewon]

Go into the Devices section of your hub, Click "Add Device" in the top right corner, then click "Virtual Device". Select the Pushover driver type, and give the new device a name, and then click Save Device. Now you'll have a new Pushover device in your list of devices. You can then configure this device's settings with your Pushover account info.

P.S. Welcome to Hubitat!

Also, there is a Pushover driver built into the hub already, so you don't have to use this community developed version - unless you want some of its enhanced features.

[rlithgow1]

@ogiewon

Also, there is a Pushover driver built into the hub already, so you don't have to use this community developed version - unless you want some of its enhanced features.

I thought they moved the enhanced features to the built in version?

[ogiewon]

@rlithgow1

I thought they moved the enhanced features to the built in version?

To the best of my knowledge, the first post is still accurate with respect to the built-in version's features.

Specifically

---

@ogiewon

Note: The following features are not included in Hubitat’s built-in driver.

Recent Additions - September 23, 2020

Much thanks to @TMLeafs for the following 3 additions

1. Added custom title in message by encasing it in ^^

• example ^This is my title^

2. Added choose sound from message by encasing it in ##

• example #bike#

3. Added Default title in preferences

An example message:

"[H]^My Title^ My Message #bike#"

The title & sound can go anywhere and in any order in the message except before priority if it used

And, per a request from @jpoeppelman1, I have added the ability to use HTML formatted messaging by adding [HTML] in the message, which can go anywhere and in any order in the message except before priority if it used.

An few example messages (remove the double quotes):

"[M][HTML]This is a <b>BOLD</b> example"
"[HTML]<a href="http://example.com/">word</a>"

Recent Addition - September 27, 2020

Much thanks to @s1godfrey for the following addition

1. Added ability to send the Pushover Device Name in message by encasing it in **

• example My-iPhone
• or, simply adding "**" to the message will send to all Pushover Devices on the account.

An example message:

"[L]*My-iPhone* My Message" - sends only to "My-iPhone"
"[L]** My Broadcast Message" - sends to all registered Pushover devices on the account

See Pushover: API for more details around the html formatting.

If this has changed, please let me know and I'll be happy to update the first post.

[rlithgow1]

@ogiewon

If this has changed, please let me know and I'll be happy to update the first post.

I must have misread all that time ago when I was installing Pushover, Danke!

[rlithgow1]

Really dumb question, what does the [H] represent in the example? Is that for priority?

[Inge_Jones]

Yep

[ogiewon]

@rlithgow1

what does the [H] represent in the example? Is that for priority?

Yes, as @Inge_Jones mentioned above.

Here are the details

@ogiewon

Documentation of available prefix options thanks to @stephack :

1. You can now set the default priority of your Pushover Notification in the preferences of the driver. With the Pushover app you can set up different notification sounds and visuals based on the priority of the message. You can create a separate virtual device for each priority level and route notifications accordingly...
   OR
2. If you are like me and don't want to dig through a stack of virtual devices...you can now also add a prefix to the message you send that would override the default priority to one of your choosing.

Prefixes
[L] - Low
[N] - Normal
[H] - High

E.g.. Message "[H]This is a test" will send "This is a test" with High Priority to your mobile app.

[E] prefix is now used for emergency notifications and requires the following parameters
retry - how often to resend notification until it is acknowledged (in seconds with a minimum of 30 seconds)
expire - timeout for resending notifications if they are never acknowledged (in seconds with a maximum of 10800)

[tsaaek]

Great driver! Thank you!

I added some rows in the driver code to be able to change the supplementary URL and url title with prefixes.

    if((matcher = message =~ /\§(.*?)\§/)){               
    message = message.minus("§${matcher[0][1]}§")      
    message = message.trim() //trim any whitespace
    customUrl = matcher[0][1]

}
if(customUrl){ url = customUrl}


if((matcher = message =~ /\¤(.*?)\¤/)){               
    message = message.minus("¤${matcher[0][1]}¤")      
    message = message.trim() //trim any whitespace
    customUrlTitle = matcher[0][1]   
}
if(customUrlTitle){ urlTitle = customUrlTitle}

Example:
"§http://example.com§ ¤Example¤"

I also found a way to trigger tasks in tasker via the supplementary url.

tasker://assistantactions?task=TaskNameHere&par1=optional par1 value&par2=optional value

r/tasker - [How-to] Run Tasks Via URL

[ogiewon]

@tsaaek

Great driver! Thank you!

I added some rows in the driver code to be able to change the supplementary URL and url title with prefixes.

Thank you @tsaaek! I have updated my GitHub repo with your changes.

[LibraSun]

SOLVED: Found it! After (much) more reading on the Forum, I came across mention of Pushover being a virtual device on HE. So, I ventured into Devices, this time doing a Create New... ... and lo and behold, I find that "Pushover driver" is indeed listed there among the System drivers. Well hidden, yes, but it exists! Will fiddle now.

---

I originally asked:

Jump forward to late 2021, and I'm looking for any mention at all of Pushover (in Apps or Devices or Hubitat Package Manager or Settings) on my C-7, and coming up empty-handed.

Have things reverted to needing this Pushover Notifications Driver if you want to send message out to it from your HE? Or is current best practice to use RM to send out HTTP Requests using well-formed URLs against the Pushover API?

I mean, I can roll my own and don't mind doing so, but was secretly hoping that Pushover had (as promised in the OP) become a stock function. I just can't find it anywhere.

Thanks for guidance!

[ogiewon]

Just use the built-in Pushover driver, to create a virtual device. Populate its settings and verify you can send a push notification via its device details page. Once that’s working, use any App in Hubitat to send a notification. There is no need to develop any code whatsoever to achieve this. When you choose a ‘notification’ action in RM, Notifications, etc., you’ll be able to choose the virtual Pushover device you’ve created.

[mebejedi]

@ogiewon

To enable HTML formatting, include an html parameter set to 1 . The normal message content in your message parameter will then be displayed as HTML.

Could you explain where the HTML parameter is set? I've got Pushover working in WC, but don't understand this part.

[EDIT] Nvrmnd....I updated the driver and it works.

[nfd0800]

I just established my Pushover account last night and have it basically working. I am overwhelmed with the plethora of information on this feature and have done a lot of reading, but much of it dates back to 2018, so I am having trouble sorting out what is really current info. Specifically, can you verify whether I need to update the Pushover driver from what is now included in the latest Hubitat firmware (2.3.0.124) in order to play a custom sound, for instance? I have everything configured, have uploaded the mp3, but yet this still results in a stock sound on my iPhone. This is a clip from what I built in Notifications. I get the iPhone notification but the mp3 does not play

:

[nfd0800]

Disregard. I updated the driver and it is working now. Sorry to bother.