Rainpoint carrier

RainPoint Local

A local Home Assistant stack for RainPoint 433/434 MHz irrigation devices. ESP32/CC1101 radios communicate with the devices; rainpointd owns decoding, associations, ACK ownership, counters, and safety; the HA integration exposes telemetry and qualified controls. Normal operation does not need the vendor cloud or an SDR.

Alpha 2 is available — sensors and single-, two- and four-zone valves. Start with Getting started: agent-assisted setup. Give the guide to your agent to install the gateway and integration, help flash your radio, and hand you off to device pairing in Home Assistant. Use gateway 0.39.19, HA integration 0.18.6 and signed radio firmware 0.21.0 together. Download the firmware and matched gateway source and HACS integration. Update the gateway before any radio. See Alpha 2 release notes and limitations. We're inviting builders to help validate fresh installs and device lifecycle behavior; alpha does not mean those remaining tests have already passed.

Device support

Read device communication references for packet rules and the roadmap for remaining qualification work.

Already installed? Follow the user upgrade guide, or give your agent the upgrade procedure. For a newly added two-zone valve, also use the two-zone pairing and testing guide.

Install on Home Assistant OS

Install RainPoint Local Gateway from HA's app/add-on repository and RainPoint Local from HACS. Both use this repository URL; HACS installs only the integration, not the gateway or radio firmware. The getting-started guide walks your agent through installation, USB flashing and Wi-Fi adoption, then guides you through pairing in HA.

The existing HomGar/RainPoint cloud integration is not required or replaced. For detailed settings or recovery, see the add-on guide and firmware guide.

Operation

HA watering notifications are enabled by default; mobile forwarding is optional. See notification behavior. These features and fresh-pairing counter initialization are deployed in the reference installation; independent clean-install and physical onboarding acceptance remain separate.

Each device has one persistent transmitting ACK owner; other radios may receive and forward reports. Firmware restores assignments after reconnect. HA state comes from device responses or independent telemetry, not command intent.

Valve actuation requires a supported paired device and a capable, available owner; no research switch or mandatory two-run unlock is required. Counter readiness and device-response confirmation still apply. Single- and four-zone valves expose counter status and morning synchronization settings. Each single-zone association has its own control, duration and persisted counter state.

All three valve families enforce bounded durations, command spacing, and durable command reservations. Startup and missing telemetry never send a speculative close. Unknown counters block ordinary control until explicit recovery is confirmed.

Development

Manage pairing through Settings → Devices & services → RainPoint Local. Device setup uses HA's native options flow; no separate sidebar panel is required.

Use the canonical checkout and Git branches; do not create additional worktrees.

PYTHONPATH=rainpointd_addon python3 -m rainpointd

This starts an empty network gateway. Use the explicit captured replay example for offline sample data. See local development for runtime options and AGENTS.md for the complete required Python and native regression commands. Install the development test dependencies with python3 -m pip install -r tests/requirements.txt in a virtual environment first. Build only the rainpoint_bridge PlatformIO environment; production must exclude experimental transmit paths.

Documentation map

Installation-specific captures, databases, credentials, and build output stay untracked. Preserve raw captures until useful exchanges have redacted fixtures.

See security boundaries before deploying or exposing listeners.