EVBox G4 BLE for Home Assistant

An unofficial Home Assistant custom integration for configuring and monitoring EVBox Gen4 charging stations over Bluetooth Low Energy, including through an active ESPHome Bluetooth proxy.

Usage, actions and troubleshooting · Full Quality Scale assessment

Product information: EVBox.

This project is independent and is not affiliated with, endorsed by, or supported by EVBox. EVBox and the product names are trademarks of their respective owners.

Requirements

• Home Assistant 2026.8.0 or newer
• A compatible EVBox Gen4 charging station
• The charger's Bluetooth security code
• Direct Bluetooth access or an active, connectable ESPHome Bluetooth proxy

Installation with HACS

Until the integration is included in HACS by default, add it as a custom repository:

1. Open HACS in Home Assistant.
2. Select Integrations.
3. Open the menu and select Custom repositories.
4. Add https://github.com/CReimer/evbox-g4-ble with the category Integration.
5. Install EVBox G4 BLE and restart Home Assistant.
6. Go to Settings > Devices & services > Add integration and search for EVBox G4 BLE.

Manual installation

Copy custom_components/evbox_g4_ble into the custom_components directory of your Home Assistant configuration, restart Home Assistant, and add the integration from Settings > Devices & services.

Features

The available controls depend on the capabilities reported by the charger. They can include:

• local BLE authentication and automatic discovery;
• firmware, connectivity, Wi-Fi and charger diagnostics;
• minimum and maximum charging current;
• card-required or automatic charging;
• LED idle behavior and phase rotation;
• charging-backend and cellular APN configuration;
• Wi-Fi scanning and configuration;
• RFID allow-list management;
• discovery and pairing of linked charge points;
• restart, identify and firmware-update actions.

The firmware update entity checks EVBox's public firmware document every 12 hours and offers a newer compatible release through Home Assistant's normal update UI. The charger itself supports FTP only, so Home Assistant downloads the vendor's HTTPS file first and exposes only that file through a credential-protected, read-only FTP server for 15 minutes. The charger and Home Assistant must be able to reach each other over IPv4. The embedded FTP server implements the SIZE request used by EVBox firmware before it starts downloading the image.

Configuration writes are read back where the charger protocol permits it. Rejected or mismatching values are reported as errors instead of being treated as successful changes.

Reliability and troubleshooting

The integration distinguishes a rejected Bluetooth security code from a charger that cannot be reached. If the code changes, Home Assistant requests reauthentication. You can also select Reconfigure on the integration to enter a new code. The existing device and entity IDs are retained.

Diagnostics are polled every five minutes; scalar configuration every 30 minutes. The refresh button/action forces a full read, using one authenticated BLE connection. Multi-step configuration changes are serialized, including RFID lists, linked charge points and backend settings. Linked charge point changes read the list from the charger before modifying it.

Before downloading web firmware, Home Assistant checks for a usable IPv4 route to the charger. This does not prove that firewall rules permit the charger's incoming FTP connection. The charger must reach Home Assistant's FTP control port and passive data ports; isolated guest Wi-Fi and container networking can prevent this.

The firmware entity reports preparation, waiting for the charger, download and waiting for installation separately. A completed download is not installation proof: the BLE-reported version must change and, when known, match the requested target version. A timeout distinguishes a charger that never connected to FTP from an installation that could not be confirmed. Check the reported firmware version before retrying an unconfirmed installation.

Compatible charging stations

The BLE services used by this integration are the same two transports accepted by EVBox Connect. EVBox lists these models as compatible with that app:

• EVBox Elvi;
• EVBox BusinessLine Gen4;
• EVBox Iqon;
• WALLBOX and SMART WALLBOX branded variants.

Development and live acceptance have so far been performed with an EVBox Elvi. The other listed Gen4 models are expected to use the same protocol but should be treated as community-tested until owners confirm their exact capabilities. Older BusinessLine Gen3 and HomeLine stations are not supported: they are configured with the wired EVBox service tool rather than EVBox Connect BLE. Newer Livo, Livo 2 and Liviqo models use EVBox Install and a different protocol.

Safety

This is an independent community project for EVBox Gen4 hardware. Charging equipment can switch substantial electrical loads. Verify current limits and other safety-relevant settings locally, and do not perform firmware updates without a recovery plan. The authors provide no warranty and accept no responsibility for damage or loss.

Do not include Bluetooth security codes, APN passwords, charger diagnostics or other credentials in bug reports. When reporting a problem, redact serial numbers, network names and backend URLs.

Development

Install requirements-test.txt using Python 3.14, then run the unit tests with:

python -m unittest discover -s tests

The integration was developed with substantial assistance from generative AI. All changes are reviewed, tested, and released under the responsibility of the maintainer.

License

The independently written source code in this repository is licensed under the Apache License 2.0.

No EVBox application, firmware, decompiled source code or credentials are distributed with this repository. The Apache License does not grant rights to EVBox trademarks, firmware, brand artwork or other third-party material.

Trademark legal notice

All product names, trademarks and registered trademarks referenced by this project or depicted in its images belong to their respective owners. Names, marks and product imagery are used only to identify compatible products. Their use does not imply endorsement of or affiliation with this project.

This notice follows the convention used by Home Assistant Brands.

Offline tests and coverage

Use Python 3.14 and install requirements-test.txt, then run python tools/run_tests.py. Bluetooth and charger commands are mocked; firmware transfers use local FTP test servers; no charger or live Home Assistant instance is contacted. Tests cover protocol parsing, connection failures, configuration readback, entity controls, setup and firmware progress. Legacy isolated protocol tests and real Home Assistant entity tests share the suite without leaking framework stubs.

CI runs the same command against Home Assistant 2026.8.0 and the latest stable release for pushes and pull requests. A separate advisory preview-version job runs daily and on manual workflow dispatch; preview failures do not fail the stable compatibility checks. Every test job requires more than 95% line coverage and more than 95% branch coverage separately in every integration module, without rounding or omitting modules. JSON, XML and HTML reports are available in the coverage-report artifact.

The suite also enforces all 54 quality declarations cumulatively through Bronze, Silver, Gold and Platinum, with 100% config, reauth, reconfigure and options-flow statement/branch coverage without exclusions. A separate required CI job runs strict mypy on every integration module against stable Home Assistant. Run it locally with python -m pip install mypy==2.4.0 and python -m mypy. The consumed aioftp API has local type stubs in typings/; real FTP tests exercise resuming, missing data connections, aborts and I/O failures. This is a self-assessment of a custom integration, not an official HA tier.