Manually run, stop, or suspend a Hydrawise zone using the setzone.php action endpoint
domain: hydrawise.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get the target zone's relay_id from a prior statusschedule.php call.
To run a zone on demand: GET /api/v1/setzone.php?action=run&api_key=<key>&period_id=999&relay_id=<id>&custom=<seconds>.
To stop one running zone: GET /api/v1/setzone.php?action=stop&api_key=<key>&relay_id=<id>; to stop everything at once use action=stopall (no relay_id needed).
To suspend a zone until a future time (e.g. a rain skip), use action=suspend with period_id=999 and custom=<unix-epoch-seconds-to-resume>, or action=suspendall for the whole controller.
Check the response's message_type field ("error" vs "info") rather than assuming HTTP status reflects success — Hydrawise returns 200 with message_type":"error" for many rejected commands.
Known gotchas
All actions are issued as HTTP GET requests with parameters in the query string, including run/stop/suspend commands — there is no JSON request body.
suspend/suspendall's custom parameter is a Unix epoch timestamp (when to resume), while the run action's custom parameter is a duration in seconds — mixing these up is an easy bug.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?