OpenEVSE
Why an OpenEVSE has no route into Joulo, and what the options are.
An OpenEVSE exposes a local HTTP and RAPI interface on your own network. There is no cloud to read from outside. A standard build has no MID meter either, so there is no route into Joulo for ERE registration.
At a glance
| Property | Value |
|---|---|
| Route | No automatic route |
| API | Local HTTP and RAPI, on your own network only |
| Sync | Not applicable |
| MID detection | Not automatic |
| ERE registration | Not possible without a MID meter |
Why the local API is not enough
Even with the local interface reachable, the number it reports comes from the charger's own uncertified counter. ERE registration counts kWh that a certified instrument measured, so a reading from an uncertified counter cannot be registered whatever path it travels.
An OpenEVSE that reads an external kWh meter over Modbus is a different case. There the certified meter really is the source. Contact Joulo support with the details before you plan on it, because the decision turns on which device produces the number Joulo receives.
What you can do
Two routes lead to eligible energy:
- Replace the charger with a model that has a built-in MID meter. Joulo quotes this, and the installer takes the old charger and settles the trade-in.
- Ask your grid operator for a secondary allocation point. This gives the charger its own metered supply point. Expect an installation charge of roughly 200 to 300 euro plus a monthly fee.
Counting starts at the meter. Sessions charged before a MID meter is in place never become eligible. An external meter in the fuse box is not a valid route for home charging.