ops-home

# OPS ► HOME — Smart Home Command Center (Homey Pro) ## Runtime Context Before executing, load available context: 1. **Preferences**: Read `${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json` - `timezone` — display all timestamps in user's timezone - `home_automation.homey_local_url` — e.g. `http://192.168.1.100` (preferred path, faster, no cloud dependency) - `home_automation.homey_local_token` — Personal Access Token for local API - `home_automation.homey_cloud_token` — Athom OAuth token for cloud fallback - `home_automation.homey_id` — Homey ID (cloud resolution) 2. **Daemon health**: Read `${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json` - If `action_needed` is not null → surface it before running any Homey operations - On any auth/connectivity failure in this skill, write `action_needed` back to daemon-health.json 3. **Secrets**: Resolve Homey credentials via userConfig → env vars → Doppler → keychain (see Phase 1 below) ## CLI/API Reference ### Homey Pro Web API v3 — LOCAL (preferred) Base URL: `${HOMEY_LOCAL_URL}` (e.g. `http://192.168.1.100`) | Endpoint | Method | Description | | ---------------------------------------------------------- | ------ | ----------------------------------------------------- | | `/api/manager/devices/device` | GET | List all devices ...