Energy
Peblar
peblar
Built inLocal pollingPlatinum
The Peblar integration integrates the [Peblar Rocksolid EV Charger] into your smart home ecosystem. It enables real-time monitoring of charging status, tracking energy consumption, controlling charging behavior, and integrating EV charging data into the Home Assistant energy dashboard.
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…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
What people report
Peblar EV chargers work locally; 2026.10.0 broke older firmware without meter history, fixed in 2026.10.1.
- Works4
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Coolblue BlueBuilt Peblar (WLAC1-F22RPWELMCR00) | Works Local | Failed on 2026.10.0 with old firmware; fixed in 2026.10.1Saved copyThe problem Since 2026.10.0 the Peblar config entry never loads. It stays in `setup_retry` with: > An unknown error occurred while communicating with the Peblar EV charger: Error occurred while communicating to the Peblar charger The authorization coordinator added in #183364 calls `meter_history()`. On my charger firmware, `GET /api/v1/statistics/meterhistory` returns 404. `async_setup_entry` awaits the first refresh of all coordinators in one `asyncio.gather`, so this one failure raises `ConfigEntryNotReady` and blocks the whole integration. The meter, user configuration and version … Excerpt saved from GitHub on 2026-10-23. | Issue #184819 · 2026-10 | |
| Peblar Business | Works Local | Listed as supportedSaved copySupported devices: Peblar Home; Peblar Home Plus; Peblar Business. Limitations: The Peblar APIs currently don't communicate when the charger is awaiting authentication (for example, using an RFID card) before it can start charging. As a result, you will see a suspended charging status in Home Assistant when the charger is actually awaiting authentication. Home Assistant manages the charger's local REST API for you. If it is switched off, setting up this integration switches it on, and it stays on afterwards. You can keep using that API yourself alongside the integration. Peblar is also sold … Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Peblar Home | Works Local | Listed as supportedSaved copySupported devices: Peblar Home; Peblar Home Plus; Peblar Business. Limitations: The Peblar APIs currently don't communicate when the charger is awaiting authentication (for example, using an RFID card) before it can start charging. As a result, you will see a suspended charging status in Home Assistant when the charger is actually awaiting authentication. Home Assistant manages the charger's local REST API for you. If it is switched off, setting up this integration switches it on, and it stays on afterwards. You can keep using that API yourself alongside the integration. Peblar is also sold … Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Peblar Home Plus | Works Local | Listed as supportedSaved copySupported devices: Peblar Home; Peblar Home Plus; Peblar Business. Limitations: The Peblar APIs currently don't communicate when the charger is awaiting authentication (for example, using an RFID card) before it can start charging. As a result, you will see a suspended charging status in Home Assistant when the charger is actually awaiting authentication. Home Assistant manages the charger's local REST API for you. If it is switched off, setting up this integration switches it on, and it stays on afterwards. You can keep using that API yourself alongside the integration. Peblar is also sold … Excerpt saved from home-assistant.io on 2026-10-23. | Docs | |
| Peblar without meter history endpoint | Partly works Local | Session authorization event entity stays unavailable on older firmwareSaved copyThe problem On a charger whose firmware does not have the meter history endpoint, the Session authorization event entity is still created and stays `unavailable` permanently. The description of #184824 says the event entity is skipped when the authorization coordinator's first refresh fails. The merged code does not do that: `event.py` only skips the entity when the charger has no RFID reader, and `test_a_charger_without_meter_history` asserts the entity exists with state `unavailable`. On this firmware `GET /api/v1/statistics/meterhistory` always returns `404`, so the entity can never become … Excerpt saved from GitHub on 2026-10-23. | Issue #187063 · 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 polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 874 (0.12%) |
|---|---|
| Quality scale | Platinum |
| Added in | Home Assistant 2025.1 |
| Set up in the UI | Yes |
| Maintainers | @frenck |
Devices listed in its documentation
- Peblar Home
- Peblar Home Plus
- Peblar Business
Limitations from the docs
- The Peblar APIs currently don't communicate when the charger is awaiting authentication (for example, using an RFID card) before it can start charging. As a result, you will see a suspended charging status in Home Assistant when the charger is actually awaiting authentication.
- Home Assistant manages the charger's local REST API for you. If it is switched off, setting up this integration switches it on, and it stays on afterwards. You can keep using that API yourself alongside the integration.
- Peblar is also sold as white-label products, such as CoolBlue BlueBuilt, Eneco Connectric® and Shell Recharge. Some of these run firmware that is locked by the reseller: they reject generic Peblar firmware and may stay on an older version. On a CoolBlue BlueBuilt charger with firmware 1.6.1+1+COOLBLUE-1, the …
- The Firmware and Customization update entities are not created, because the charger does not report any available update.
- The Socket lock binary sensor always shows the socket as unlocked, because this firmware reports the socket as unlocked even while the cable is locked in. The Keep socket locked switch does lock the cable.
- The List autocharge vehicles, Add autocharge vehicle and Delete autocharge vehicle actions do not work, because this firmware does not provide the autocharge vehicle list.
- The Custom solar smart charging mode is not offered, as it needs firmware 1.10 or later.
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.
