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) - no official response from Athom yet. If that ever lands, I’ll revisit this.
