REST API
Access to the site controllers through the EdgeTech backend over REST, for Home Assistant, DIY and integrations: status, control, schedules, solar modes, usage export. With a subscription. The public API surface, authentication and an OpenAPI file are being finalised.
Decision pending Whether this document stays as described is not yet decided. It is on the site so the team can see it in place.
The endpoints below are the app’s API today; the third-party API, its token scheme and read/write rules are being defined. Nothing here is final.
What it covers
| Area | Calls |
|---|---|
| Sites and sockets | list sites, site info, site status, sockets, socket status, socket and site configuration |
| Control | allow or disallow charging, start now, delayed start, schedule items, plug and charge, socket priority, phases per socket |
| Limits | max site current, grid connection type |
| Solar | solar mode, charge from solar only, extended trigger and condition |
| Insight | usage report per period, energy price setting, force status refresh |
| Support | diagnostics ticket, log upload, firmware check and upgrade |
Home Assistant
A rest sensor for status and rest_command for control, with a per-site token. An example configuration and the OpenAPI file follow when the API is public.
Local instead
No cloud, no subscription: drive the charge controller directly over Modbus RTU (register map), with evcc or Home Assistant’s Modbus integration. One master per bus.