1.3.1 is out. Fixes the frozen-member issue @halfrican.ak reported earlier in this thread, thanks again for the detailed info
What was happening: if a member's device failed to get created (most commonly a leftover device from a previous install still holding that member's device ID), that member would silently stop updating on every poll afterward — with no other members affected, and no useful error explaining why. Delete-and-re-add worked as a manual fix, but it shouldn't have needed to be manual.
1.3.1 fixes both halves: a failure now affects only that one member, not the whole poll, and the log message names the actual cause (a device ID conflict) instead of pointing at the wrong thing.
Update via HPM: Repair → PositionGuard. Manual installs: driver first, then app. README now has the exact steps under "Updating manually."
(Separate from @halfrican.ak's other post above about the MissingMethodException. That one's an app/driver version mismatch, already resolved for that specific case, and unrelated to this fix.)
Updated without any issues, will continue to monitor. Thanks for your attention to issues that are found 
1.4.0 is out. Two new things and a behavior change worth checking your rules against.
Member counts per area. Each area in a selected group now gets its own device with three attributes: memberCount, staleCount (counted from a position that's gone quiet), and freshCount (confirmed only). Family: Home count → memberCount = 0 is a one-attribute "everyone's out" trigger, no per-member logic. The device carries a number, never who or where.
It works for any group, not just family. A friends group with the pub, downtown or the sports court as an area gives you a live count of who's there. Members of a friends group only see each other inside the group's own areas, and any member can hide themselves from a specific area, so it stays opt-in per person.
Stale now reads unknown. A phone that stopped reporting used to flip between stale and its real status as it went quiet and woke. It now reports unknown, and two new attributes, positionFresh and positionAgeSeconds, let a rule gate on freshness directly. outsideUsualArea is unchanged, still strictly true/false. If a rule compares safetyStatus to a specific value, check it against the new behavior.
Presence area. Each member device has a Presence area preference, defaulting to an area named "Home." If yours is called something else, presence stays not present until you set it, currentArea is right regardless. Next release will pick this up automatically; for now it's one preference per device.
Update via HPM → Repair → PositionGuard, which picks up the app and both drivers together.