Manually trigger a Rachio schedule rule (multi-zone program) on demand and skip an upcoming scheduled run
domain: rachio.readme.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get the schedule rule id from the ScheduleRule objects nested in a Device, or via GET /public/schedulerule/{id} directly.
To run the whole program immediately, send PUT /public/schedulerule/start with body {"id": "<scheduleRuleId>"} — this runs all the rule's zones in their configured order and durations.
To skip the schedule's next planned run instead of running it now, send PUT /public/schedulerule/skip with the same {"id": ...} shape.
To scale all runtimes in a schedule (e.g. -50% during cooler weather) without restructuring zones, use PUT /public/schedulerule/seasonal_adjustment.
Watch for CLIMATE_SKIP_NOTIFICATION_EVENT / RAIN_SKIP_NOTIFICATION_EVENT / WIND_SKIP_NOTIFICATION_EVENT webhooks, which fire when Rachio's own weather intelligence decides to skip a run automatically.
Known gotchas
schedulerule/start always uses the rule's stored per-zone durations and order; it ignores any one-off duration override you might want for a single run.
seasonal_adjustment expects a fractional multiplier, not a percentage string; out-of-range values return a 4XX with limited detail.
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?