Hi, how can I get the app to stop notifying me of a device that is very much online and sending events to the hub? The device was reconnected two days ago but the app keeps sending notifications of inactivity. I would have thought that once the device started reporting again it would no longer be considered Inactive, or at least provide a way to "reset" it. Snooze seems to just make it notify me over and over again.
Did you just take that screenshot tonight?
The last activity shown in the screenshot was on 3/18.
3 Likes
Adding to this, we'd also need to see your settings for the group that device is a part of and ideally the app as a whole. If you have multiple instances of the app (on the same or different hubs), be sure to check those, too. The app won't send one if it's less than your threshold (though I see now this could be a couple days based on your screenshot, so it's likely it would actually be included...), and a snooze (your device is not snoozed in your screenshot above) would entirely exclude it, so something else must be going on.
Yes you are all correct; I've been looking at date fields all day for work and apparently lost all sense of things. 
My apologies and thank you for your quick responses.
1 Like
Version 3.0 Beta
If anyone wants to test, I've been working on some updates I've been meaning to do for a long time. For version 3.0, I've changed/added:
- Each device group is now a separate child app from the main/parent Device Activity Check 3 app. This means:
- The "In use by" tab for any device makes it easier to see which group(s) a particular device is in rather than just Device Activity Check in general (my primary motivation for adding this)
- There are now two apps, parent and child, to install (but the bundle ZIP -- or eventually HPM -- will handle this for you if you don't manually install)
- Option to use Zigbee and Z-Wave "last message" data instead of device/driver "Last Activity At" data for "Last Activity" at detection, if such data present.
- Not well tested yet (beta, but please let me know!)
- Works only on C-8/C-8 Pro (not sure what happens if you try on older versions, but probably don't try...)
- Considering something similar for Matter, but only online/offline data is provided with no date, and it's not quite as helpful in my experience
- Removed legacy "Presence" option as detection method
- Option to configure additional post-refresh delay before notification (if using refresh, if refresh run)
- Other minor changes, including putting detection type selection above device selection on group pages (child apps now)
Existing installs will continue to function; version 3.0 is new app code (changes like the new child app made automatic migration challenging, so that's not something I'm going to attempt). You can use both alongside each other, temporarily or as long as you want. While only 3.0 will receive development and new features going forward, there is no reason to change/upgrade from 2.x if it is working well for you now.
Installation
Installation is manual only for now (not in HPM).
Link: (deleted, now released; please use production release instead)
(import as bundle to your hub, either via download/import or URL)
Do not overwrite existing app code with new code. Version 3.0 is an entirely new app (or actually two, parent and child).
10 Likes
On the main application page can the members of the device groups be collapsed or even just show the child app / device group names where they could be clicked on to open the child app page?
In V3? Probably. 
V2 didn't work that way and no one asked, so I didn't think to change anything...but I can see where it might take up a lot of space if you don't care for the details!
Yes in V3. Some of my groups are large and then require a lot of scrolling to get to the app details after the groups.
Could the “Post-refresh delay before notification” be a free type field rather than a drop-down? Or have longer times in the drop-down? I have a few devices at the fringe of my mesh that take longer than a min to respond sometimes.
I got the HPM notification that an update was available. I ended up having to completely remove both installs and start from scratch. Thanks for including my asks. Looks good to me.
Sorry, you caught me when I was planning to test that before announcing, but I took so long, you got there first. 
Sounds like it didn't break HPM, so thanks for checking that!
It will install as basically a new app since there is no in-place upgrade from v2 due to the significant changes (from a single app to parent/child apps). For existing beta users, I suspect a Match Up would catch your existing v3 install if you wanted to upgrade that, otherwise most people (who didn't test) should just be in a position where HPM can/will install it like a new app, just like the original beta install did. I know this is a bit unusual.
And for everyone else, I should mention that version 3 is now released with the changes I noted above plus a couple feature requests since then. I'll summarize that and re-iterate the installation instructions here:
Version 3.0
New:
- Each device group is now a separate child app from the main/parent Device Activity Check 3 app. This means:
- The "In use by" tab for any device makes it easier to see which group(s) a particular device is in rather than just Device Activity Check in general (my primary motivation for adding this)
- There are now two apps, parent and child, to install
- Option to use Zigbee and Z-Wave "last message" data instead of device/driver "Last Activity At" data for "Last Activity" at detection, if such data present (C-8 and C-8 Pro only)
- Removed legacy "Presence" option as detection method
- Option to configure additional post-refresh delay before notification (if using refresh, if refresh run)
- Other minor changes, including putting detection type selection above device selection on group pages (child apps now)
Existing installs will continue to function; version 3.0 is new app code. If installing manually, add v3 as new app code; do not overwrite the existing v2 app code if you have the app installed. You can use both alongside each other, temporarily or as long as you want. While only 3.0 will receive development and new features going forward, there is no reason to change/upgrade from 2.x if it is working well for you now.
Installation
Device Activity Check is available in HPM or can be installed manually; find instructions in original post.
8 Likes
I updated via HPM and the new Device Activity Check 3 app was available to be added via "Add User App", leaving my existing setup untouched. Thank you!
2 Likes
I just finished copying my DAC2 groups to DAC3, and when I ran a report nearly every device looking like this:
All of those devices are only in this group (which also has the "Supplant with Zigbee details" checked"):
Ah - the logs show lots of errors of this form:
Thanks! Seems to be something wrong with Zigbee data parsing (I didn't test that well, as I disclaimed for the beta release, but no one complained, so I figured it must have been good ). I'll see if I can figure out what's going on there. In the meantime, that's the only way I've been able to reproduce this, so I suspect it will work as before if you just disable the option.
2 Likes
Yes, turning that off avoided the errors.
Now that I can see the report, under DAC3 I find that checking on or off the Snooze button takes about 4 second (C8 Pro), via 1/2 to 2 second on DAC2.