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 emergency level notifications?
If you are willing to use a custom driver, please see the post below. This is the same driver that the official driver is based on (possibly identical). I have submitted a request to have this custom driver updated for Emergency Notifications. Keep an eye on that thread.
I'm not sure if the Hubitat team plan to update this driver with small modifications as it is more of an interim solution until they get their mobile app in production. I'll let @bravenel speak to that.
@bravenel, we made the change in the custom driver already.
[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 achknowledged (in seconds with a maximum of 10800)
I attempted to limit the preference inputs for retry and expire using “range” but it didn’t seem to limit the options so I just included that info in the description text. Please let me know the correct syntax for range limits if supported.
Looking in the Pushover App, I can see the area for Default and for High Priority but not Emergency. To my mind, [H] in my message would map to High Priority sound; [N] would map to default sound. Does [L} map to NO sound? and lastly, what does [E] map to?
Or am I completely off and missing a key piece...
I am not sure what features the Hubitat built-in Pushover driver currently supports. However, if you need some additional features, please take a look at my community version of the same driver.
