OpenSprinkler & Home Assistant
OpenSprinkler is the reference open-source irrigation controller, and its Home Assistant integration matches that philosophy: a custom integration installed through HACS that polls the controller’s fully documented local HTTP API. Zones and programs appear as switches, with run-once support, rain delay control, and controller diagnostics, and no cloud account exists anywhere in the stack.
Because the firmware is open source and also speaks MQTT natively, OpenSprinkler is the controller of choice when an installation calls for deep customization: remote stations, HTTP-driven zones, two master stations, and sensor inputs are all part of the standard firmware. The integration is actively maintained and configured entirely from the Home Assistant UI.
Installed through HACS
How OpenSprinkler Works with Home Assistant
Getting OpenSprinkler connected to Home Assistant and running reliably.
Local connection
Home Assistant connects to OpenSprinkler over the local network. Zones, programs, and sensors appear as entities you can control and automate.
Zones & schedules
Run any zone for a set number of minutes, trigger full programs, or set a rain delay, from the dashboard, voice, or an automation.
Weather-aware watering
Combine OpenSprinkler with forecast data, a rain gauge, or soil moisture sensors so watering skips automatically when it is not needed.
Common OpenSprinkler Issues
The problems installers run into with OpenSprinkler and Home Assistant — and how a managed setup prevents them.
Cloud apps bolted onto dumb timers
Many consumer sprinkler controllers only work through the manufacturer's cloud. If the service is discontinued or paywalled, the hardware is stranded. OpenSprinkler is deployed for its local control path, which keeps working regardless.
Weak wireless where the controller lives
Controllers get mounted in garages and utility rooms at the edge of wireless coverage. Dropped connections make zones show unavailable and schedules unreliable until coverage is fixed.
Valve wiring surprises on retrofit
Swapping an old timer for OpenSprinkler means re-landing zone commons, master valve, and rain sensor wires. Mislabeled or shared wires cause zones that never fire or fire in pairs.
A stuck valve waters all night
A failed solenoid or a lost stop command can leave a zone running for hours. Without runtime monitoring and alerts, the first sign is a flooded lawn or a water bill.
Why installers choose managed OpenSprinkler irrigation
- Local-first configuration so schedules survive internet outages
- Skip logic wired to real data: rain, forecast, and soil moisture
- Runtime monitoring that alerts on stuck valves and zones that never ran
- Seasonal adjustment reviewed and tuned instead of set-and-forget
OpenSprinkler devices we deploy
Hardware from the Selora catalog that runs on this integration. Every unit is tested and supported as part of a managed installation.
Irrigation
2 devicesOpenSprinkler 3 (OS 3.4)
The reference open-source sprinkler controller: 8 zones on board, expandable to 72 with zone expanders, built-in Wi-Fi and OLED display, with an optional wired Ethernet module. Home Assistant runs zones, programs, and rain delays over the fully documented local HTTP API, and no cloud account or subscription exists at all.
OpenSprinkler Pi 2.0
A Raspberry Pi extension board that turns the Pi into a full OpenSprinkler controller running the same unified open-source firmware. It uses the Pi's own Ethernet or Wi-Fi, drives 8 zones expandable to 200 with zone expansion boards, and exposes the same local HTTP API Home Assistant uses to run zones and programs. Ideal when you want irrigation on hardware you already rack in the utility room.
Frequently Asked Questions
Ready to Install OpenSprinkler Professionally?
Stop troubleshooting OpenSprinkler integration issues. Let Selora handle the setup, monitoring, and maintenance so you can focus on your clients.