A Home Assistant custom integration for Renogy ONE Core power systems, talking to the same private "DC Home" gateway API used by the official Renogy phone app. It surfaces telemetry (battery, charger, distribution box channels, tanks, temperatures, TPMS) as sensors, exposes real load switches/dimmers as controls, and curates device settings (charge limits, alarm thresholds, battery type, and similar) as configuration entities.
Unofficial. This integration talks to Renogy's private mobile-app API, which has been reverse-engineered for interoperability and is not publicly documented or supported by Renogy. It is not affiliated with or endorsed by Renogy. The API can change without notice and break this integration.
- A Renogy ONE Core gateway already set up and working in the Renogy DC Home app.
- Your Renogy account email and password (the same ones used in the app).
- Home Assistant with HACS installed.
This integration is not in the default HACS store, so add it as a custom repository:
- In Home Assistant, go to HACS → Integrations.
- Click the ⋮ menu (top right) → Custom repositories.
- Add this repository's URL:
https://github.com/tdack/ha-renogy-gateway - Category: Integration.
- Find "Renogy Gateway" in HACS and install it.
- Restart Home Assistant.
- Go to Settings → Devices & services → Add integration.
- Search for Renogy Gateway.
- Enter your Renogy account email and password.
- If your account has more than one gateway, pick the one to add.
Each devices behind the gateway is created in Home Assistant with its telemetry as sensors, real load channels as switches/lights, and device settings grouped under the entity Configuration tab.
Remove the integration entry from Settings → Devices & services, then remove the repository from HACS if you no longer want updates.
This is a community project maintained on a best-effort basis. Please file issues at the GitHub issue tracker.
docs/PROTOCOL.md documents the reverse-engineered
private gateway/RTM API this integration talks to — auth, the WebSocket
telemetry/control protocol, and the self-describing schema discovery
(gwm.devs/get_product/get_model) that drives entity creation here.
Useful background if you're debugging an issue or curious how a given
device's fields end up as the entities they do.
This integration uses Renogy's own brand icon/logo (the same images
firstof9/ha-renogy uses, sourced
from home-assistant/brands'
custom_integrations/renogy/ folder). Two delivery mechanisms are set up:
custom_components/renogy_gateway/brand/— bundled directly in the integration. Home Assistant 2026.3+ serves these locally via the Brands Proxy API with no extra configuration, so the icon shows up immediately after installing, without waiting on an external PR.brands/custom_integrations/renogy_gateway/— a staging copy in the legacy layout, ready to submit as a PR to home-assistant/brands for older Home Assistant versions that don't yet support local brand images.
docs/icon.png (shown at the top of this README) is the same icon.