peaqev ev-charging
elden1337/hass-peaq · v3.7.5
Home Assistant custom component that aids in both peak-level energy charge avoidance and spotprice-aware charging.
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, humidity, air quality…) | |
select | Mode picker (as switches) |
What people report
Peaqev controls EV chargers (Easee, Chargeamps, Zaptec, Garo) to cap peak power; users report occasional charger-control failures tied to vendor APIs.
- Partly works4
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Chargeamps EV charger | Partly works Cloud | Owner notes charger API sometimes too slow to pause chargingSaved copyIf you havent rebooted since i would like the full logs for peaqev from the night. The "unable to stop charger" should just keep trying, i also get that sometimes if chargeamps api is not fast enough. The thing with interim day peak foe gothenburg model should work, but in this case it looks off yes. Question is if it managed to raise it in the earlier attempts of the hour after the peak breach, cos very late in the hour increasing is not allwed anyway since the risk of breach is too high. I still think it sounds like a non response from easee cloud, but let's see the log to see what my code … Excerpt saved from GitHub on 2026-10-23. | Issue #359 · 2024-08 | |
| Easee EV charger | Partly works Cloud | Peaqev sometimes could not stop the charger; owner suspected Easee API issuesSaved copyHello, For the second night in a row peaqev has broken my peak - it seems that it can't stop my easee charger for some reason. Could the fallback be to instead request the lowest amps available when this happens. I am on the latest HA, peaqev integration and latest easee integration. Here is the error message, please let me know if I can provide some more info. [code] Excerpt saved from GitHub on 2026-10-23. | Issue #359 · 2024-08 | |
| Garo wallbox GLBDCWM-T222WO | Partly works | Support added but needed entity-name fixes; owner wanted testersSaved copyHi there, I have the Garo wallbox (model GLBDCWM-T222WO). I saw that support for it has been added in a recent release of hass-peaq and tried an install using the main branch. I quickly found some errors in garowallbox.py regarding entity names that was easy to correct. That got rid of some errors at start-up. The first problem in the log is now: ``` 2023-05-25 23:40:08.078 WARNING (MainThread) [custom_components.peaqev.peaqservice.chargertypes.types.garowallbox] You are initiating GaroWallbox as Chargertype. Bare in mind that this chargertype has not been signed off in testing and may be … Excerpt saved from GitHub on 2026-10-23. | Issue #7 · 2023-05 | |
| Zaptec EV charger | Partly works | Works after hotfix 3.3.1; update-current feature not implementedSaved copy… logged: 12:07:42 Error setting up entry sensor.ams_p for peaqev Traceback (most recent call last): File "/config/custom_components/peaqev/peaqservice/chargertypes/chargertype_factory.py", line 62, in async_create ret.is_initialized = await ret.async_setup() ^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/peaqev/peaqservice/chargertypes/icharger_type.py", line 78, in async_setup update_current=self.call_update_current, ^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/peaqev/peaqservice/chargertypes/types/zap Excerpt saved from GitHub on 2026-10-23. | Issue #319 · 2023-12 |
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
Calculated
Works out its values from other data rather than talking to a device.
Details
| Installs (analytics) | 6 |
|---|---|
| GitHub stars | 70 |
| Latest version | 3.7.5 (2026-08-07) |
| Set up in the UI | Yes |
| Maintainers | @elden1337 |
| License | GPL-3.0 |
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.
Sources
- Documentation: https://github.com/elden1337/hass-peaq
- Source code: https://github.com/elden1337/hass-peaq
- Issues: https://github.com/elden1337/hass-peaq/issues
- HACS: https://hacs.xyz
