@kentcdodds/hydrawise
Server-side Hunter Hydrawise controller and zone helpers backed by the hydrawiseApiKey secret.
- Other
- home
- irrigation
- hydrawise
- hunter
- automation
- Version
- 1.1.0
- License
- MIT
- Published
- September 11, 2026
- Pinned commit
07dd090- Rating
- No ratings yet
- Forks
- 0
- Adaptation effort
- —
README
Agent docs@kentcdodds/hydrawise
Intent
Server-side Hunter Hydrawise irrigation helpers for listing controllers, reading zone schedules, and running or suspending zones. A weekday status job posts a glanceable Discord #reporting line (read-only).
What it does
- List controllers and read zone status without side effects
- Run, stop, suspend, or resume one zone or all zones (mutating — only when explicitly requested)
- Call a compact
requesthelper for raw Hydrawise REST under/api/v1/ - Post a weekday morning status line (controllers, rain/sensors, next run) via
the scheduled
weekday-statusjob
Prerequisites / setup
Generate an API key in Hunter Hydrawise (Account Details → Generate API Key).
Save it in Kody as user secret
hydrawiseApiKey(never paste the value in chat):Approve host
api.hydrawise.comand package access tohydrawiseApiKeyif prompted.Agents: see
AGENTS.mdfor import paths, dry-run smoke, and mutation cautions.
Hydrawise does not publish an OpenAPI spec (PDF REST guide only). Auth is the
api_key query param via the secret placeholder — not Bearer.
Done when
hydrawiseApiKeyis saved; host and package secret access are approved- Read-only
list-zones/get-controllersreturns controller and zone data weekday-statuswithdryRun: trueformats a status line without posting- Mutating zone actions are used only when the user explicitly asks
Report this listing
Log in to report this listing.