Renogy Gateway — HACS integration for Renogy ONE Core power systems

Share your Projects! Custom Integrations
, , ,
1

Hi all,

With the help of Claude Code and Cowork I've put together a custom integration for the Renogy ONE Core power system (the smart distribution box, shunt, MPPT/DC-DC chargers, TPMS, and inverter/charger that hang off it).

Repo: GitHub - tdack/ha-renogy-gateway: A Home Assistant custom integration for Renogy ONE Core power systems · GitHub

What it does

It talks to the same private "DC Home" gateway API the official Renogy phone app uses (reverse-engineered for interoperability — see docs/PROTOCOL.md in the repo for the full writeup). Once connected, it discovers your rig's devices and fields at runtime — no hardcoded device list — and surfaces:

  • Sensors for telemetry (battery SOC/voltage/current, charger output, tank levels, temperatures, TPMS pressure/temperature)
  • Switches/lights for real load channels, including dimmable ones
  • Numbers/selects for device settings (charge profile voltages, alarm thresholds, battery type, etc.) under each entity's Configuration tab
  • Buttons/switches for Manual/Auto scenes configured in the Renogy app
  • Your own channel names from the app (e.g. "Bedroom Light" instead of dc_10a_1) carry through automatically

It's push-based (WebSocket subscribe), not polling, so updates arrive as the gateway pushes them.

Screenshot
Screenshot2074×1664 260 KB

Install

Not in the HACS default store — add it as a custom repository:

  1. HACS → Integrations → ⋮ → Custom repositories
  2. Add https://github.com/tdack/ha-renogy-gateway, category Integration
  3. Install, restart HA, then Settings → Devices & services → Add integration → search "Renogy Gateway"

Requires your Rengoy DC Home credentials to login. Credentials are sent to the Renogy API for authentication.

Caveats

  1. This talks to a private, undocumented API — it's not affiliated with or endorsed by Renogy, and the API can change without notice. It's been tested against my own ONE Core rig; I'd appreciate reports (via GitHub issues) if you try it on a different setup, since device schemas may vary more between firmware revisions.

  2. The integration exposes significantly more configuration items than the Renogy DC Home app. Make changes with care, whilst you are with your system, you can break things if you make uninformed changes (eg: excessively high charging currents)

  3. This integration only works if you have enabled your ONE Core to access the internet in some way so that it can talk to the Renogy DC Home API and servers. If the ONE Core isn't connected to DC Home via the internet this integration will not work for you.

Feedback, bug reports and PRs welcome!