Peblar EV charger
The Peblar is a range of smart EV chargers. The EV charger is connected to the Currentt Navigator via Modbus TCP (Ethernet).
⚙️ How it works
The Peblar communicates via Modbus TCP (Ethernet) with the Currentt Navigator. The Navigator reads the charging data (such as charging power and charging status) and sets the maximum charging current of the EV charger. This way the charging current is continuously matched to the available capacity of the grid connection and to the current yield of the solar panels.
✅ Compatible models
| Model | Type |
|---|---|
| Peblar Home | Fixed cable |
| Peblar Business | Socket / Fixed cable |
🧰 Requirements
- Currentt Navigator (connected to the local network)
- Network connection (Ethernet or WiFi) for the EV charger
- Access to the web interface of the EV charger
- Firmware 1.6 or later on the EV charger
Modbus TCP is supported from firmware 1.6 onwards. If you have an older firmware version, check for updates first before continuing.
🪛 Installation instructions
Step 1: Connect the EV charger to the network
- Connect the EV charger to your network using an Ethernet cable (recommended) or via WiFi
- Make sure the EV charger is on the same network as the Currentt Navigator
A wired connection is more stable than WiFi and prevents communication issues caused by a weak or fluctuating signal.
Step 2: Open the web interface
You configure the settings of the EV charger via the charger's web interface.
- Open a browser on a device that is on the same network as the EV charger
- Navigate to the charge point ID of the charger, for example
PBLR-XXXXXXX.local- The charge point ID is printed on the sticker in the charger's Quick guide
- You can also use the IP address of the charger
- Log in to the web interface
Cannot reach the web interface? The EV charger creates its own WiFi hotspot for 15 minutes after power-up. Connect to it and navigate to 172.16.0.1. Switch the power off and on again to reactivate the hotspot.
Step 3: Check the firmware
- Check in the web interface whether firmware updates are available
- Install the latest firmware; it must be at least version 1.6
After installing new firmware, the EV charger restarts and the connection with the web interface is temporarily lost.
Step 4: Enable the Modbus API
- In the web interface, go to Settings
- Open Advanced
- Enable the Modbus API
- Set the Access mode to Read & write
- Save the settings
If the access mode is set to read only, the Currentt Navigator can read the EV charger but cannot control it. Always choose Read & write.
Set the charging strategies on the EV charger itself to Default and disable smart charging. If these remain active, the EV charger and the Currentt Navigator will work against each other.
Step 5: Configuration in the Currentt Navigator
After configuring the EV charger, it must be added in the Currentt Navigator.
Via the installation wizard (recommended)
- Click the settings icon (top right of the screen)
- Choose Installation wizard
- Follow the steps on the screen
Manual configuration
- Click the settings icon (top right of the screen)
- Go to Components
- Click the + button in the EV chargers section
- Select Peblar
- Under Communication, enter the connection details:
| Parameter | Value |
|---|---|
| Host | The IP address or hostname of the EV charger, for example pblr-<number>.local |
| TCP port | 502 (default) |
- Click Save
The hostname of the Peblar is its charge point ID, in the form pblr-<number>.local. You can find this ID on the sticker in the charger's Quick guide.
Using an IP address instead of the hostname? Then set a static IP address on the EV charger or reserve the IP address in your router (DHCP reservation). With DHCP, the address can change after a router restart, causing the connection to drop.
The Currentt Navigator and the EV charger must be on the same network (and the same VLAN). If they are on different network segments, the Navigator cannot reach the EV charger.
📋 Settings summary
| Parameter | Value |
|---|---|
| Connection | Local network (Ethernet or WiFi) |
| Protocol | Modbus TCP |
| Host | IP address or pblr-<number>.local |
| TCP port | 502 |
| Modbus address | 1 (default) |
| Firmware | 1.6 or later |
| Modbus API | Enabled |
| Access mode | Read & write |
| Charging strategy | Default (smart charging off) |
🛟 Troubleshooting
| Problem | Possible cause | Solution |
|---|---|---|
| No connection | Modbus API not enabled | Enable the Modbus API via Settings → Advanced |
| No connection | Firmware older than 1.6 | Update the firmware of the EV charger |
| No connection | Wrong host | Check the charge point ID or the IP address of the EV charger |
| No connection | Devices on different networks | Make sure the Navigator and the EV charger are on the same (V)LAN |
| No connection | Hostname is not resolved | Use the IP address instead of pblr-<number>.local |
| No connection after restart | IP address changed (DHCP) | Set a static IP address or create a DHCP reservation in the router |
| Reading works, but no control | Access mode is set to read only | Set the access mode to Read & write |
| EV charger does not follow the control commands | Smart charging is enabled on the EV charger | Set the charging strategy to Default and disable smart charging |
| Unstable connection | Weak WiFi signal | Connect the EV charger using a wired Ethernet connection |