Quick Summary (TL;DR)
Choose myenergi zappi when automatic solar-surplus charging is the priority; choose a compatible Wallbox Pulsar Plus when the official Home Assistant integration and remotely adjustable charging settings matter most; consider Easee when compact hardware, charger sharing and dynamic load balancing fit the property. None of those conclusions means the three products offer interchangeable integrations. The native Home Assistant Wallbox integration polls MyWallbox’s cloud API. Popular zappi and Easee Home Assistant integrations are community-maintained or partner/API-based, and their exposed controls can change with firmware and account access. A charger advertising OCPP or a Wi-Fi connection is not automatically a locally controllable Home Assistant device.
Our practical recommendation: shortlist the precise regional hardware model, ask the installer for the actual CT/meter and protective-device specification, then check the integration’s connection path and control entities before buying. zappi v2.1 models with built-in Wi-Fi can use OCPP 1.6J through myenergi’s cloud gateway, but that is not direct local OCPP. Wallbox’s built-in Home Assistant integration depends on its cloud portal. Easee’s cloud API is documented; whether a particular local-Wi-Fi approach exposes the control you need is a different, model-specific question. For an off-grid-first, no-cloud specification, none of these should be treated as an assured drop-in local controller without further verification.
Who should buy which EV charger?
| Household priority | Best starting point | Reason | Verify before paying |
|---|---|---|---|
| Solar-first home with PV | myenergi zappi | ECO and ECO+ charging behaviour built into the charger | Correct CT positioning, battery interaction and model/firmware |
| Easy Home Assistant controls via a built-in integration | Wallbox Pulsar Plus, supported regional version | Official Home Assistant Wallbox integration includes monitoring and selected controls | MyWallbox credentials, Wi-Fi, integration permissions, exact unit |
| Small enclosure, multiple chargers, load balancing | Easee, appropriate UK/EU variant | Compact family and coordinated site/circuit features | Country-approved variant, Easee Equalizer requirement, API access |
| Home Assistant automation with no vendor cloud | None automatically qualifies | Native Home Assistant support and native local control are separate questions | Require a demonstrated supported local endpoint or OCPP architecture |
| UK single-phase domestic home | zappi, compatible Pulsar Plus or Easee One | All have regional domestic configurations | Installer’s 7.4 kW design and full electrical quote |
| European three-phase property | Regional zappi, Wallbox or Easee Charge Max/Up, as available | Three-phase options exist in selected ranges | Phase capability, onboard vehicle limit and current EU range |
This is a product selection guide, not a laboratory review. We have not carried out side-by-side power measurements, tested fault recovery on all firmware revisions or obtained installation quotes for a particular address. Where a feature is controlled through a third-party project, do not mistake its documentation for a commitment from the hardware manufacturer.
Three chargers, three different integration philosophies
A smart EV charger operates at two levels. The EVSE itself negotiates permissible current with the vehicle and enforces electrical protection or an installer-defined limit. The smart energy system schedules charging, responds to solar production or tariffs and displays information in Home Assistant. If the smart side fails, the EVSE’s protections must remain effective; a Raspberry Pi should never become the sole safety or load-protection mechanism.
zappi: its stand-out feature is the appliance-level ECO/ECO+ strategy. It monitors the home’s import/export using correctly configured CTs and adjusts or suspends charging without relying on Home Assistant to sample power every few seconds. Wallbox: the Wallbox app and service are central to the supported consumer experience; Home Assistant’s built-in integration uses that portal and can expose charging power, price and solar controls on supported units. Easee: the manufacturer offers charger-site management, firmware-controlled features, cloud APIs and load balancing with its own site/electrical equipment. Local Wi-Fi communication should not be assumed equivalent to a complete, officially supported local Home Assistant API.
| Characteristic | myenergi zappi | Wallbox Pulsar Plus | Easee household charger |
|---|---|---|---|
| Primary attraction | PV-diversion features and energy ecosystem | Mainstream charger with native HA integration | Compact unit, multi-unit load management |
| Home Assistant built-in integration | Do not assume; common routes are community custom integrations | Yes: Wallbox | No equivalent official core Easee integration confirmed for this comparison |
| Built-in HA connection path | Community integration usually uses myenergi service/API | Cloud polling: MyWallbox Portal | Community/partner cloud-API path is common |
| Manufacturer cloud needed for those routes | Generally yes for the listed approaches | Yes | Generally yes for cloud integrations |
| OCPP | zappi built-in-Wi-Fi v2.1 models: 1.6J via myenergi cloud gateway | Depends on exact Pulsar Plus version, region and firmware | Depends on model, management arrangement and provider; confirm in writing |
| Solar behaviour | Native ECO / ECO+ | Solar Charging features where supported with required metering | May require Equalizer, vendor features or external controller depending on model |
| Load balancing | Compatible myenergi CT/system design | Power Boost / suitable meter where supported | Easee site/circuit balancing and Equalizer options |
| Best technical question | Does ECO+ cooperate properly with my home battery? | Which exact controls are available in my HA entities? | What will still work without Easee Cloud? |
What ‘native’ means in this table
A built-in Home Assistant integration is shipped with Home Assistant and maintained through its integration lifecycle. A community integration is installed and updated separately, often through HACS. A manufacturer API can be documented and official while the Home Assistant connector using it remains a community project. A local interface actually operates across the LAN without dependence on a vendor backend. These four claims are not synonyms. The Home Assistant Wallbox page explicitly classifies its integration as Cloud Polling. See the official documentation linked in the sources section.
myenergi zappi: the solar-first option
zappi’s usefulness comes from treating surplus PV as a charging signal rather than merely supplying a timer. The manufacturer’s ECO mode adjusts charging to use surplus generation but can fill a shortfall from the grid, whereas ECO+ can pause when grid import exceeds the configured policy. On a single-phase AC charge point, the typical minimum EV charging current is 6 A, approximately 1.4 kW at 230 V. Below this, the charger cannot endlessly ramp current down like a small resistive load; it must import some electricity or pause as configured.
| Charging mode | Behaviour | Practical use | Caveat |
|---|---|---|---|
| FAST | Charge at the permitted maximum | Guaranteed charge before leaving | May use expensive grid electricity |
| ECO | Modulates charge, allowing grid support | Smooth charging through passing clouds | Not necessarily 100% solar-supplied |
| ECO+ | Can pause charging when solar surplus is insufficient | Maximising self-consumption | Starts/stops can depend on vehicle behaviour and minimum-green settings |
| Boost/schedules | Add a required charge during selected periods | Low-tariff overnight top-up | Check interaction with automation and departure targets |
CT positioning determines whether these modes behave sensibly. A clamp on the wrong conductor can make export appear as import; a clamp around both live and neutral can measure almost zero. With batteries and multiple inverter feeds, it is essential to understand whether zappi sees net grid flow or the wrong part of the system. Ask for a CT-placement diagram and a commissioning test in which a known load is switched on and the measured import rises in the correct direction. Leave installation and any mains-board work to a qualified electrician.
zappi and Home Assistant
As of October 2026, do not assume a standard Home Assistant installation contains a fully supported, built-in zappi integration. Community myenergi projects exist and can expose sensors and some controls using the myenergi service. Verify each project’s currently supported firmware, authentication, usage limits and maintenance history before relying on it. A ‘charge power’ sensor is not a promise of reliable remote pause/resume or current control.
myenergi documents OCPP 1.6J for later zappi units with built-in Wi-Fi, with the myenergi account, current firmware and an OCPP provider required. The manufacturer’s own material describes this as cloud-to-cloud. That is an important distinction for enthusiasts hoping to run a fully offline OCPP controller on Home Assistant. If your requirement is complete LAN independence, test it or obtain written confirmation before treating zappi as suitable.
Wallbox Pulsar Plus: easiest built-in Home Assistant path
Home Assistant’s official Wallbox integration is unusually clear about both its strengths and dependency. It retrieves charger information from MyWallbox Portal and offers charging monitoring plus selected settings such as Charging Power, Energy Price, Solar Charging and Pause/Resume where the connected model and account permit them. It can feed electricity usage into the Energy dashboard. It requires suitable portal account permissions; Home Assistant’s documentation states admin credentials are needed for proper operation.
Configuration normally starts at Settings → Devices & services → Add Integration → Wallbox, followed by the MyWallbox account. If the charger appears in the manufacturer’s app but not Home Assistant, check permissions and portal availability before chasing local firewall rules. If the manufacturer’s cloud is unavailable, the integration may be unable to update or send settings, even though the charger itself may continue charging according to its retained configuration.
Pulsar Plus is a family name, not an exact international specification. UK/EU and North American products differ in voltage, cable and connector arrangement, and certification. The North American Pulsar Plus OCPP documentation and the Pulsar Plus ‘e’ firmware release notes cannot be used as proof that every UK Pulsar Plus has identical OCPP abilities. Ask for the full part number, installation region, firmware and current supported OCPP profiles before planning a migration to a third-party charge-point-management system.
Wallbox solar and dynamic power
Wallbox markets features such as Solar Charging and Power Boost, but their availability depends on the charger version, market and supporting meter. For a solar home, buying only the charging head may be insufficient: ask whether the quote includes the supported meter, current sensors, any communication cable, commissioning and the correct portal feature activation. Request a demonstration that (1) household import/export is measured with the correct sign, (2) the charger respects the supply limit, and (3) cloud loss does not defeat the device’s standalone electrical protection.
| Wallbox feature | Home Assistant / hardware implication | What to verify |
|---|---|---|
| Energy monitoring | Often exposes session and consumption data via portal | Are figures per session, cumulative, or both? |
| Remote pause/resume | Native HA control on supported accounts | Does your specific firmware expose it? |
| Charge current/power | May be adjustable from native integration | What minimum/maximum current can the device accept? |
| Solar Charging | Native control entity is documented | Is the required Wallbox meter included? |
| Power Boost | Dynamic load management depends on installation hardware | Which meter and supply limit are certified for this model? |
| OCPP | Varies across charger family and regional firmware | Can the specific unit connect to your intended backend? |
Easee: compact site-aware charging, with market-specific caveats
Easee is attractive where size, appearance, multiple sockets and coordinated current sharing count. Easee One is a UK-oriented domestic product with up to 7.4 kW single-phase charging. The manufacturer documents Wi-Fi/cellular connection, a flexible tethered/untethered arrangement and load-balancing capabilities. European line-ups have different names and power options: Charge Up, Charge Max, Charge Core and Charge Pro should never be treated as interchangeable by market or metering certification.
A particularly important September 2026 manufacturer announcement states that, from 1 January 2027, Easee plans to sell Charge Max and Charge Pro as its only charger models in EU markets; Charge Up and Charge Core EU sales are scheduled to be phased out, while the UK is explicitly unaffected. An EU shopper choosing a Charge Up in late 2026 should ask about availability and support; a UK Easee One buyer should not interpret the EU change as a UK recall or sudden loss of service. Existing supported installed products are a separate question from future retail availability.
Easee documents a cloud REST API, and advises partners to prefer its real-time streaming interfaces where appropriate instead of hammering REST endpoints. Some vendor materials also mention local Wi-Fi capabilities. However, a manufacturer mentioning a local Wi-Fi interface does not establish that a maintained, official Home Assistant local integration can read and alter all charging settings. Check the exact connector, authentication, rate limits and entitlements. For several households using shared electrical capacity, evaluate Easee’s own controller/Equalizer arrangements on their merits and regard Home Assistant as a supervisory layer.
| Easee model or market | Why it matters | Buying action |
|---|---|---|
| Easee One (UK home) | Single-phase domestic option, up to 7.4 kW | Obtain UK-specific certification and full installed quote |
| Charge Up / Core (EU) | EU range transition announced for late 2026 | Ask supplier about availability, service and replacement model |
| Charge Max (EU) | MID-certified metering and EU home positioning | Confirm whether billing/reimbursement needs MID |
| Charge Pro (EU) | Commercial and multi-tenant positioning | Compare back-office requirements and permissions |
| Equalizer or coordinated site balancing | Load management is not merely a Home Assistant script | Include meter/accessories and commissioning in quotation |
Local control, cloud control and OCPP: which layer actually talks to which?
Many comparisons mix up Wi-Fi, OCPP and Home Assistant. A charger can use Wi-Fi only to reach a cloud, while a different product may expose a local HTTP endpoint. OCPP is a protocol between charge point and charge-point-management system, not the EV-to-charger signalling protocol and not inherently a Home Assistant service. To use an OCPP-capable charger independently, you need both a suitable charge point configuration and a compatible management server. Proprietary myenergi gateway arrangements may still run through vendor infrastructure.
| Route | Typical data flow | Works with vendor cloud offline? | Technical trade-off |
|---|---|---|---|
| Native HA Wallbox | Charger → MyWallbox → Home Assistant | No for live HA integration | Easy supported setup; cloud dependency |
| Community zappi connection | Charger → myenergi service → custom HA component | Generally no for cloud-based connector | Useful ecosystem sensors; community maintenance |
| Community Easee cloud connector | Charger → Easee Cloud API → HA component | No for that connector | Broad possibilities; API access and limits |
| Vendor OCPP gateway | Charger → vendor backend → OCPP platform | Usually no for the gateway | More automation choices; extra backend complexity |
| Verified direct local API | Charger → household LAN → controller | Potentially yes, if truly local | Requires exact model/firmware support |
| External sub-meter | Dedicated CT/Modbus meter → HA | Yes if locally read | Independent energy measurement, not EVSE control |
A separate meter can provide reliable, local kWh consumed by the EV circuit, even when the charge point’s own cloud is down. It cannot safely replace the EVSE control circuit. For a technical introduction see our published ESP32 Modbus energy meter guide and ESP32 CT-clamp monitoring guide. Do not count the EV circuit both as a separate source and as an added load on top of the whole-home meter in Home Assistant’s Energy dashboard.
Regional hardware: UK, mainland Europe and North America
In a UK domestic installation, the common charging limit is 32 A single-phase, which at 230 V is approximately 7.36 kW. Three-phase EVSEs in suitable European installations may supply up to 11 or 22 kW, but only if the property, vehicle onboard AC charger and approved protection permit it. The car—not the wallbox marketing—is frequently the limiting factor. A 22 kW charger connected to a car with an 11 kW AC onboard charger generally will not charge it at 22 kW.
For UK installations, the electrician must assess supply capacity, earthing, open-PEN protection where relevant, RCD/RCBO arrangement, overcurrent protection, communication accessories, cable route and BS 7671 requirements. Applicable GB smart-charge-point regulations are about the sold product and its compliance, not evidence that a specific Home Assistant setup has a working local API. The government guidance also explains that charger-grant eligibility is scheme- and model-specific; never infer an automatic grant from an advertised ‘smart charger’.
| Region | Important checks | Common trap |
|---|---|---|
| Great Britain | GB compliant charger, supply rating, smart-charge rules, installer declaration | Importing an EU variant without UK documentation |
| EU single phase | Country-specific approval, connector, phase/load limits | Assuming every EU 22 kW model suits a 1-phase supply |
| EU three phase | Vehicle AC limit, three-phase CT/meter and supply contract | Expecting 22 kW from an 11 kW vehicle |
| North America | UL/CSA approval, NACS/J1772 variant, 120/240 V wiring rules | Using US Pulsar documentation for a UK Pulsar Plus |
| Shared property | Load management, user roles, billing and metering | Assuming cloud account owner has installer permissions |
Solar-surplus charging: what actually wins?
For a PV homeowner, the first question is whether you want the charger to track surplus itself or whether Home Assistant will coordinate multiple devices. zappi’s ECO/ECO+ modes are a compelling route for the first goal. Wallbox’s solar capability can also be effective with the correct hardware. With Easee, confirm the chosen device, energy meterAliExpress price and automation platform support the specific start/stop or current-adjustment behaviour you expect.
Example: solar output is 4.2 kW and the house consumes 1.0 kW excluding the EV. There is roughly 3.2 kW net solar surplus, so a single-phase EV can often charge near 3.2 kW rather than importing from the grid, subject to measurement, efficiency and control lag. Ten minutes later a kettle and oven add 2.5 kW; surplus falls to 0.7 kW. A correctly configured ECO+ policy may pause because that is below the typical ~1.4 kW minimum. A crude Home Assistant rule that merely ‘switches on at noon’ will import grid electricity instead.
Do not infer the financial outcome from a solar percentage alone. Suppose 8 kWh of charging would otherwise have earned £0.10/kWh exported and avoided £0.28/kWh imported electricity. The illustrative value of shifting that energy into the EV is 8 × (£0.28 − £0.10) = £1.44, before charging losses and any tariff-specific fees. With a very favourable export tariff the benefit shrinks. With battery storage present, prioritising car charging versus charging the home battery becomes a genuine optimisation choice rather than a blanket ‘zero export’ objective.
Solar commissioning checklist
- Confirm a qualified installer has tested protective devices and the charging circuit.
- Verify grid CT direction with a known household load and with real export.
- Check that PV, battery and EV meters do not double count the same electrical flow.
- Test low-surplus, high-surplus and passing-cloud periods with the vehicle attached.
- If relevant, verify battery reserve and charging priority under different tariffs.
- Disconnect the broadband connection deliberately and observe the charger’s safe retained policy; restore it before completing commissioning.
- Confirm overnight departure-charge scheduling is possible even when solar generation is zero.
Home Assistant installation paths and what to test
For Wallbox, use the official integration setup page in Home Assistant, with MyWallbox administrator permissions and the charger visible in the portal. Check that the expected charging-power and pause/resume entities actually appear; do not copy an automation based on someone’s entity IDs. Verify whether the state is updated quickly enough for your purpose. A cloud polling integration is normally unsuitable as the sole fast electrical load-shedding safeguard.
For zappi, choose a current, maintained Home Assistant community integration only after reading its documentation, checking your zappi and hub generation and verifying that your myenergi account can authenticate. Start read-only, inspect the exposed measurement entities, then test supported control changes with a vehicle parked safely. If evaluating OCPP, note that the myenergi documentation requires a supported Wi-Fi unit, a myaccount registration and a backend agreement; its cloud-gateway architecture means that a ‘local OCPP server’ cannot be assumed to eliminate internet dependence.
For Easee, establish whether your use case can be satisfied by the charger’s own Easee app or Equalizer. If Home Assistant integration is required, examine the connector’s release frequency, vendor API terms, handling of reauthentication and behaviour after firmware upgrades. Implement conservative update intervals and back-off; Easee’s official developer documents recommend streaming APIs for real-time work rather than rapid polling. A custom integration that successfully reads the current does not automatically prove it can set the current without conflicting with site load balancing.
A practical automation priority order is: electrical and charger protection → site/load balance limit → minimum departure charge → tariff optimiser → solar preference → dashboard cosmetics. Home Assistant should request an allowed target, and the EVSE must remain responsible for enforcing its own safe limits. Do not disable the manufacturer’s load-management feature because an automation seems more clever.
Whole-project buying cost: ask for an installed-system quote
Sticker prices for the charging head do not compare like with like. An installer might include one CT but quote another meter, an upgraded consumer unit, long outdoor cable runs or an additional data connection separately. Regional prices change with promotions, labour and tax. We therefore do not invent a current nationwide ‘fully installed’ number for each charger. Instead, use the quote template below so competing installers price the same scope.
| Cost item | myenergi zappi | Wallbox Pulsar Plus | Easee |
|---|---|---|---|
| Charger and region-specific hardware | Ask for exact zappi model code | Exact Pulsar Plus SKU and connector | Exact One / Up / Max SKU |
| Tethered cable or Type 2 lead | Confirm length and fit | Confirm tethered/untethered | Check detachable/lockable lead option |
| Grid/solar measurement | CTs and any hub/harvi parts | Compatible Power Boost/Solar meter | Equalizer/meter if needed |
| Installation and testing | Circuit and protection, commissioning | Circuit and protection, commissioning | Circuit and protection, commissioning |
| Network connectivity | Wi-Fi/Ethernet location and setup | Strong charger Wi-Fi coverage | Wi-Fi or cellular coverage |
| Tariff or third-party services | Account/OCPP operator conditions | Wallbox portal or external EMS | Cloud account/partner service |
| Maintenance | Firmware and installer support | Portal updates, firmware and app | Firmware, API access and installer support |
| Unexpected civil work | Cable routing or trench | Cable routing or trench | Cable routing or trench |
Worked lifetime-price comparison (illustrative, not quotations)
A simple framework for a five-year comparison is installed price + accessories + subscriptions + likely service costs − demonstrable energy savings. Assume Option A costs £1,050 installed, Option B £1,150 and Option C £1,000 (fictional illustrative prices). Suppose an additional third-party software service costs £3/month for one option: over 60 months that is £180, before inflation. If a more capable solar mode saves a verified extra 250 kWh/year of otherwise imported energy, with a net tariff spread of £0.14/kWh, its added savings are £35/year or £175 across five years before losses. Such differences matter more than a £30 headline promotion; but all those inputs need evidence from your installation.
For a home with no solar, a scheduled overnight tariff is often more valuable than a sophisticated PV-diversion control that will never be used. If no household member uses Home Assistant, the supplied manufacturer app and customer service could be a better purchase criterion than API flexibility. Conversely, a multi-brand household that genuinely automates around tariffs, PV and battery reserve should pay close attention to integration longevity and cloud dependency.
Firmware, accounts, subscriptions and ownership risk
Firmware can change your interface without changing the box on the wall. Record the charger model, firmware number, app version and installer configuration after commissioning. Keep auto-update arrangements compatible with the vendor’s safety recommendations, and retest Home Assistant actions after a major version upgrade. Never freeze security-critical firmware indefinitely merely to preserve a third-party integration.
The vendor’s own home-charging application may have a different pricing model from a third-party OCPP operator, paid cloud reporting, an API integrator or a fleet-management platform. A vendor offering an ‘API’ does not mean unlimited free API calls to everyone. Ask these questions in writing: Is API access included for individual customers? Can the household change installer/administrator account ownership? Can the charger move to a new backend? Will firmware updates retain third-party compatibility? Does an optional service charge affect access to charge-history exports? What remains operational if the service is discontinued?
| Failure | zappi considerations | Wallbox considerations | Easee considerations |
|---|---|---|---|
| No home internet | Check native solar modes remain as configured | HA cloud integration stops updating | Cloud connector stops; site logic needs checking |
| Vendor account unavailable | Community HA and gateway OCPP may be affected | HA portal authentication unavailable | Cloud API integration unavailable |
| Home Assistant restarted | Native zappi charging should not depend on HA | Charger follows own retained settings | Charger follows own site controls |
| Wrong CT polarity | Solar mode can use erroneous sign | Power/Solar metering distorted | Equalizer or other meter misread |
| Installer account missing | Some advanced settings inaccessible | Permissions may block HA controls | Site/charger assignment may block API or setup |
| API/firmware change | Community component may need update | Official integration may need update | Third-party connector may need update |
How to troubleshoot a missing or unreliable EV charger in Home Assistant
| Symptom | Likely cause | First safe check |
|---|---|---|
| Charger visible in app but not Home Assistant | Portal permissions, credentials, unsupported integration | Check manufacturer’s service and the exact integration requirements |
| Energy figures look ten times too large | Unit mismatch W versus kW, cumulative versus session kWh | Inspect the sensor unit, state class and meter definition |
| Charge keeps pausing on sunny day | ECO+ minimum-current logic or unstable export | Review import/export trace and vehicle’s start/stop behaviour |
| Solar ‘surplus’ charging still imports heavily | Incorrect CT placement, battery interaction or lag | Ask installer to validate meter boundary and sign |
| HA pause command works slowly | Cloud poll cycle or queued command | Measure actual delay, avoid using it for safety-critical control |
| Multiple chargers overload a circuit | Incorrect site-group configuration or broken balancing assumption | Stop use and ask installer to verify certified site protection |
| Automation controls disappear after update | Entity naming or API permission change | Check integration release notes and permissions |
| Cloud failure breaks all dashboards | All telemetry routed through vendor internet | Consider independent certified circuit metering for visibility |
The ESP32AliExpress price/Hive/DIY temptation is to replace the charger logic with a relay or an ESPHome board. Do not do that. EVSEs incorporate controls and protection requirements that are not reproduced by a general-purpose relay or improvised firmware. Use ESP32AliExpress price devices for supervised measurement of a suitably isolated local meter, not to bypass CP/PP pilot negotiation, earth leakage protection, PEN safety or site current limits.
Which one would we choose?
For a UK solar home, start with zappi if its supported ECO/ECO+ and meter configuration match the actual solar/battery system. It is not the ideal answer if absolute local-only Home Assistant control is an uncompromising requirement. For a mainstream Home Assistant installation, the Wallbox Pulsar Plus has the clearest official built-in integration path, but accept the MyWallbox cloud dependency and verify regional firmware and the extra meter options. For a multi-charger or aesthetically constrained property, Easee deserves a quote, particularly where manufacturer-supported site balancing is useful; however, verify the regional charger and integration route independently rather than assuming an open API means local Home Assistant support.
For a local-first engineering project, look beyond these three unless the vendor can demonstrate the exact capability you want. Our existing published ESP32 energy-monitor methods comparison is a useful introduction to independent, local electricity measurement.
Frequently asked questions
Does Wallbox Pulsar Plus work with Home Assistant?
Yes, there is a built-in Wallbox integration. It connects through MyWallbox Portal and can expose monitoring and selected controls, with permissions and capabilities depending on the account and supported charger. It is classified by Home Assistant as Cloud Polling, not a local integration.
Does myenergi zappi have an official native Home Assistant integration?
Do not assume it does. Community-maintained myenergi integrations are available, but must be evaluated for current support. Later built-in-Wi-Fi zappi models have a manufacturer-documented OCPP 1.6J cloud-gateway route; that does not automatically equal a built-in Home Assistant integration.
Can Easee work without the internet?
Certain charging and site-balancing functions are designed to continue under configured local control, but the Home Assistant cloud-API route requires internet service. The existence and scope of a usable local API for your model and firmware must be confirmed independently; do not mistake generic ‘Wi-Fi enabled’ language for an official offline Home Assistant feature.
Which charger is best for solar panels?
zappi is a strong first candidate because ECO/ECO+ solar behaviour is a core function. Wallbox’s solar features can be attractive with compatible meters. Easee can be part of a wider energy-management arrangement. The decisive question is how each behaves with your PV generation, grid meter and home battery, not simply whether a brochure mentions solar.
Can I run OCPP 1.6J straight into Home Assistant?
Only if the specific charger can connect to your chosen compatible OCPP backend and that backend can work with Home Assistant as configured. The zappi OCPP implementation described by myenergi uses its cloud gateway. Wallbox OCPP support depends on regional variant and firmware. Check supported profiles and network endpoint choices before buying.
What if I want 11 kW instead of 7 kW?
You need a compatible three-phase supply, charger and vehicle onboard AC charger. A single-phase 32 A installation cannot deliver 11 kW simply through a software setting. A qualified installer must assess grid capacity, earthing, protection and cable selection.
Will charging history show in the Home Assistant Energy dashboard?
Potentially, if your chosen integration exposes a suitable energy sensor with correct units and state semantics. A single-session counter that resets to zero is not necessarily a correct long-term energy source. Validate the data against a dedicated meter or manufacturer report and avoid double counting whole-home energy and EV usage.
Official sources and manufacturer documentation
The following sources support the factual distinctions above. Always check current model documentation and market-specific installer requirements before purchase or commissioning.
- Home Assistant: Wallbox integration — official cloud-polling integration, supported functions and account permissions.
- myenergi: OCPP setup requirements — compatible Wi-Fi zappi generation, account and backend requirements.
- myenergi: ECO/ECO+ zappi user manual — charging modes, minimum current and technical behaviour.
- myenergi: managing energy and OCPP gateway — documents the cloud-to-cloud OCPP 1.6J arrangement.
- Easee One manufacturer specification — UK product and charger capabilities.
- Easee September 2026 EU range update — EU portfolio transition, expressly distinct from the UK.
- Easee developer API introduction — cloud API approach and streaming advice.
- Wallbox OCPP hardware/function reference — example North American device scope; not blanket proof for UK hardware.
- UK government: residential charger technical requirements — BS EN 61851, BS 7671 and smart-charge obligations.
Editorial verification date: 15 October 2026. Product software, certification, regional availability and API entitlements can change. This guide is informational and is not installation, legal or electrical-engineering sign-off.