Location Awareness

**Quick judgment:** A well-designed, feature-rich location and geofencing skill suited to technically comfortable users who already run (or are willing to run) a self-hosted location backend. Excellent for personal automation and ETA/reminder workflows, but requires nontrivial setup and carries inherent location-privacy risks. **Strengths & scenarios where it shines** - You already use **Home Assistant, OwnTracks, GPSLogger, or a custom HTTP endpoint** and want OpenClaw to query your location, ETAs, and movement history. - You want **location-based reminders and geofence rules** ("remind me to do X when I arrive at Y", time-at-work stats, last visit to place X). - You prefer **self-hosted, privacy-conscious tracking** over third-party cloud services and are comfortable editing JSON config files and environment variables. - You like **simple, predictable natural-language → command mappings** and terse, automation-friendly responses, including optional `--json` output for scripting. **Key risks & limitations** - **Privacy and security:** Even though the design is self-hosted, all location data are highly sensitive. Misconfigured servers, weak tokens, or overly permissive notification channels (e.g., sending detailed locations over unencrypted or shared channels) can leak real-time and historical location information. - **Setup complexity:** Correctly configuring providers (URLs, tokens, entity IDs, files) and geofence JSON requires technical skill. Non-technical users may struggle with initial integration and debugging. - **External dependency reliability:** Functionality depends heavily on the chosen backend (Home Assistant/OwnTracks/HTTP/GPSLogger) and on external services like OpenStreetMap for geocoding. Network or backend issues will directly impact reliability and latency. - **No built-in policy layer:** The skill assumes that any caller allowed to use it can query detailed location, history, and POI data. Additional access control or redaction policies need to be enforced at the OpenClaw or environment level if required. **Overall:** Strong choice for power users who control their infrastructure and understand the privacy implications. Not ideal for users wanting a plug-and-play, zero-config location solution or for environments where fine-grained access control over location data is mandatory without extra safeguards.