location-awarenessLocation awareness via privacy-friendly GPS tracking (Home Assistant, OwnTracks, GPS Logger). Set location-based reminders and ask about movement history, travel time, and nearby POIs.
Install via ClawdBot CLI:
clawdbot install Hegghammer/location-awarenessRequires:
This skill provides commands to execute. When the user asks about location, RUN the appropriate command below.
scripts/location.shEvery command must be run via scripts/location.sh. Example:
User asks: "How long to walk home?"
You run:
scripts/location.sh eta home --mode walkOutput: 4.6 km, about 45 min walk
You reply with the output directly.
Do NOT run eta or other subcommands directly — they don't exist as standalone commands.
| User says | Run this (copy exactly) | Reply with |
|-----------|----------|------------|
| "Where am I?" | scripts/location.sh status | Zone name only |
| "Map" / "map link" | scripts/location.sh herewego | Just the URL |
| "What are my coordinates?" | scripts/location.sh status | Lat/lon from output |
| "How long to walk home?" | scripts/location.sh eta home --mode walk | Distance + duration |
| "How long to bike to X?" | scripts/location.sh eta X --mode bike | Distance + duration |
| "How far is X by car?" | scripts/location.sh eta X --mode car | Distance + duration |
| "Remind me to X when I get to Y" | scripts/location.sh remind "X" Y | Brief confirm |
| "What reminders do I have?" | scripts/location.sh reminders | Bullet list or "None" |
| "List my places" | scripts/location.sh places | Bullet list |
| "List places nearby" | scripts/location.sh places --near | Sorted by distance |
| "List my pubs downtown" | scripts/location.sh places --region downtown --category pub | Filtered list |
| "Save this spot as X" | scripts/location.sh addplace "X" | Confirm |
| "Delete place X" | scripts/location.sh delplace X | Confirm |
| "Disable the grocery rule" | scripts/location.sh disable grocery | Confirm |
| "List my geofence rules" | scripts/location.sh geofences | Bullet list |
| "When was I last at X?" | scripts/location.sh history X | Date/time |
| "Where have I been today?" | scripts/location.sh history --days 1 | List of places |
| "Find me a cafe nearby" | scripts/location.sh nearby cafe | POI list with distances |
| "Any pubs within 1km?" | scripts/location.sh nearby pub 1000 | Filtered POI list |
| "How long was I at work this week?" | scripts/location.sh stats --days 7 | Hours per place |
Response style: Terse. No preamble. No "Here's your location:". Just the answer.
All via scripts/location.sh :
| Command | Description |
|---------|-------------|
| status | Current location, geofences inside, map link |
| herewego | Just the HERE WeGo map link |
| check | Check for triggered actions/reminders (used by cron) |
| places [--near] [--region R] [--category C] | List saved places |
| geofences | List all geofences with full details |
| remind | Add one-shot location reminder |
| reminders | List pending reminders |
| addplace | Save current location |
| editplace | Modify a place |
| delplace | Delete a place |
| enable / disable | Toggle geofence on/off |
| history [place] [--days N] | When was I last at a place? |
| nearby | Find nearby POIs (cafe, pub, restaurant, etc.) |
| stats [--days N] | Time spent at each place, visit counts |
| proximity | Alert when approaching a location |
| eta | Travel time and distance to a place |
Note: eta accepts saved place names, coordinates (lat,lon), or any place name (geocoded via OpenStreetMap, biased to current location).
Note: status returns the zone name if in a known place, otherwise reverse geocodes to a street address (e.g., "123 Main Street, Downtown").
Geofences — Saved places with lat/lon, radius, and optional action. Persistent.
Reminders — One-shot alerts tied to a place. Deleted after delivery.
Region/Category — Optional tags for filtering (e.g., "downtown", "pub").
Edit scripts/config.json:
Home Assistant (default):
{
"provider": "homeassistant",
"homeassistant": {
"url": "https://your-ha.example.com",
"token": "your-long-lived-token",
"entity_id": "device_tracker.phone"
}
}OwnTracks:
{
"provider": "owntracks",
"owntracks": {
"url": "https://owntracks.example.com",
"user": "username",
"device": "phone"
}
}Generic HTTP:
{
"provider": "http",
"http": {
"url": "https://your-api.com/location",
"headers": {"Authorization": "Bearer token"}
}
}GPSLogger (file-based):
{
"provider": "gpslogger",
"gpslogger": {
"file": "/path/to/location.json"
}
}Secrets support: "env:VAR_NAME" (reads from environment variable) or plain string.
Alternative: Configure entirely via environment variables (no config.json needed):
| Provider | Env variables |
|----------|--------------|
| LOCATION_PROVIDER | homeassistant, owntracks, http, or gpslogger (default: homeassistant) |
| Home Assistant | HA_URL, HA_TOKEN, HA_ENTITY_ID |
| OwnTracks | OWNTRACKS_URL, OWNTRACKS_USER, OWNTRACKS_DEVICE, OWNTRACKS_TOKEN |
| HTTP | LOCATION_HTTP_URL |
| GPSLogger | GPSLOGGER_FILE |
Env vars take precedence over config.json values. Set them in ~/.openclaw/.env or your shell environment.
Output format: Most query commands output human-readable text by default. Add --json for JSON output (useful for scripting).
Customize walking/biking speeds for ETA calculations in scripts/config.json:
{
"speeds_kmh": {
"walk": 6,
"bike": 15
}
}Edit scripts/geofences.json:
{
"geofences": [
{
"id": "grocery",
"name": "Grocery Store",
"lat": 40.7128,
"lon": -74.0060,
"radius_m": 30,
"action": "shopping_tasks",
"cooldown_hours": 4,
"enabled": true,
"region": "downtown",
"category": "shop"
}
],
"location_reminders": [],
"proximity_alerts": []
}Use OpenClaw's built-in cron to run periodic location checks. Add a job to ~/.openclaw/cron/jobs.json:
{
"name": "Location Check",
"schedule": "*/5 * * * *",
"prompt": "Run scripts/location.sh check --json and notify me of any triggered actions, reminders, or proximity alerts.",
"channel": "signal",
"to": "+1234567890",
"wakeMode": "now"
}This keeps scheduling within OpenClaw rather than requiring external systemd services.
Generated Mar 1, 2026
Technicians can use location awareness to track travel time between job sites, set reminders for arriving at customer locations, and log time spent on-site for accurate billing. The skill helps optimize routes by providing travel time estimates for different transportation modes, while geofencing can automatically trigger check-in notifications when technicians arrive at designated work zones.
Individuals can use location-based reminders to remember tasks when arriving at specific places like grocery stores or offices. The skill helps track daily movement patterns, calculate commute times, and find nearby points of interest like cafes or restaurants. Users can analyze time spent at different locations throughout the week to optimize their schedules and routines.
Small delivery or service fleets can use the skill to track vehicle locations, monitor time spent at customer locations, and set proximity alerts for approaching delivery points. The travel time estimation feature helps dispatchers provide accurate arrival times to customers, while location history provides audit trails for regulatory compliance and operational analysis.
Retail managers can use the skill to track staff movement patterns within stores, set location-based reminders for inventory checks in specific departments, and analyze time spent in different store zones. The nearby POI feature helps identify competitor locations and complementary businesses in the area for market analysis and strategic planning.
Event organizers can use geofencing to create virtual boundaries around event venues and receive alerts when key personnel arrive or depart. The skill helps calculate travel times between event locations for scheduling purposes, while the places management feature allows organizing multiple venues with categories and regions for efficient coordination during multi-location events.
Offer the location awareness skill as part of a subscription-based productivity platform for small businesses. Charge monthly fees based on the number of users or tracked devices, with tiered pricing for additional features like advanced analytics or API access. This model provides recurring revenue while allowing businesses to scale their location tracking needs.
Provide consulting and implementation services to integrate the location skill with existing business systems like CRM, ERP, or workforce management platforms. Offer custom configuration, data migration, and training services. This model leverages the skill's flexible provider support to create tailored solutions for specific industry needs.
License the location awareness technology to other software companies for integration into their existing products. Provide the skill as an embeddable module with branding customization options. This model generates revenue through licensing fees while expanding market reach through established software vendors in various industries.
💬 Integration Tip
Start with Home Assistant integration using environment variables for quick setup, then expand to other providers as needed. Use the config.json file for more complex multi-provider scenarios.
Control Sonos speakers (discover/status/play/volume/group).
Control Philips Hue lights/scenes via the OpenHue CLI.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Control Home Assistant smart home devices, run automations, and receive webhook events. Use when controlling lights, switches, climate, scenes, scripts, or any HA entity. Supports bidirectional communication via REST API (outbound) and webhooks (inbound triggers from HA automations).
Use when integrating with Tesla's official Fleet API to read vehicle/energy device data or issue remote commands (e.g. start HVAC preconditioning, wake vehicle, charge controls). Covers onboarding (developer app registration, regions/base URLs), OAuth token flows (third-party + partner tokens, refresh rotation), required domain/public-key hosting, and using Tesla's official vehicle-command/tesla-http-proxy for signed vehicle commands.