ok, thanks.
I use Zooz Zen15s to monitor my Sump pump(s). The Sump pulls a fairly predictable peak power (800 Watts), and by watching the peak power, I can Count events (pumps). You could then set a watch on the number of occurences in a 24 hour period.
Fairly simple to do in RM. I recently started dumping the events to files with the idea of playing around with Node-Red to do some tracking over time.
S
1 Like
How can I get this app to check every hour for the condition instead of a specific time or when a button is pressed?
First, I'm not sure I would recommend that -- what is the reason for such frequency? If you are dealing with a device or network problem, addressing that first would be better. Maybe this app isn't the best approach.
But, to directly answer the question: this is possible. As you are aware, the app lets you "trigger" a notification with button presses. It can also do so with switches (either in addition to or instead of the scheduled time; FWIW, I use mine once a day and am even thinking of adding less frequent options). Therefore, all you need to do is create such a virtual device and couple it with a rule or other automation that performs the necessary command (e.g., push button 1 or turn on) at the desired frequency.
3 Likes
I believe this occurred when I ran a Device Activity Report this morning:
Debug logging is set to off:
The log message is accurate and also has the solution. If you don't use the LAN or cloud report pages (the links that open "outside" the app, not the in-app report), you can ignore it. If to want to use them, you'll need to enable Oauth as described in the installation/upgrade instructions and as is also documented in general here:
https://docs2.hubitat.com/en/user-interface/developer/apps-code#enabling-oauth
Also, FWIW, those log entries could only occur from opening the app and hitting "Done," not from having run a notification/report.
@bertabcd1234 hello! Huge thanks for this app!
I noticed that some of my devices have not only the online and offline statuses, but also the unknown status. Could the app be configured to check not the offline status, but any status is not equal to the online? Because now devices with the unknown status are not included in the report.
It look like this in the device's logs:
| Id: | 849 |
|---|---|
| Date/Time: | 9/06/2024 11:00:00.363 pm |
| Name: | healthStatus |
| Description: | Health status is unknown |
| State change: | true |
| Physical: | true |
| Digital: | false |
| Value: | unknown |
| Unit: | |
| Source: | DEVICE |
| Type: | physical |
| Device id: | 34 |
| Device name: | Leakage Sensor Cabinet |
| Produced by: | Leakage Sensor Cabinet |
| Triggered apps: |
Hi @sinkler ,
Most of the custom drivers that use healthStatus attribute will send ‘unknown’ value when there is nothing received from the device during the initial pairing to the Hubitat hub. I.e. ‘unknown’ usually means a Zigbee pairing problem…
It may be a good idea to post also in custom driver dedicated thread in this forum to get help on the problem (if there is a problem wit the device).
