HS3 Pushover Plugin

[Ltek]

@MrHappy
Small / Easy feature request... can you add an option inside the Event Condition to 'disable' that message from sending?

Two reasons I ask for this...

1. While developing my event system, I have used your plugin extensively. Both for long-term use notifications and for troubleshooting-type notifications. I'd like to turn off the later without removing them, in case they are needed later.

2. Since there is no HS3 feature to add Comments to Events (huge gap IMO) your plugin can fill this gap nicely

thank you for considering, and for the REALLY useful plugin.

[mrhappy]

Just tested, looks like it works

Yes it should work, only in three fields IIRC without checking the code, message title, message body and the URL. Supports the HS standard variables and also a couple of custom ones that are detailed in the help file.

[Ltek]

@mrhappy
I didnt see this in the documentation... can we use system variables like $$DSR:<refID>

?

I'd like to have 1 event, per chosen device(s), that will pass the device status text.

thx!

Just tested, looks like it works

[Ltek]

@mrhappy
I didnt see this in the documentation... can we use system variables like $$DSR:<refID>

?

I'd like to have 1 event, per chosen device(s), that will pass the device status text.

thx!

[mrhappy]

I agree with mrhappy - except that having AT&T in the US, I often have phone service and no 3/4g .. yes, cuz AT&T SUX

This plugin REALLY helps those of us moving from Vera because the HS3 notification system is crap. Once you drive a Lexus, you don't want to drive a Chevy kinda thing.

Notifications in Vera were better in every way natively (we could set notifications directly on any Devices, any Scene (event), and with a $5 plugin you could customize the HELLOO out of it.

I had different phone audio notifications for doors opening, house mode setting, occupancy / proximity, motion sensors, etc... and could make the sound different (for EACH notification) based on the House Mode, time of day, etc.

I've found nothing in HS3 that compare and suspect even if you can do the same stuff through hundreds of event - the level of work would be like the difference between walking barefoot in winter, from LA to NYC vs Flying there in a 747. Maybe extending the Pushover script could fill the void?

I made the suggestion when HS3 was coming out that the condition for events could have a place also attached to the event actions (like a nested if..then). This would make things like this somewhat easier, unfortunately without this it becomes a fair bit more difficult to have actions that change say the sound of the message depending on another condition.

You can use the scripting method exposed to write a script that checked a device and sent a message with a different parameter depending on a factor (that option already exists) however you then are reliant on editing the scripts if you need to change the message.