# \[APP\]\[Pro\]\[SHS\] Device Watchdog - Battery, connectivity & staleness monitoring for all your devices

**URL:** <https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537>\
**Category:** Apps\
**Created:** [July 24, 2026, 10:54am UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537 "2026-07-24T10:54:46Z")\
**Posts on this page:** 1\
**Showing post:** 31

<div class="post-metadata">

**Author:** ![Rick\_D](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rick_d/32/143953_2.png) [@Rick\_D](https://community.homey.app/u/Rick_D)\
**Post date:** [July 30, 2026, 1:20pm UTC](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537/31 "2026-07-30T13:20:31Z")

</div>

Quick follow-up on the technical side, for anyone curious: I looked into whether detection could be improved further here, and it looks like this is currently a genuine platform limitation, not something fixable app-side. Homey’s Zigbee coordinator does track a proper `node.lastSeen` internally (every received frame, not just capability changes), but it’s not exposed through the standard app SDK - only through elevated/manager-level access that a monitoring app like this shouldn’t really be requesting. There’s an open community idea asking for exactly this ([expose node.lastSeen in the Zigbee SDK](https://community.homey.app/t/idea-expose-node-lastseen-in-the-zigbee-sdk/155238)) - no official response from Athom yet. If that ever lands, I’ll revisit this.

---

_[View the full topic](https://community.homey.app/t/app-pro-shs-device-watchdog-battery-connectivity-staleness-monitoring-for-all-your-devices/157537)._