Quick Summary (TL;DR)
OpenEVSE is the stronger choice for a technically competent Home Assistant user who needs local charging control, accessible firmware, and a programmable solar-surplus strategy. A complete, appropriately approved commercial wallbox is usually the better choice for a typical household that prioritises installer acceptance, clear warranty responsibility and straightforward regulatory compliance. Neither label is enough on its own: OpenEVSE sells components, kits and assembled products, and commercial chargers differ sharply in their cloud dependence and exposed controls.
Our buying recommendation: choose the specific charger variant, the installation jurisdiction and the verified Home Assistant control path together. Do not import a North American J1772/NACS OpenEVSE product and assume it is suitable for a UK Type 2 installation. Do not assume that assembling an electrically functional charger proves product conformity. A competent EV-chargepoint installer must approve the final electrical design and protection measures.
OpenEVSE vs a commercial EV wallbox: decision at a glance
| Buying question | OpenEVSE with compatible Wi-Fi firmware | Typical turnkey commercial wallbox | What really matters |
|---|---|---|---|
| Local Home Assistant access | Official integration over local network | Varies: cloud, local or OCPP | Confirm control entities, not only sensors |
| Hardware openness | Controller and gateway are documented for builders | Often proprietary hardware and service procedures | Long-term repairability versus supported service |
| Assembly required | Depends on kit versus assembled SKU | Normally factory assembled | Exact product, not brand name |
| Installation documentation | Builder, supplier and electrician must establish suitable complete assembly | Usually supplied as part of an approved product | Compliance for the actual market and installation |
| Warranty accountability | Varies by component/kit/assembled purchase | Usually one manufacturer/integrator plus installer | Written terms and local support |
| Solar diversion | Native Eco mode with suitable meter/MQTT input | Native on some products; external automation on others | Works during HA outage? |
| Network outage behaviour | Local control can remain available; test each firmware setup | Ranges from locally autonomous to cloud dependent | Charging fallback should not depend on HA |
| OCPP | ESP32AliExpress price gateway firmware documents OCPP 1.6J | Some provide OCPP, sometimes only in certain modes | Firmware, backend ownership and OCPP profile |
| Best fit | Engineer, integrator, test lab, supported local installation | Family household, landlord or grant-eligible project | Legal compliance before features |
This is not a contest between a dangerous DIY box and a perfect factory charger. It is a choice between different responsibilities. A fully assembled OpenEVSE product may be a sensible purchase in the market for which it was designed; a kit might be appropriate for a controlled engineering project; and a commercial wallbox can still be a poor Home Assistant purchase if all useful features are locked behind a service provider.
What OpenEVSE actually is — and why the exact SKU matters
OpenEVSE is an open charging-equipment platform that combines an EVSE controller, a control-pilot interface and protection/monitoring functions with a network gateway. Its ESP32AliExpress price Wi-Fi gateway can expose a web interface, HTTP/WebSocket data, MQTT and charging modes. The design allows an owner to monitor delivered energy, adjust the offered charging current, schedule sessions and integrate with a local automation system, subject to controller and gateway firmware compatibility.
The American OpenEVSE store distinguishes an assembled Advanced Series station from kit bundles, controller boards and accessory kits. Its published 48 A assembled products are supplied with North American SAE J1772 or NACS connectors and 208–264 V input specifications, not automatically a UK/EU 230/400 V Type 2 wallbox. A quoted North American price must never be used as an all-in installed British price. At the time of research the supplier listed $659 for an assembled 48 A J1772 product and $349 for a base kit, but availability, connector, shipping, tax and certification must be checked directly before purchase; these are snapshots, not a price guarantee. OpenEVSE product listing.
There is also the emonEVSE ecosystem from OpenEnergyMonitor, which has an OpenEVSE-based approach and documented solar-PV diversion. Do not assume every OpenEVSE controller, enclosure and cable sold by different suppliers has identical electrical ratings, protection arrangements or conformity documentation. Likewise, a product being open source does not mean every part of a finished high-power electrical appliance is user-serviceable without risk.
The buyer must distinguish five layers
- Chargepoint assembly: enclosure, terminals, cable/socket, contactor, thermal provisions and rated power path.
- Safety systems: earth-fault/residual-current provisions, contactor fault checks and appropriate upstream or integrated protection.
- EV communication: the IEC 61851 / SAE charging pilot, which advertises a current limit to the vehicle; it does not make the vehicle draw a guaranteed power.
- Network gateway: ESP32AliExpress price, firmware, HTTP, MQTT, web UI and optional OCPP.
- Site automation: Home Assistant, grid/solar meter, tariff data and house-level safety constraints.
An inexpensive controller board is not a substitute for the other four layers. Conversely, a boxed wall charger can implement all five internally, even if the owner cannot edit its source code.
Home Assistant integration: actual local capabilities
The official Home Assistant OpenEVSE integration communicates with supported OpenEVSE Wi-Fi firmware locally, without an internet connection or cloud account. It can discover the charger or connect by IP address, and provides charging state, power, current, session information, accumulated delivered energy and selected controls. The precise exposed entities depend on the firmware and integration version; review the device page rather than assuming every listed feature exists on an older ESP8266AliExpress price gateway.
For current firmware the charger can also use local MQTT: the OpenEVSE MQTT developer guide describes published state topics, commands, broker configuration and optional TLS. The architecture documentation explains that the ESP32AliExpress price gateway passes control to the separate charging controller and arbitrates commands from timers, external API clients and safety mechanisms.
| Integration path | Network dependency | Monitoring | Charging control | Typical limitation |
|---|---|---|---|---|
| Home Assistant official OpenEVSE | Local LAN | Current, power, charging state, energy | Current and state where supported | Compatible gateway firmware required |
| OpenEVSE MQTT | Local broker or configured remote broker | Configurable published topics | Configurable command topics | Broker security and topic design are your responsibility |
| OpenEVSE web/HTTP API | Local LAN | Detailed web status and API readings | Settings/commands subject to firmware | API changes across releases |
| Commercial Wallbox native HA integration | MyWallbox cloud | Charging and energy | Several controls, including pause/resume | Account/cloud dependency |
| Commercial Ohme native HA integration | Ohme cloud | Charger status and power | Supported charger functions | No native energy sensor in current HA documentation |
| Tesla Gen 3 Wall Connector native HA | Local LAN | Electrical telemetry and lifetime energy | Mainly monitoring in documented official integration | Not a substitute for a local current-command API |
| Other commercial OCPP-capable charger | Backend chosen by vendor/site operator | Depends on messages/profiles | Depends on OCPP version and vendor permissions | Home Assistant support is not guaranteed |
Two important distinctions: the official Wallbox integration reads data from the MyWallbox portal; the official Ohme integration is cloud polling. The Tesla Wall Connector integration is local polling but its published official entity list is primarily sensors. Local telemetry is not the same as local dispatch control.
Practical commissioning steps for OpenEVSE and Home Assistant
- Identify the exact OpenEVSE controller hardware, gateway and firmware; inspect the supplier’s compatibility and update guidance.
- Commission the charger electrically before using Home Assistant. A qualified installer should test its protective functions and document the approved circuit.
- Give the Wi-Fi gateway a reserved IP address; use a dedicated IoT network with access rules if possible.
- Open the charger web interface locally and confirm a connected vehicle, charge status and energy reading.
- In Home Assistant go to Settings → Devices & services → Add integration → OpenEVSE; accept discovery or enter its local host and authentication.
- Enable only the entities needed for your energy dashboard and automations. Compare reported current and energy to an independent meter.
- Test offline behaviour by deliberately disconnecting the router’s internet uplink while keeping the LAN active. Repeat with Home Assistant itself unavailable.
- Keep fixed charger maximum-current limits and other electrical protections configured outside the Home Assistant automation.
Never expose an unauthenticated charger API or MQTT command topic to the public internet. If you enable remote access, use a secured VPN or similarly controlled access path; treat any interface that can start charging or increase the current limit as a control-system endpoint.
Charging power, current limits and phase support
A charging station normally announces an upper current limit, and the onboard charger in the car then decides what it can draw. Power can be approximated by P = V × I for one phase, or P ≈ √3 × V(line-to-line) × I for a balanced three-phase supply. Real-world charging power changes with voltage, vehicle capability, charging efficiency, battery temperature and state of charge.
| Configuration | Illustrative current | Approximate AC input power | Buying implication |
|---|---|---|---|
| Single phase, 230 V | 6 A | 1.38 kW | Common minimum continuous AC charge pilot current |
| Single phase, 230 V | 10 A | 2.30 kW | Modest tariff/solar charging rate |
| Single phase, 230 V | 16 A | 3.68 kW | May suit constrained circuits after load assessment |
| Single phase, 230 V | 32 A | 7.36 kW | Common domestic UK wallbox class |
| Three phase, 400 V | 16 A/phase | 11.1 kW | Requires a suitable 3-phase charger and vehicle |
| Three phase, 400 V | 32 A/phase | 22.2 kW | Supply, installation and onboard vehicle charger must permit it |
The 48 A OpenEVSE Advanced Series sold in North America should not be described as a generic 48 A UK home wallbox. Different connector systems, earthing and fault-detection standards, overcurrent assumptions and single/three-phase requirements matter. Verify the complete equipment’s manufacturer documentation for the exact market.
A further subtlety is solar-surplus operation. At 230 V, the nominal 6 A floor means roughly 1.4 kW of available charging power before a conventional single-phase AC charging session can start. If your roof produces only 800 W of export, no amount of clever Home Assistant YAML can command a normal Mode 3 charger to send 800 W continuously through a 6 A minimum-current interface. Some systems blend grid power or pause until more surplus exists.
Solar surplus: OpenEVSE Eco mode versus built-in commercial features
OpenEVSE’s documented Eco mode uses a live grid import/export or solar-generation measurement to alter current and start or pause charging. In the OpenEnergyMonitor configuration the grid CT sign convention is important: import is positive and export negative. The emonEVSE setup guide describes an MQTT solar input, the nominal 6 A floor and practical vehicle compatibility caveats. Newer OpenEVSE gateway documentation also describes smoothing to avoid rapid start/stop oscillations.
A commercial solar-first wallbox such as a supported myenergi zappi can already provide dedicated solar behaviour with its own measurement hardware. Other models require a manufacturer-compatible CT, meter, accessory, cloud service or external controller. A Home Assistant integration does not necessarily make those systems equivalent.
| Solar-control criterion | OpenEVSE | Purpose-built commercial solar charger | HA-driven generic wallbox |
|---|---|---|---|
| Source of available power | Compatible grid/solar meter sent to EVSE | Supported vendor CT/meter | Any reliable HA sensor plus compatible control API |
| Control loop | Gateway Eco mode or external controller | Charger/brand logic | HA automation and integration |
| Internet outage | Can continue with LAN/meter feed | Product dependent; often local charging core | Cloud-only APIs may fail |
| HA outage | Eco mode may run independently of HA | Often independent of HA | Automation normally stops |
| Grid import/export sign | Must configure correctly | Depends on installer setup | Must normalise sensors explicitly |
| Battery priority | Needs deliberate configuration | Manufacturer-specific setting | Must coordinate priorities |
| Minimum rate | Vehicle/AC standard limits apply | Same fundamental current floor | Same fundamental current floor |
Worked surplus example
Suppose an inverter exports 3.5 kW while household demand is already included in the grid meter measurement. At 230 V, the charging pilot would nominally allow roughly 3,500 / 230 = 15.2 A. A cautious controller could choose 14 A (about 3.22 kW) to leave a buffer against cloud changes and measurement latency. The remaining margin is not guaranteed: a kettle, an induction hob or sudden PV cloud cover may reverse export into grid import before the next reading.
If the grid meter instead reports total solar production rather than surplus, diverting 3.5 kW could import electricity to cover the appliances already running. That error is common in DIY automation: generation, import/export and home consumption are distinct quantities. Where batteries are installed, decide explicitly whether the car should charge after the home battery reaches a threshold, in parallel with battery charging, or before the stationary battery.
Safe control strategy, without wiring instructions
Use a proven charger-side maximum limit as the hard ceiling. Feed Home Assistant or OpenEVSE a requested current bounded by that ceiling, use meter-quality checks and a no-data timeout, and preserve the charger’s independent electrical protection and fault handling. A charging command must never replace an RCD, appropriate PEN-fault arrangement, contactor weld detection, thermal cut-out or vehicle communications protocol.
For an engineering deployment, test the state transitions: export disappears, Wi-Fi drops, Home Assistant restarts, the EV refuses a low current, the EV is unplugged, a protective device operates, and the utility supply returns. The desired response to failed telemetry should be conservative; do not keep increasing charge current based on a stale export value.
Installation legality, protective devices and liability
This is the single most important reason many households should choose a complete commercial charger. Open source is not an electrical product approval scheme. You must evaluate the final installed assembly rather than the individual controller’s marketing page or a component’s CE/UKCA symbol. A kit enclosure with modified wiring, an imported product with the wrong connector, or a privately assembled unit may require additional conformity assessment, documentation and installer sign-off.
In Great Britain, government technical specifications refer to BS EN 61851, BS 7671, correct Mode 3 Type 2 arrangements, suitable markings and installation requirements for grant-eligible equipment. The Electric Vehicles (Smart Charge Points) Regulations 2021 apply to relevant private chargepoints sold in Great Britain, with defined exemptions; they address smart functionality and device requirements but do not replace the electrical installation rules. Government guidance explains which sales are in scope. Grants also have separate approved-product and installer conditions, and neither eligibility nor grant availability should be assumed.
An installer needs to assess earthing, protection against an open PEN conductor where relevant, protective conductor continuity, RCD/DC fault detection, overcurrent and short-circuit protection, equipment thermal ratings, cable sizing, diversity/load control, environmental exposure and notification/certification requirements. Some chargers integrate functions while others require appropriate upstream protection. Never assume an onboard GFCI/RCD description alone proves the finished installation meets the local rules.
| Safety/compliance checkpoint | Complete commercial wallbox | OpenEVSE kit or altered assembly | Ask for |
|---|---|---|---|
| Product documentation | Usually single manufacturer documentation | Must establish documents for final assembly | Exact model, serial, instructions and conformity evidence |
| Regional connector | Correct UK/EU Type 2 variant required | Kit parts may be SAE J1772/NACS | Connector, ratings and supply compatibility |
| RCD/DC leakage protection | Integrated or specified upstream | Depends on controller, sensors and assembly | Written protection design from installer |
| PEN-fault mitigation where applicable | Sometimes integrated | Requires separately justified solution | Earthing and open-PEN assessment |
| Ingress/thermal performance | Rated finished enclosure/product | Builder must verify complete assembly | IP rating in final installed orientation |
| Warranty | Manufacturer and installer terms | Component warranties may differ | Who handles fault, call-out, labour and replacement |
| Insurer/landlord acceptance | Usually easier to document | May face refusal | Written approval before ordering |
| Grant/smart-chargepoint requirements | Model-specific evidence | Do not assume eligibility | Current scheme and regulatory status |
For installations outside Great Britain, consult local requirements and certified equipment for that country; the GB rules should not be copied as universal law. For UK readers, a self-built charger should not be connected to a household EV circuit merely because its controller powers up on a bench.
OCPP: useful, but not automatically plug-and-play
OCPP is a communications protocol between a chargepoint and a management backend. OpenEVSE ESP32 gateway documentation lists OCPP 1.6J capabilities in supported firmware. A commercial charger may advertise OCPP yet restrict the endpoint, certificate settings, local mode or operator selection. Conversely, a local Home Assistant API may already provide everything needed for one household without running an OCPP central system.
| Question | Local OpenEVSE API | OCPP 1.6J | Proprietary commercial cloud API |
|---|---|---|---|
| Need a backend server? | No, HA talks to charger | Yes, a compatible central system is normally involved | Vendor hosts infrastructure |
| Can it work without public internet? | Yes on suitable LAN | Potentially, if local backend permitted | Usually not for cloud functions |
| Does it guarantee current limits? | Documented API supports control | Only if implementation supports profile/commands | Vendor/model-specific |
| Does HA provide every feature natively? | Official OpenEVSE integration exists | OCPP controller often community/add-on integration | Native integration varies |
| Best for a single DIY home | Often simplest | Useful for backend research/multicharger platforms | Easiest if vendor already covers tariff features |
For readers choosing OCPP, check connection mode, whether the charger can connect to a local WebSocket backend, whether its OCPP backend can be changed by the owner, transport/security setup and actual Smart Charging message support. Advertising OCPP 1.6 does not promise that every optional smart-charging profile is implemented. Future-protocol support, including 2.0.1, should be confirmed in the specific firmware rather than inferred from marketing material.
A realistic total-cost comparison
The cheapest shopping-cart price is rarely the cheapest installed EV charger. A builder may pay separately for a contactor, enclosure, cable, protected supply, meter, DIN accessories, weatherproof glands, testing, electrician time, replacement parts and an installer willing to take responsibility. A commercial box may cost more at checkout but include those assemblies and simpler after-sales responsibility.
The US OpenEVSE store currently shows different prices for component kits and assembled J1772/NACS stations, but these prices cannot be used as UK Type 2 installed-price comparators. For a decision in Britain obtain two written installed quotations for product variants suitable for that market.
| Cost element | OpenEVSE kit pathway | Assembled/turnkey commercial pathway | Hidden-cost warning |
|---|---|---|---|
| EVSE hardware | Kit/components | Finished charger | Does the kit include all safety parts? |
| Suitable connector/cable | Must be specifically selected | Bundled or socketed option | Type 2 vs J1772/NACS |
| Consumer unit/circuit work | Required where necessary | Required where necessary | Same electrical labour may dominate |
| Load-management meter/CT | Often third party | Vendor accessory or integrated | Extra parts and calibration |
| Network hardware | Wi-Fi gateway, possible MQTT broker | Wi-Fi/Ethernet/cellular vendor plan | Ongoing data/connectivity costs |
| Verification/compliance | Additional design/test/evidence possible | Model documentation typically available | Insurer, landlord, electrician acceptance |
| Support/repair | Owner/integrator plus component vendor | Manufacturer/installer | Down-time and call-out charges |
| Warranty | Terms depend on exact parts and SKU | Often finished product with service terms | Replacement labour may be excluded |
Five-year illustrative ownership model
Consider two hypothetical completed installations, with all figures purely illustrative in pounds, not quotations or advertised OpenEVSE UK prices. They include installer work and expected service/maintenance allowances, but omit electricity energy itself because both systems serve the same EV.
| Item | Supported DIY-style pathway | Turnkey commercial wallbox |
|---|---|---|
| Hardware and required accessories | £700 | £850 |
| Professional installation / testing | £500 | £400 |
| Additional design/commissioning | £250 | £0 |
| Five-year parts/service allowance | £220 | £120 |
| Five-year recurring cloud or data fee | £0 | £0 |
| Illustrative five-year spend | £1,670 | £1,370 |
This does not show that commercial charging is always cheaper. It shows that an open design can cost more once the full cost of responsible compliance and commissioning is counted. The outcome flips if you already have an acceptable, assembled OpenEVSE product, qualified engineering support and a suitable meter, or if a commercial charger needs an expensive proprietary management subscription. Check offers and terms at the date of purchase.
When smart charging pays for itself
Suppose your car charges 2,500 kWh each year. Shifting 1,800 kWh from a 28 p/kWh peak rate to a 10 p/kWh off-peak rate produces 1,800 × £0.18 = £324/year of gross electricity-bill savings, before any tariff fees or efficiency effects. The saving comes from the tariff and scheduling behaviour, not automatically from buying OpenEVSE. A commercial charger that already supports the same schedule may capture the same amount without extra automation.
For solar charging, the real avoided cost is usually the import unit price minus the export payment you give up, adjusted for AC charging losses and when generation is actually surplus. At 28 p/kWh import and 12 p/kWh export, 1,000 kWh redirected from genuine exported energy gives an illustrative £160 gross annual benefit, not £280. If your dynamic import tariff is temporarily cheaper than the value of export, forcing solar charging can even lose money.
Reliability: what happens when things go offline?
A robust household charging installation should have a clear hierarchy. Protective devices and charging-pilot logic are hard requirements; household current limit and commissioning settings come next; app schedules and clever tariff automations are optional optimisations. Home Assistant must never be a single point of failure for overcurrent or leakage protection.
| Failure or event | Desired safe behaviour | Verification method |
|---|---|---|
| Internet outage | Local charging and essential protective functions remain | Remove WAN connectivity, keep LAN available |
| Home Assistant server down | Hardware charging remains safe at a configured fallback | Stop HA without changing charger power |
| Solar-grid meter data stale | Solar-divert logic stops relying on stale surplus | Disconnect meter feed safely at network level |
| Wi-Fi AP restart | Reconnection is predictable, no uncontrolled rate increase | Restart AP during a test session |
| Overnight price API missing | Use clear fallback schedule or user decision | Disable price integration in test |
| Car connected but not charging | Error distinguishable from normal scheduled wait | Check charger status + vehicle indication |
| Vehicle disconnect | Contactor and session states behave correctly | Qualified commissioning procedure |
| Protective device operates | Charger reports fault and requires proper investigation | Qualified electrician-only testing |
The key difference between hardware safety and software scheduling must remain visible in any dashboard. A Home Assistant automation can request a low current during a price spike. It must not defeat the device’s installed maximum circuit limit or report a successful safety test based merely on a green dashboard icon.
Which option should you choose?
Choose OpenEVSE when
- You genuinely need local control, can verify the official Home Assistant integration on your firmware and want to avoid cloud-based charger commands.
- You are comfortable with firmware, API security, MQTT or Ethernet gateways and test-driven automation.
- You can purchase an appropriate complete assembly for your location, or you have an authorised route to design, test and approve a custom unit.
- You want to integrate detailed grid import/export measurements, solar-divert modes and an independently managed local network.
- You value repairability and accept that long-term owner support can be part of the cost.
Choose a complete commercial wallbox when
- The charger is for a normal home with multiple drivers who need it to work without ongoing experimentation.
- You want a straightforward installed package with verified product conformity, a clear installer, warranty and support route.
- You need grant eligibility, landlord/insurer acceptance or a particular national Type 2 specification.
- A vendor-supported feature such as zappi solar charging or Ohme smart tariffs already solves the problem.
- You prefer a professionally supported commercial local-access model rather than a kit, even if that means paying more upfront.
Consider a third route: open integration, commercial safety envelope
The choice is not necessarily OpenEVSE or cloud-locked hardware. Some properly certified commercial products expose local Modbus, local HTTP, MQTT, OCPP with owner-selectable backend, or manufacturer-supported local interfaces. For a professional home installation, a certified wallbox with documented local control can be the best combination of installer acceptance and automation ownership. Verify the exact SKU and firmware — not merely a logo on a compatibility chart.
Pre-purchase checklist: the questions that prevent expensive mistakes
- Which national market and connector? Write down Type 2/Type 1/NACS, supply voltage, phase count and approval documents.
- What does the electrician approve? Obtain written agreement on charger, cable, earthing, RCD/DC fault protection and any needed open-PEN solution before ordering.
- Which precise HA integration? Ask whether it is built-in, community-maintained or based on a separate MQTT/OCPP controller.
- Which commands work offline? List the exact start/stop and current-setting entities available with internet disconnected.
- What meter is required? Confirm sign convention, CT ratio, phase support, location and who configures it.
- Where is the permanent maximum current set? Check it is independent of HA and protected against accidental API changes.
- Who owns the cloud account or OCPP backend? Check whether you can move operator without losing basic smart functions.
- How will firmware update? Require rollback/recovery instructions, update support duration and backup configuration.
- What happens when the gateway or broker fails? Test failure modes during commissioning rather than relying on a brochure.
- What costs continue? Count subscriptions, cellular data, accessories, electrician return visits and repair labour.
Troubleshooting and common misconceptions
| Symptom or claim | Likely cause / reality | First sensible check |
|---|---|---|
| OpenEVSE not discovered by Home Assistant | No Wi-Fi gateway, unsupported firmware or network discovery blocked | Visit local charger web UI and use manual IP setup |
| Charger reports 0 W despite a connected cable | Car is delaying charging or charger is waiting | Vehicle schedule, pilot state, authorised session |
| Automation keeps importing grid power | Solar-generation sensor used instead of surplus meter | Grid import/export sign and CT positioning |
| Charging oscillates every minute | No smoothing/hysteresis or solar fluctuates near 6 A floor | Divert control strategy and minimum dwell times |
| Charger can be monitored but current cannot be adjusted | Integration exposes sensors only, or vendor API permissions differ | Supported entity list and firmware documentation |
| OCPP advertised but local OCPP fails | Vendor fixes backend, optional profile missing or certificates wrong | Installer documentation and backend connection settings |
| A kit carries a CE or UKCA logo on a part | Component marking is not finished-device approval | Final assembly technical documentation |
| Device keeps charging if HA stops | May be normal fallback, not necessarily a defect | Installer-approved maximum and fallback settings |
| Energy dashboard overstates consumption | Whole-home meter plus EV meter counted twice as grid import | Add EV as individual device, not another grid supply |
Frequently asked questions
Is OpenEVSE an officially supported Home Assistant integration?
Yes. Home Assistant maintains an OpenEVSE integration for a compatible network-connected OpenEVSE Wi-Fi charger. It uses local communication; older gateway firmware may need updating. Check the published entity list for the precise version you will operate.
Does OpenEVSE require the cloud?
Not for the documented local integration. It can work over a local network; some optional external data, remote services or smart tariff arrangements may separately depend on internet access. Local does not automatically mean all MQTT brokers and external feeds are local — you decide where they run.
Is an OpenEVSE kit legal to install in the UK?
There is no simple brand-level yes/no answer. The finished chargepoint and installation must meet applicable product, electrical and sales rules. A component kit is not automatically a compliant UK household appliance. Consult an appropriately qualified local installer and obtain documentation before purchasing or energising equipment. The published North American J1772/NACS units should not be assumed suitable for a UK Type 2 charging installation.
Can OpenEVSE divert solar power without Home Assistant?
Yes, supported OpenEVSE/emonEVSE Eco mode can operate from appropriate meter data sent to its gateway/MQTT input without needing Home Assistant to run the control loop. That does not remove the need for robust and correctly calibrated grid measurements.
Can Home Assistant make any charger solar-aware?
Only if a usable control interface exists. A telemetry-only integration cannot alter the car’s charging current. Even with a writable command, the minimum 6 A AC charging threshold, battery interactions, latency and connection reliability still limit performance.
Is OCPP better than local MQTT?
Neither is universally better. OCPP can be valuable for independent backend management, multiple chargers and operator interoperability. Local MQTT or HTTP is often simpler for one OpenEVSE-equipped household with Home Assistant. OCPP support must be verified for the exact firmware, including the specific optional smart-charging features needed.
What is the best wallbox for a typical UK household?
Prefer an appropriately approved, professionally installed Type 2 charger with clearly documented protection, warranty and a control path matching your needs. If no-cloud Home Assistant automation is essential, specifically shortlist commercial chargers with verified local APIs and the relevant supported firmware, rather than importing a charger solely because its hardware is open.
Final verdict
For Home Assistant automation flexibility, OpenEVSE is a compelling technical platform: local firmware, a documented official integration, MQTT and solar-divert features are real strengths. For a typical domestic installation, certified complete commercial hardware generally offers a simpler route through installation, ongoing support and product accountability. The most attractive middle ground is often a professionally approved charger that also gives its owner a documented local API.
Buy the electrical installation first, and the Home Assistant feature list second. A five-minute demo of a charging-current slider is not a substitute for a safe, supportable high-power appliance.
Official documentation and references
- Home Assistant: OpenEVSE integration — local connection, features, configuration and diagnostics.
- OpenEVSE: ESP32 Wi-Fi MQTT developer guide — commands, topics and version requirements.
- OpenEVSE: ESP32 firmware architecture — arbitration, protections, logging and integrations.
- OpenEnergyMonitor: emonEVSE setup and Eco mode — solar measurement and surplus control.
- OpenEVSE official product catalogue — distinguish kits, assembled products and market-specific connectors.
- Home Assistant: Wallbox, Ohme and Tesla Wall Connector — compare actual connection paths.
- UK Government: Residential chargepoint minimum technical specification.
- UK Government: Smart chargepoints regulations guidance.
- UK law: Electric Vehicles (Smart Charge Points) Regulations 2021.
Related reading on esp32.co.uk
- ESP32 Modbus Energy Meter with Home Assistant: SDM120 / SDM630 Guide — building reliable meter telemetry.
- ESP32 Energy Monitoring Methods Compared: Pulse Meter vs CT Clamp vs PZEM vs Modbus — selecting appropriate measurement technology.
- Home Assistant Energy Dashboard Troubleshooting for ESPHome — avoiding incorrect power and energy readings.