An unofficial Home Assistant integration for Rockcore RC-C solar micro-inverters — the ones monitored through the RC-C mobile app (Shanghai Rockcore Electronics Technology).
It brings live production data from the app.rc-ess.com cloud into Home
Assistant, so your balcony / rooftop micro-inverter shows up as a proper device
with sensors and works with the Energy dashboard.
⚠️ Not affiliated with or endorsed by Rockcore. The upstream API is undocumented and reverse-engineered — it may change or break at any time. Use only with your own account and hardware.
The micro-inverter exposed as a Home Assistant device, with live Power, daily / monthly / lifetime energy, and efficiency sensors.
- 🔌 Live power (W)
- ☀️ Energy today, this month, and lifetime total (kWh)
- 📈 Inverter efficiency (%)
- 🏠 One Home Assistant device per inverter, auto-discovered from your account
- ⚡ Energy dashboard compatible (
Total energy→ Solar production) - ☁️ Cloud polling with a configurable update interval (default 60s)
| Sensor | Unit | Device class | State class |
|---|---|---|---|
| Power | W | power | measurement |
| Energy today | kWh | energy | total_increasing |
| Energy this month | kWh | energy | total_increasing |
| Total energy | kWh | energy | total_increasing |
| Efficiency | % | — | measurement |
- In HACS → ⋮ → Custom repositories.
- Add
https://github.com/mnrmurilo/RC-Cas category Integration. - Search for RC-C Solar and download it.
- Restart Home Assistant.
Copy custom_components/rcess_solar into your Home Assistant
config/custom_components/ directory and restart.
- Settings → Devices & services → Add integration.
- Search for RC-C Solar (rc-ess).
- Enter the email and password you use in the RC-C app.
That's it — your inverter(s) are discovered automatically.
The polling interval can be changed later via the integration's Configure (Options) button (15–3600 seconds).
Settings → Dashboards → Energy → Add solar production and select the Total energy sensor.
There is no local API on the inverter and no official integration, so the data had to be pulled from the same cloud the RC-C app uses. The whole thing was figured out in my homelab using a man-in-the-middle proxy.
Homelab note: everything below ran on my own LAN against my own account and my own inverter. Nothing here touches anyone else's data.
A full TCP port scan of the inverter (1–65535) returned nothing open, and
it answered no Tuya / Solarman / Modbus / SSDP / mDNS / SNMP discovery probes.
It only talks outbound to the vendor cloud — so a cloud integration it is.
An existing community integration
(ErwinSt/home-assistant-solarcore-energy)
targets a legacy server (gf.rockcore-energy.com:9721/rcmi-manager) and
returned "User not registered" for my account — newer RC-C accounts live on a
different platform.
Decompiling the RC-C app (an Expo / React Native app, same build on iOS and
Android) showed it's a thin shell around a web app served from
app.rc-ess.com via a jowoiot IoT backend.
I ran mitmproxy on a Proxmox LXC container in the homelab instead:
iPhone (RC-C app) ──HTTP proxy──▶ mitmproxy on LXC (192.168.68.x:8080) ──▶ app.rc-ess.com
- iPhone Wi-Fi → Configure Proxy → Manual pointed at the container.
- Installed + trusted the mitmproxy CA on the phone (Settings → General → About → Certificate Trust Settings).
- Logged into RC-C once and opened the inverter's live view to record the full login + telemetry flow.
Capturing on a dedicated homelab box (rather than the laptop) sidestepped the corporate firewall entirely and kept the capture off the work machine.
From the capture, the request/response contract was reconstructed and then verified live against the server before writing a single line of the integration.
Base URL: https://app.rc-ess.com/jowoiot-proxy/api
All requests send these tenant headers (observed from the app):
Content-Type: application/json;charset=utf-8
scope: yx_test
OwnerId: 1
oem: rc
POST /project/rc/auth/login
{ "channelType": 2, "content": "<email>", "password": "<password>", "type": "2" }Response → data.response.accessToken (a bearer token). All subsequent calls
send Authorization: Bearer <accessToken>; on 401 the client simply logs in
again.
POST /project/rc/station/overview/searchStation
{ "page": 1, "row": 100 }→ data.content[] { id, name, ... }
GET /project/rc/station/item/getList?stationId={stationId}→ [ { id, sn, model, stationId, ... } ]
GET /project/rc/device/data/{deviceId}Energy fields are in Wh and divided by 1000 for the kWh sensors.
RC-C/
├── custom_components/
│ └── rcess_solar/
│ ├── __init__.py # setup + DataUpdateCoordinator
│ ├── api.py # async client for app.rc-ess.com
│ ├── config_flow.py # UI login + options
│ ├── const.py # endpoints + tenant headers
│ ├── sensor.py # sensor entities
│ ├── manifest.json
│ └── translations/en.json
├── docs/
│ └── home-assistant-device.png
├── .github/workflows/validate.yml # hassfest + HACS CI
├── hacs.json
├── README.md
├── SECURITY.md
├── LICENSE
└── .gitignore
This is a personal, best-effort project provided as-is under the MIT license. It depends on an undocumented third-party cloud API that can change without notice. Not affiliated with Rockcore. See SECURITY.md for how credentials are handled and how to report issues.

{ "power": 537, // current AC power, W "efficiency": 67, // % "dayEnergy": 900, // Wh -> 0.90 kWh "monthEnergy": "56620",// Wh -> 56.62 kWh "yearEnergy": "392280", "accEnergy": "392280", // lifetime Wh -> 392.28 kWh "model": "RC8009", "isOnline": true, "state": true }