@dennypage Look under his toupe
Yes, here. It's a native Pushover feature. OK, you guys were right, Pushover is kinda cool - #28 by mebejedi
Yes, I am aware that Pushover natively supports priorities by use of the priority
field. However I haven't found any native Pushover documentation that references using [H]
or [E]
leading the body of the message field to set priority.
curl -s -o /dev/null \
--form-string "token=${APP_TOKEN}" \
--form-string "user=${USER_KEY}" \
--form-string "priority=${priority}" \
--form-string "message=${message}" \
https://api.pushover.net/1/messages.json
LOL...yeah, I know it sounds bizarre, but my wife has a "thing" for widgets. They are her favorite part of the Android OS, and when I first showed them to her many years ago her eyes lit up. She has widgets all over her home screens which makes me pretty confident she will like/use the Pushover widget. Or at least not hate it.
Mildly related to Pushover. If you have a NVR Security system at home, you can send email notifications to Pushover, and then to your phone, which can then be pushed to your smart watch. Others have gotten the snapshots to show up on their watches. I can't get the pic to show on my watch, but the smartphone shows the image. It saves the time opening up my NVR app.
It looks like you can create more than one email alias, so you can create one for your wife and have specific notifications intended only for her. (Or just pay five bucks for her own account)
You can change all this:
To this:
And you will not find any official Pushover documentation to that effect. When we created the original Pushover Driver for Hubitat, we had to come up with ways to utilize the features of the Pushover API, while staying within the constraints of the Hubitat Notification Standard Capability. Thus, we embedded features like the message priority with brackets, which the driver then strips off before making the proper Pushover API call.
You can read through the history of the Pushover community driver development by reading the following thread. The first post also explains the use of all of the features that have been implemented. Note: Some features require the use of the Community version of the driver, as the community has continued to add features even after Hubitat took their snapshot of the code to include in the Hubitat Platform.
This is what I was planning, since the price is right might as well get her her own account.
"Happy birthday, honey, I know it's just what you always wanted!!!"
And you will be honoring the TOS. You are a scholar and a gentleman.
Thank you for the education Dan. Makes sense.
I was going to ask you...your OP in the Pushover driver topic includes two differing statements:
Near the start:
Lower down just above the link to the GitHub:
And here in this topic, you just said:
So it seems like the first statement in the Pushover topic is no longer correct? Can you confirm if the community driver is currently the same as the built-in driver? Either way the Pushover driver topic looks like it needs an update to reconcile the two differing statements about the built-in vs. community driver in it.
I have the apps installed on my wife and daughter's phones. I disabled notifications and just use it as a present sensor. They never use the app and don't notice the app is even there. But if there's anything specific that needs their attention, then the extremely rare time a text can be sent to them.
Has using Pushover as a presence sensor ever been talked about?
How would that work?
Horses for courses, sounds like that works well for you.
I use Owntracks for presence, more options including live map of location, and movement w/history. Wife has actually already given approval for me to add the Owntracks app to her phone. The angle that worked - Safety! (Hit her where she lives.) "Honey, what if an earthquake or other significant event happens when we're not together? It could be critical for us to know where the other is, and we may not be able to connect over cellular lines due to call/text congestion!" My wife is a natural disaster-phobe, so she ate it up!
I think he's referring to using the HE mobile app as the presence sensor, not the Pushover mobile app...AFAIK there is not capability in the Pushover to work as a presence sensor, and I've never seen any talk of that.
The first statement is still correct, to the best of my knowledge.
To use the advanced features that were added after Hubitat took their snapshot, you will need to use the Community driver.
I can see where the wording in the post might lead to some confusion. Iβll look into tweaking it for clarity.
Yes, I think that's the issue. The wording did lead to some confusion in my case, though I am known to fall into that state (confusion) quite easily.
Oh and thank you for the driver and enhanced features, very nice.
If this is the question above, the built-in driver does offer priority with the same "tags" in the message. Mapping these to the numeric Pushover priority levels, it's:
[L] = -1
[N] = 0
[H] = 1
[E] = 2
I assume this is the same as the community driver, and the "tag" must be at the beginning of the notification text (e.g., not even a space before, etc.).
Community driver adds
[S] for -2 priority.