OpenEVSE
openevse
The OpenEVSE integration connects your Home Assistant installation to an OpenEVSE electric vehicle charging station that runs the OpenEVSE Wi-Fi firmware. The integration talks to the charger locally over your home network, so it works without an internet connection and without a cloud account.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
What people report
OpenEVSE needs the official Wi-Fi firmware and runs locally. The manual override switch is a blind toggle, not idempotent.
- Works1
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| OpenEVSE charger with Wi-Fi firmware | Works Local | Supported with official Wi-Fi firmware onlySaved copySupported devices: OpenEVSE chargers without the Wi-Fi module, since they have no network interface to communicate with.. Limitations: The integration manages a single OpenEVSE charger per config entry. If you have multiple chargers, add each one as a separate integration instance. Only OpenEVSE chargers with the official Wi-Fi firmware are supported. Chargers reached only over MQTT, or third-party firmware variants, are not. The Vehicle state of charge and Vehicle range sensors depend on the connected vehicle reporting this information through the charger. Many vehicles do not, in which case … Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| OpenEVSE (controller 8.2.3.EU, WiFi v5.1.5) | Partly works Local | Manual override switch is a blind toggle; idempotent methods upstream in progressSaved copy… problem ### System information Firmware, the device reports two separate version numbers, worth being explicit about since it's easy to conflate them: - `openevse_firmware: 8.2.3.EU`, main OpenEVSE controller firmware - WiFi module firmware: `v5.1.5` (this is what `/config` reports as `version`, and what the library's `_version_check()` actually gates on, not the controller firmware above) First/last working version: not applicable, not a regression. `turn_on`/`turn_off` have both called `toggle_override()` since this switch was written. Configuration: config-entry/UI-based, no YAML. Only … Excerpt saved from GitHub on 2026-10-23. | Issue #184844 · 2026-10 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 174 (0.02%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 0.38 |
| Set up in the UI | Yes |
| Maintainers | @c00w, @firstof9 |
Devices listed in its documentation
- OpenEVSE chargers without the Wi-Fi module, since they have no network interface to communicate with.
Limitations from the docs
- The integration manages a single OpenEVSE charger per config entry. If you have multiple chargers, add each one as a separate integration instance.
- Only OpenEVSE chargers with the official Wi-Fi firmware are supported. Chargers reached only over MQTT, or third-party firmware variants, are not.
- The Vehicle state of charge and Vehicle range sensors depend on the connected vehicle reporting this information through the charger. Many vehicles do not, in which case these sensors stay unavailable.
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
