V2C
How Joulo connects a V2C Trydan through the V2C Cloud, and which Trydan revisions carry a MID meter.
V2C Trydan chargers connect through the V2C Cloud. You generate an API key at v2c.cloud and paste it into Joulo. The key is static, so the connection does not expire on its own.
At a glance
| Property | Value |
|---|---|
| Route | Cloud API |
| API | V2C Cloud |
| Authentication | Static API key from v2c.cloud |
| Sync | Every 15 minutes |
| MID detection | Per charger, from the V2C device shadow (pcb_type, product code) |
| Backfill | Automatic, to 1 January 2026 |
How the connection works
Joulo lists your paired devices and reads statistics per device. V2C changed its device identifier from a numeric ID to an alphanumeric one. Older integrations cached the numeric ID, so Joulo builds a mapping on each run and falls back to the stored ID when no mapping exists.
What Joulo reads
Joulo reads the charge statistics per device and turns each entry into a session with a start time, an end time and the metered energy.
MID certification
The catalog holds three V2C rows, and they are deliberately distinct:
| Catalog model | MID meter |
|---|---|
| Trydan | Never |
| Trydan Pro | Optional add-on, so the verdict stays open until confirmed |
| Trydan Pro MID | Confirmed by review |
A plain Trydan is not eligible for ERE registration. A Trydan Pro is eligible only when it reads a MID meter. A product code ending in -MID means a MID meter from the factory. The device shadow reports pcb_type = MIDMETER when the charger reads it.
Limitations
/pairings/meand the session statistics carry no MID flag. Joulo reads the device shadow (/device/reported) once a day per charger for that.- A charger that reads its MID meter reports energy in steps of 10 Wh. Joulo does not count a session on 1 Wh from such a charger.
- A device renamed in the V2C app keeps its identifier. Joulo follows the identifier, not the name.