Skip to content
Home Assistant TestFlight
Water

HomGar/RainPoint Cloud

brettmeyerowitz/homeassistant-homgar · vv3.1.2

HACSCloud push

Home Assistant custom integration for RainPoint and HomGar irrigation devices.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
switchSwitch or outlet
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature, humidity, air quality…)
valveValve

What people report

RainPoint/HomGar H-series hubs and RF valves work via the cloud; Bluetooth-only and Tuya T-series devices are outside scope.

  • Works4
  • Partly works1
  • Won’t be supported1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
RainPoint HTP159W WiFi valveWorks CloudWiFi tap timer support added
Saved copy
Summary - Add HTP159W WiFi valve/tap timer support for issue #55. - Recognize raw device payloads published in the cloud `state` field for REST and MQTT hub-as-device paths. - Route HTP159W Home Assistant valve commands through `controlWorkModeDP`, including the 60-second `3c000000` runtime payload. - Prefer the selected home that actually contains a discovered hub when requesting MQTT credentials. ## Validation - Live HTP159W MQTT open/close state confirmed. - Live Home Assistant initiated open/close confirmed by the device owner. - `bash scripts/pre-commit-docker-test.sh` ## Device Audit - …

Excerpt saved from GitHub on 2026-10-23.

PR #57 · 2026-05
RainPoint HTV0540FRF valveWorks CloudValve entities and 1-60 min duration per zone (v1.2.0)
Saved copy
Unsupported device: HTV213FRF irrigation valve Hub: HWG023WRF (detected in HA as `device_tracker.homgar_95_98`, state: `home`) Valve module: HTV213FRF (single-zone RF irrigation timer) ### Current behavior The integration successfully connects to the HomGar cloud and detects the HWG023WRF hub. However, the HTV213FRF valve module is not recognized, no `valve.*` or `number.*` entities are created for it. Based on the code in `const.py`, only `HTV0540FRF` is currently mapped as `MODEL_VALVE_HUB`. My device model (`HTV213FRF`) is not in the list, so its payload is stored as raw/unknown data …

Excerpt saved from GitHub on 2026-10-23.

Issue #11 · 2026-03
RainPoint HTV245FRF valveWorks CloudSupported in v1.3.2 with the HTV0540FRF decoder
Saved copy
Great news @reclus23! 🎉 I've just released v1.3.2 with full support for HTV213FRF and HTV245FRF valve controllers! ### What's Fixed: ✅ HTV213FRF and HTV245FRF now supported ✅ Uses same decoder as HTV0540FRF (since payload starts with 11#) ✅ Will create valve entities (open/close control per zone) ✅ Will create duration number entities (1-60 min per zone) ### What This Does: - HTV213FRF and HTV245FRF are now recognized instead of showing as 'unsupported' - Both use the same as HTV0540FRF (confirmed by your 11# payload) - Valve entities will be created for each zone reported by your device - …

Excerpt saved from GitHub on 2026-10-23.

Issue #11 · 2026-03
RainPoint HWG023WRF hubWorks CloudHub detected as device tracker
Saved copy
Unsupported device: HTV213FRF irrigation valve Hub: HWG023WRF (detected in HA as `device_tracker.homgar_95_98`, state: `home`) Valve module: HTV213FRF (single-zone RF irrigation timer) ### Current behavior The integration successfully connects to the HomGar cloud and detects the HWG023WRF hub. However, the HTV213FRF valve module is not recognized, no `valve.*` or `number.*` entities are created for it. Based on the code in `const.py`, only `HTV0540FRF` is currently mapped as `MODEL_VALVE_HUB`. My device model (`HTV213FRF`) is not in the list, so its payload is stored as raw/unknown data …

Excerpt saved from GitHub on 2026-10-23.

Issue #11 · 2026-03
RainPoint HTV213FRF valvePartly works CloudRecognised in v1.3.2 but decoder found no zones for reporter
Saved copy
Unsupported device: HTV213FRF irrigation valve Hub: HWG023WRF (detected in HA as `device_tracker.homgar_95_98`, state: `home`) Valve module: HTV213FRF (single-zone RF irrigation timer) ### Current behavior The integration successfully connects to the HomGar cloud and detects the HWG023WRF hub. However, the HTV213FRF valve module is not recognized, no `valve.*` or `number.*` entities are created for it. Based on the code in `const.py`, only `HTV0540FRF` is currently mapped as `MODEL_VALVE_HUB`. My device model (`HTV213FRF`) is not in the list, so its payload is stored as raw/unknown data …

Excerpt saved from GitHub on 2026-10-23.

Issue #11 · 2026-03
RainPoint HCS048B Bluetooth sensorWon’t be supportedRegisters in app but never appears in Home Assistant; Bluetooth-only
Saved copy
Why An HCS048B registers fine in the RainPoint app and then never appears in Home Assistant. It isn't a setup fault and no configuration fixes it: that sensor reports over Bluetooth straight to the phone, its readings are cached there, and the cloud is never told. An account containing one used to crash setup outright for exactly this reason (#97), the cloud answers with a null payload because it has nothing to report. A cloud integration cannot read these by any means, so listing them sent people hunting for a fault that was never theirs. ## What changed The README list is generated from …

Excerpt saved from GitHub on 2026-10-23.

PR #116 · 2026-09

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Cloud push

Goes through the maker’s cloud, which sends updates as they happen. Needs the internet and an account.

Details

Installs (analytics)537 (0.08%)
GitHub stars27
Latest versionv3.1.2 (2026-10-20)
Set up in the UIYes
Maintainers@brettmeyerowitz
LicenseMIT

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.