Peblar Home EV Charger with Local REST API

hi Frank,
I just bought a Peblar charger and tried setting it up on HA. I can access the charger web UI and there are no errors . The HA integration however throws the following exception

Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/peblar/config_flow.py”, line 95, in async_step_reconfigure
info = await peblar.system_information()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/peblar/peblar.py”, line 230, in system_information
return PeblarSystemInformation.from_json(result)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File “”, line 232, in mashumaro_from_json
mashumaro.exceptions.MissingField: Field “meter_calibration_current_gain_b” of type int is missing in PeblarSystemInformation instance

Is it a mismatch with the latest firmware version of Peblar.
Firmware version
1.9.0+1+WL-1
Customization firmware version
Peblar-1.14

thanks
Ryan

Hi everyone,

I am trying to connect my Eneco Connectric EV charger (a Peblar white label) to Home Assistant. I’ve read that some users have successfully managed to get this working, but I am currently stuck. At the moment, the charger uses a built-in 4G SIM card for its default connection.

To get the Peblar integration working in Home Assistant, I need local network access. The issue is that I cannot reach the local management page of the charger via its IP address at all.

Here is what I have tried so far:

  • Connected the charger to my regular home WiFi. It connects successfully, but the management page remains unreachable and the integration fails.
  • Connected the charger to a WiFi range extender to rule out a weak signal. Unfortunately, this gave the exact same result.
  • Ran a physical Ethernet (UTP) cable to the charger. Even with a wired connection, the web interface won’t load and the Home Assistant integration refuses to connect.

Could this be due to a specific network setting, a restriction in the Eneco firmware, or am I missing another crucial step? Any tips would be greatly appreciated!

System information:

  • Firmware version: 1.7.1+1+WL-1
  • Personal firmware: Eneco_eMobility-1.2

Thanks in advance for your help!

EDIT: it suddenly works, no idea why. generated a new key after i plugged a UTP cable in my charger and voila, works.

I just have installed Eneco Connectric EV charger. I can access to the local web UI but it only shows a time schedule option as “smart charging”.

Maybe I should wait until Eneco provisions it with “dynamic load balancing” capability as they sell it as an extra subscription (which I have).

Were you able to solve "10276 · Solar charging not supported yet”?

Got my Peblar Business installed as well last month. Good looking, local (no cloud bullshit and subscriptions), best value for money, full functionality…. Default integration not covering 100% functionality and management in HA but using it together with this API integration every single topic needed covered. 100% scheduling and load balancing (keeping track of capacity tariff in Belgium) from within HA.

What kinda functionality is missing?

Is it possible to report the authtoken used to start a session? I have different rfid cards and dependent on the card used I would like to activate a different charging mode on the Peblar. I could not find anything on the AuthToken on the Peblar Developer site, but this script (MacOS) show the AuthToken per session:

sessionCookie=$(curl -s --request POST http://<host>/api/v1/auth/login -H "Content-Type: application/json"  -d '{ "Password": "<password>"}' -D - | sed -n 's/^Set-Cookie: sessionid=\([0-9A-Fa-f]*\).*/\1/p')

starttime=$(date -u -v-1d +"%Y-%m-%dT00:00:00")
stoptime=$(date -u -v+1M +"%Y-%m-%dT%H:%M:%S")
curl -s --location --request GET "http://<host>/api/v1/statistics/meterhistory?StartTime=$starttime&StopTime=$stoptime" --header 'Content-Type: application/json' --cookie "sessionid=$sessionCookie" | jq -r '.Session[-1]?.AuthToken // 0'

Hi, with your input (code) in your topic, I managed (with some help from AI) to make an automation en script that returns the actual RFID, Starttime, StopTime and Sessionnumber in a few helpers.

With this helpers you can start other automations

@Rklootwijk Got it working