Quick Summary (TL;DR)
The best smart EV charger for Home Assistant is the one whose exact hardware and firmware expose the controls you need, without depending on a fragile workaround. For a local-first household, OpenEVSE is a strong specialist option because Home Assistant’s built-in integration communicates with the charger over the local network and supports charging-current adjustment. go-e Charger hardware is attractive for technically confident owners seeking documented interfaces such as local HTTP API, but its particular Home Assistant route may depend on community software, evcc or an OCPP controller. Wallbox and Ohme are practical mainstream choices with built-in Home Assistant integrations, although those integrations use the manufacturers’ cloud services. Myenergi zappi deserves attention when solar-surplus charging is the primary objective; confirm the exact OCPP-capable model, account and firmware before planning third-party control.
Do not choose by the word “OCPP” alone. OCPP is a charger-to-management-system protocol, not a promise that Home Assistant will instantly discover a charger, nor that load balancing, phase switching, solar diversion and all charging controls will work through it. Confirm the usable API, data granularity, control permissions, network-failure behaviour and installer-supported protective features before ordering. In Great Britain, also establish whether the proposed charge point and installation meet the applicable smart-charge-point rules and electrical requirements.
Our picks at a glance
| Best for | Charger or family to investigate | Why it makes the shortlist | Principal compromise |
|---|---|---|---|
| Local Home Assistant control | OpenEVSE with supported Wi-Fi firmware | Built-in local integration, live measurements, charge-current control | Specialist product; assess local approvals and qualified installation |
| Open interfaces and advanced tinkering | go-e Charger Gemini / appropriate later models | Manufacturer documents local HTTP, cloud, OCPP and other interfaces on supported models | Home Assistant implementation is model- and integration-dependent |
| Straightforward mainstream HA integration | Wallbox compatible charger | Built-in Home Assistant integration with metering, current and solar settings | Official integration uses MyWallbox cloud polling |
| Tariff-oriented managed charging | Ohme Home Pro / ePod | Built-in Home Assistant integration, provider-aware schedules and selected controls | Cloud connection, model-specific controls; no direct energy total from Ohme API |
| Solar-first UK installation | Myenergi zappi | Manufacturer solar-diversion ecosystem and OCPP configuration on supported units | Manufacturer hardware, CT and firmware details must be checked; HA OCPP is not plug-and-play |
| Local charge monitoring without deep control | Tesla Wall Connector Gen 3 | Built-in Home Assistant local integration; energy and connection sensors | The official HA integration provides monitoring, not general current control |
This is a feature-based shortlist, not laboratory testing or a live price ranking. Charger families are not identical products. Hardware revisions, region, wiring, firmware, subscriptions and installer configuration may change what is available. Obtain a written compatibility answer for the model being quoted.
What makes an EV charger genuinely Home Assistant friendly?
A capable wallbox has two jobs. Its first and essential job is to charge a vehicle safely, observe its electrical limits and respond correctly to fault conditions. Its second job is to report status and accept optional smart instructions. Home Assistant should be in the second category: an optimisation layer rather than the only thing preventing a household overload or protecting the charge circuit.
Start with the functions you really want. Owners looking only for a daily energy dashboard need an accurate cumulative kWh figure and sensible update frequency. Solar enthusiasts need measured grid import/export, adjustable current and behaviour that remains stable as clouds pass. Users on half-hourly tariffs need predictable scheduled start and stop, ideally with a departure deadline. A household with limited import capacity needs a properly engineered dynamic-load-management arrangement, not just an automation that hopes the Wi-Fi network stays online.
- Complete electrical commissioning first. Confirm protective devices, load balancing, earth arrangements, charge-current limits and the manufacturer’s approved configuration. Do not bypass the charger’s controls to make an integration work.
- Update charger firmware using its supported method and record model and firmware version. Read the integration’s device-support notes, not just the integration name.
- Check the intended connection. Local integrations need the correct network path; cloud integrations need account credentials and working vendor service; OCPP requires a compatible backend reachable from the charge point.
- Open Settings → Devices & services → Add Integration and choose the appropriate built-in integration when available. For third-party integrations, inspect maintainership, permissions, update policy and security before installing.
- Identify the real entities. Find connection state, charging status, current limit, instant power, session energy, cumulative energy and error state. Do not assume similarly named sensors have the same units.
- Test while unplugged, plugged but idle, and actively charging. Compare the dashboard with the charger’s native display and, where available, an independent circuit meter.
- Test loss of internet and Home Assistant separately. Record whether charging continues, whether a current limit remains in force and how schedules resume. Restore normal operation after each test.
If the device has one backend field, do not overwrite a vendor-provided OCPP URL simply to experiment. First establish a rollback path and whether that field must remain associated with a billing or tariff service. A CSMS design can require additional security, TLS, certificates and configuration beyond pointing to a local IP address.
Home Assistant Energy dashboard: power is not energy
Home Assistant’s Energy dashboard needs a cumulative energy measurement in kWh or another valid long-term energy sensor with the right state properties. A momentary power reading in kW is not interchangeable. For example, an EVSE reading 6.6 kW for two hours consumes approximately 13.2 kWh at the wall; the same number entered as a kWh total would corrupt your accounting. Battery charging losses and vehicle heating mean energy measured by the charger may not equal the energy stored in the vehicle battery.
OpenEVSE and Tesla Wall Connector integrations document total energy measurements suitable for the Energy dashboard. Wallbox also exposes added energy through its cloud integration. Ohme is a relevant exception: the built-in integration documentation currently explains that the API does not supply cumulative energy directly, and suggests deriving energy from reported power. Where precise EV charging costs matter, a dedicated approved circuit meter can provide a stronger independent baseline.
For an existing system, see our published guides to the <a href=”https://esp32AliExpress price.co.uk/esp32AliExpress price-modbus-energy-meter-home-assistant-sdm120-sdm630AliExpress price/”>ESP32AliExpress price Modbus energy meter with Home Assistant</a>, <a href=”https://esp32AliExpress price.co.uk/esp32-ct-clamp-energy-monitor-for-home-assistant/”>ESP32 CT clamp energy monitoring</a> and <a href=”https://esp32.co.uk/home-assistant-energy-dashboard-troubleshooting-esphome/”>Energy dashboard troubleshooting with ESPHome</a>. Use the same grid and consumption boundaries every time; do not count an EV circuit twice as separate whole-house demand.
OCPP self-hosting: five tests before you depend on it
OCPP provides a route to interoperability, but a charger’s real-world implementation determines what works. Request the exact OCPP version and supported commands from the supplier. Test against the actual CSMS or local charging controller before relying on it to schedule a vehicle every night.
| Acceptance test | Pass condition | Typical failure |
|---|---|---|
| Connect and identify | CSMS shows the correct station and connector | Wrong URL, TLS trust or station ID |
| Meter reading | Correct energy units and reasonable timestamps | MeterValues missing or infrequent |
| Remote start/authorise | Session begins as expected with user approval | Charger requires local RFID or vehicle action |
| Remote current profile | Current changes within manufacturer-approved bounds | Smart-charging profiles ignored |
| Restart and outage | Known safe current and usable charging after reconnect | Charger stays blocked by stale backend setting |
A secure OCPP design must account for credentials, transport encryption, access rules, logging and firmware changes. Never expose an unauthenticated charger backend on the public internet. The Open Charge Alliance publishes the official OCPP version histories and specifications; verify which version your chosen charging software actually implements.
Charging safety, UK requirements and installation costs
In Great Britain, applicable domestic charge-point products are subject to the Electric Vehicles (Smart Charge Points) Regulations 2021, with features covering smart functionality, off-peak scheduling, randomised delays, security and certain behaviour when network communication is lost. The regulations do not mean you should disconnect approved safety equipment or disable protective charger functions to obtain faster Home Assistant automations. Check applicability to the proposed product and installation rather than assuming every UK and non-UK model is equivalent.
Have a qualified EV charge-point installer review the service rating, DNO notification or application, earthing arrangement including relevant PEN fault protection, suitable RCD and fault-current arrangements, cable routing, isolation, surge considerations, correct CT placement and meter installation. The exact solution depends on the property’s supply and the charger’s approved design. These are not do-it-yourself changes to make through Home Assistant or ESP32 relays.
Compare installed cost, not wallbox sticker price
| Cost component | Ask the installer to include | Why it may vary |
|---|---|---|
| Charger hardware | Exact product and tethered/untethered choice | Brand, cable, warranty and power rating |
| Electrical installation | Cable, protection, isolation, commissioning | Distance, structure and existing consumer unit |
| Dynamic load management | Approved CT/meter and setup | Whole-home import limit and existing solar |
| Solar integration | Metering accessories or controller | Single/three-phase and battery coexistence |
| Network connectivity | Reliable Wi-Fi or Ethernet arrangement | Signal strength at garage/driveway |
| OCPP or API setup | Supported configuration and tests | Installer support versus DIY administration |
| Energy monitoring | Meter calibration/reporting method | Estimated sensor versus dedicated meter |
| Service and changes | Firmware, subscriptions and ownership transfer | Vendor policy and cloud dependence |
We do not provide a live charger price list because dealer packages and installation requirements differ. A charger advertised at a low hardware-only price may cost more once a new consumer unit, a long cable run, CT wiring and network improvements are included. Conversely, paying more for OCPP functionality is unnecessary when a manufacturer’s own time-of-use and solar controls already meet the household’s requirements.
A practical buying checklist
Before placing an order, send the supplier or electrician these questions: (1) Which exact model, hardware revision and firmware will you install? (2) Is the Home Assistant integration built-in, community-maintained or only available via an external controller? (3) Which capabilities work with the internet disconnected? (4) Can a third-party system set charging current, start/stop sessions and read lifetime kWh? (5) Is OCPP configurable by the owner and what happens to the supplier’s cloud service afterward? (6) Does dynamic load management continue safely without Wi-Fi or Home Assistant? (7) Which CT or meter is required for solar charging and where will it be fitted? (8) Can the vehicle and supply use the advertised AC power and phase-switching features? (9) Does my energy provider support this exact combination for its managed tariff? (10) What is included in the installed quote and warranty?
Ask for a copy of the finished configuration and the installer’s handover documents. Those records matter when the internet router is replaced, the energy tariff changes or the house is sold.
Troubleshooting: five common EV charging automation problems
| Symptom | Likely causes | Sensible checks |
|---|---|---|
| Charger online, entities unavailable | Wrong account, network route, firmware or API permission | Check native app/web UI, integration logs and DNS |
| Current limit updates slowly | Cloud polling or charger-imposed update cadence | Confirm documented integration update interval |
| Solar mode imports electricity | Reversed CT, incorrect sign, stale grid reading | Compare grid meter, inverter and clamp direction |
| Charger ignores a schedule | Competing car, vendor, tariff and HA rules | Disable conflicting schedules one at a time |
| OCPP backend connects but cannot charge | Transaction, authorisation or smart-profile mismatch | Test support for required OCPP operations |
Do not interpret “offline” as evidence that the charger is electrically dead. A cloud dashboard can be unreachable while the charger continues safely charging. Conversely, an apparently healthy Home Assistant dashboard is not proof that the charger-side protection or load-management equipment is correctly commissioned. For any persistent fault, involve the installer and follow the manufacturer’s approved procedure.
Frequently asked questions
Is OCPP automatically the best option for Home Assistant?
No. A stable built-in local integration may be simpler, faster and more capable for a single domestic charger. OCPP is valuable where backend independence or coordinated control across devices matters, but you need compatible server software and proof that the required commands work on that charger.
Will a charger with an API continue working without the internet?
It depends on whether its local charging capability and scheduling functions remain operational, and what the default charger behaviour is when connectivity disappears. The presence of a cloud API is not proof of local control, nor is a local read-only API proof of adjustable charging current. Ask for a documented outage scenario.
Can an ESP32 replace an EV charger controller?
No. An ESP32 can help monitor an approved meter or read permitted network signals. It should not substitute for a certified charging controller, contactors, residual-current protection or a manufacturer-approved protective load-management device. This guide concerns smart integration with properly installed EV equipment.
Should I buy 22 kW rather than 7.4 kW for future-proofing?
Only if your supply, vehicle requirements, installation cost and future plans justify it. Many properties have single-phase supply, and many vehicles have lower AC charging limits. A 22 kW product may be compatible with lower-power service but does not create extra grid capacity.
Can Home Assistant calculate an EV charging bill accurately?
It can produce a useful estimate from properly measured kWh and the correct time-varying tariff. It cannot make a poor energy sensor accurate, and vehicle SOC is not equivalent to electricity bought from the grid. Use a suitable billing-grade or approved meter where formal reimbursement or contractual accuracy matters.
Is Home Assistant required to get cheap overnight or solar charging?
No. A charger with native time windows, an appropriate energy supplier’s managed charging service or a manufacturer-supported solar controller may already meet the need. Home Assistant becomes valuable when you want the charger to coordinate with wider home energy systems and wish to inspect the data yourself.
Final recommendation
If local Home Assistant operation is a firm requirement, start by evaluating OpenEVSE’s supported integration and go-e’s documented local interfaces, then confirm product suitability and installation support for your location. If you favour mainstream ease of setup and native tariff programmes, look at Wallbox or Ohme, accepting their cloud dependencies. If your main goal is solar-first charging, compare zappi’s supported solar ecosystem against the grid meter, battery and vehicle you already own. If you want simple local usage monitoring on a Gen 3 Tesla Wall Connector, its built-in Home Assistant integration is useful, but do not mistake it for a complete control API.
Make the purchase on verified functions for the exact hardware, installer competence, safe independent load management and the complete installed cost. Select one primary scheduler, confirm that charging survives network disruptions as intended and use Home Assistant to add value—not to carry the safety responsibilities of the charging equipment.
Sources and further reading
- <a href=”https://www.home-assistant.io/integrations/openevse/”>Home Assistant — OpenEVSE</a>: local integration capabilities, firmware requirements and energy entities.
- <a href=”https://go-e.com/en/solutions/for-customers/electric-car-charging-at-home”>go-e — Electric car charging at home</a> and <a href=”https://go-e.com/en/support/instructions”>go-e — Interface/API documentation links</a>: charging modes and published protocols.
- <a href=”https://www.home-assistant.io/integrations/wallbox/”>Home Assistant — Wallbox</a>: MyWallbox cloud route, settings and polling interval.
- <a href=”https://www.home-assistant.io/integrations/ohme/”>Home Assistant — Ohme</a>: supported products, cloud entities, tariff functions and energy-sensor limitation.
- <a href=”https://support.myenergi.com/hc/en-gb/articles/16864772981137-Setting-up-Open-Charge-Point-Protocol-OCPP”>Myenergi — Setting up OCPP for zappi</a>: supported models and backend requirements.
- <a href=”https://www.home-assistant.io/integrations/tesla_wall_connector”>Home Assistant — Tesla Wall Connector</a>: local Gen 3 telemetry and supported functionality.
- <a href=”https://openchargealliance.org/protocols/open-charge-point-protocol/”>Open Charge Alliance — OCPP versions</a>: OCPP 1.6, 2.0.1 and 2.1 scope.
- <a href=”https://docs.evcc.io/en/chargers/”>evcc — Supported chargers</a>: device-level integration and current-control capabilities.
- <a href=”https://www.gov.uk/guidance/regulations-electric-vehicle-smart-charge-points”>UK Government — Smart charge point regulations</a>: regulatory features and compliance principles.
Editorial note (October 2026): This comparison is based on publicly documented software behaviour and manufacturer guidance, not hands-on testing of every model. Firmware, cloud services, support policies and utility tariffs can change. No live product price is implied. All fixed electrical work and protective equipment should be specified and installed by a qualified EV charge-point professional.