Awesome. I didn't even think of making another pushover device and setting the default sound to a custom selection.
However, the virtual notifications is a fantastic approach. I could utilize this even further for other needs. Thank you, @jtp10181. 
Yes you can and you get an additional 10k notifications per month … or whatever it is.
I have a separate pushover ID for messages from my edgerouter setup - originally configured while I was debugging my arp notifier but I have left it in place. I was also thinking about setting up separate IDs for each HE.
Luckily I never go over 10k to need another pushover account. JTP is correct that you can have unlimited devices in HE under 1 pushover account. I went with the route of creating another pushover virtual device under my original account, specifically for this report to have custom notification sound. I tried virtual notification driver to push the report to an RM rule with custom sound, but it added html code from that driver to the pushover message that I didn't want to see. It also seemed like another rule that doesn't need to be ran to achieve the same results once the first report triggers.
1 Like
Yeah I don’t even hit 1k in a month myself but when I was debugging my arp driver I hit 1k in a few days. It was also nice to separate the traffic in the pushover interface.
I have three HEs that all use the same pushover key so I have to send a hub identifier with certain messages. I just thought individual keys would make it simpler.
Hi,
I would like to trigger an event based on the online-offline status of a wifi device. I only have status, not capability, so I cannot use Rule manager or webcore without checking the status every hours or so. I would like to minitor real time and update a variable or a switch, anything that can help trigger my webcore piston as soon as my device turn online. Is there something this app can do?
Thanks!
No.
This app allows you to
I still think it would ultimately do what you are looking for, just not in the exact way that you are wanting (which is normally unreliable, though I am not familiar with your specific device).
1 Like
All,
I've released version 2.3 with the following changes:
- Added search to device list for groups (thanks to @jtp10181 for suggesting this)
- Added LAN and cloud report page options mentioned above, technically added in v2.2 that was never put in HPM, so it may be new to lots of people. Using these options requires OAuth. See the ReadMe in GitHub if you are not sure how to enable this, or you may keep using the app as-is without doing so.
8 Likes
In the notification is there any way to separate out/group the battery percentages from the inactivity in the list? Thanks.
In the same instance,no; you can, however, create as many as you want.
1 Like
I have two separate groups already. One for battery percentage and another for inactivity. Can I send two separate notifications at different times to separate them from each other?
Sorry for any confusion; I meant separate app instances, not groups. This is not possible within the same app instance. However, you can install multiple instances of the app, each with entirely different configuration, which may suit your needs
2 Likes
Separate app instances will work for my use case. Thank you for the clarification.
Hi,
I've found this thread from searching on "lastActivityTime". I recently ran into an issue with a zigbee contact switch using a driver someone contributed "Xiaomi Aqara Mijia Sensors and Switches".
TLDR: it has a "presence" check that runs every N hours, and this was fooling my app into thinking the device (with dead batter) was still having daily activity
Is there a better field to use for checking the last time communication came from the battery powered device?
Also, apologies if this app here already does this, I looked at the source for this app here and saw it using
dev.getLastActivity()?.getTime()
I'm using
it.device.lastActivityTime.getTime()
which looks like the same thing?
Here was the log that fooled me:
And here is the device option for "presence" check
If this driver is by an author who is no longer maintaining their drivers (and was well known for using this attribute for that purpose), I'd suggest moving to a different driver if you can.
But either way, this app can work. You, of course, can't use the "Last Activity At"-based detection method, but you can use the "presence attribute" option for that group instead. (Each group has options for how you want to monitor the devices.)
I use the device activity checker for a lot of devices but for devices like the aqara that have a presence in the driver, I simply use the notifier app to let me know if a sensor goes “not present”.
Thanks, makes sense. I decided to just turn off this "presence" option in the device (as seen in the graphic actually) and then I can use lastActivityAt again.
Actually in the end I gave up on this zigbee door contact as it's just a very small battery and went with a zwave contact sensor instead.
Would it be easy to add an option to turn on or off a device within a group when a notification is sent out? I would like to use a device to indicate when batteries are low or devices haven't respond to display on my dashboard. Thanks.
Not too hard -- I've thought about this before -- but there are some issues/questions surrounding it that make it more complex than it might initially seem be:
- like its name, the app just "checks" things on your schedule but doesn't "monitor" anything on its own, so a switch being on or off doesn't necessarily tell you anything about right now (though I certainly understand how it might be useful to some extent)
- what turns the switch back off? (the next time there could be a notification but wasn't? should previewing/manually viewing the current report page also do either of these things?)
But I'm happy to try something if anyone finds it useful -- just not sure what people are expecting for any of the above.
All good questions. Here is how I would envision it works:
For each group you have the option of specifying a virtual switch, or the app creates a virtual switch. The app checks the group as it does now at the specified time. If the group triggers the alert then it turns the switch on. The next time the app checks, if there is no trigger event then it turns the switch off.
Since it is a virtual switch - if I resolve the condition I can easily turn the switch off manually before it checks again if needed. For example - replacing batteries.
One switch per group vs. one for the app would make sense. This would provide the ability to have a switch alerting to battery conditions, no response to activity check, etc.
1 Like
An added bonus would be to add a text field to the virtual device to store the report. Then when the device is triggered the text field could be used to display the report to indicate which device is the problem on touchscreens.
1 Like
