Local control
The integration sends charging-current, stop, schedule, adaptive-mode, and ground-protection commands directly to the charger. It also lets you manage the charger's optional OCPP connection.
Local-only Home Assistant integration
Control your Eveus EV charger from Home Assistant.
The Eveus EV Charger integration runs in Home Assistant and communicates directly with your charger over the local network. Install the integration through HACS to control charging, monitor electrical measurements and charging costs, manage schedules, estimate EV battery SOC in Advanced mode, and receive actionable safety notices.
Built for useful EV charging automations
Events and device triggers
The integration fires events on real charger transitions β charging started or finished, car connected or disconnected, error β and offers them as ready-made device triggers in the automation editor. The finished event carries the session's energy, cost, and duration. State and Substate are enum sensors, so state triggers offer a dropdown of valid values.
Energy and cost
The integration exposes the charger's current voltage, current, and power measurements, along with session energy, total energy, resettable counters, tariffs, and charging costs. Last Session sensors keep each finished session's energy, cost, and duration until the next session completes β and past sessions stay in their history.
SOC and ETA
In Advanced mode, the integration estimates EV battery state of charge, time to target, finish time, remaining grid energy, and expected cost. These values are derived from charger data and your configured battery details.
Safety notices
The integration creates Home Assistant Repairs issues for confirmed missing ground, disabled ground protection, overheating, excessive leakage current, charger faults, and a low internal backup battery.
Real-network resilience
The integration adapts its polling rate, handles powered-off chargers without repeated log noise, confirms commands against charger responses, starts reauthentication when credentials fail, and redacts exported diagnostics.
English and Ukrainian
The integration includes English and Ukrainian Home Assistant translations. You can also add multiple Eveus chargers; Home Assistant creates a separate device and entities for each one.
Install the integration through HACS
- Open HACS and search for Eveus EV Charger β it is in the HACS default store, so no custom repository is needed.
- Install it and restart Home Assistant.
- Open Settings β Devices & Services β Add Integration, then search for Eveus EV Charger.
- Enter the charger address and credentials, then choose the charger model, phase count, and integration mode.
Requirements: an Eveus 16A, 32A, 40A, or 48A charger whose local HTTP API is reachable from Home Assistant, plus the charger username and password.
Frequently asked questions
Does the Eveus EV charger work with Home Assistant?
Yes. The Eveus EV Charger integration connects Home Assistant to Eveus 16A, 32A, 40A, and 48A chargers over the local network and is installable through HACS.
Does the integration need a cloud account?
No. The integration communicates with the charger only over your local network β no cloud account and no telemetry. The charger's own optional OCPP connection is a separate feature and may use a remote backend.
Can Home Assistant estimate the EV battery state of charge?
Yes. In Advanced mode the integration estimates battery SOC, time to target, and expected finish time from charger data and the battery details you configure (initial SOC, battery capacity, correction factor).
Why does setup fail while the charger's web page works?
Chargers on older firmware (R3.01.x has been reported) can answer their web page normally but reply to the integration's API request in a way setup can't use. Update the charger firmware: message @energy_star on Telegram to get added to the charger support channel with the firmware files and instructions β then update through the Grizzl-E app or flash the downloaded file from the charger's web interface. The setup dialog shows the concrete failure reason, and the troubleshooting guide explains what to report if the firmware can't be updated.