Easee EV charger - easee_api setup guide
Easee Home / Charge chargers are controlled through the Easee Cloud API. No LAN scan is required for telemetry or control, but the charger must already be online in the customer's Easee app.
What the customer enters
- Add an Easee EV charger from Otonomo Devices.
- Enter the charger serial in
charger_id(for exampleEH123456). - Save the Easee account in Devices -> Sign-ins:
EASEE_USERNAME: Easee account email or phoneEASEE_PASSWORD: Easee account password
The password is stored encrypted in Otonomo's box_secrets store. It is never
shown back to the browser and is not written into the Pi manifest or
/etc/otonomo/env.
Optional fields
site_id and circuit_id are only needed for circuit-level dynamic current
control. A single home charger can be onboarded with only charger_id.
What Otonomo reads
- charger online state
- charger operating mode
- current charging power
- current output and voltage
- session and lifetime energy
- cable lock, smart charging, reason-for-no-current, and temperature when the Easee state endpoint provides them
What Otonomo can control
Safe controls:
- start, stop, pause, and resume charging
- temporary per-charger current limit
- temporary circuit current limit when
site_idandcircuit_idare set
Operator-gated or future controls:
- cable lock
- charger settings such as smart charging flags
- schedule override
- permanent max charger or circuit current
Permanent current limits are installer-level settings and should not be changed by automation.
Troubleshooting
If the sign-in fails, the Devices page marks the Easee account as failed and
asks the customer to re-enter it. If telemetry is stale, confirm the charger is
visible in the Easee app and that charger_id matches the serial exactly.
Independent interoperability tool. Not affiliated with Easee.