[APP][Pro] Peblar - Go and explore while we build your future

Apps
41

This will be fixed in the next version of the app.

42

Could you send a diagnostic report right after the car started charging?

43

Hi Edwin,

Ik krijg de volgende code om te delen: cc7798a7-1a1e-4fe3-8e31-7ad1cf82a240

Kun jij daarmee uit de voeten?

44

Yes. Can you also provide a report without charging and without car connected?

45

Sure: 338da95f-1bec-4526-a7b3-a3cdf8dfbfee

And thanks for the help :+1:t3:

Met vriendelijke groet,
Ed de Vries

Verstuurd vanaf mobiel

46

Hi,

Amperage seems way off in the app. Other measurements are fine, probably a math miscalculation somewhere?

IMG_4608
IMG_46081179×2556 104 KB

47

Hi,

Which firmware is running on your device, and what is the Peblar dashboard output for these values?

I haven’t touched those values in previous updates.

48

Hmm, after the latest firmware update(1.9.2+1+WL-1), adding again to Homey I get:

image
image393×441 13.7 KB

any clues?

Cheers,

Tom.
49

Hi,

Questions regarding Device discovery, I have my Peblar in different VLAN.
Does this work based on mDNS or?.. because unfortunately I have no option to put in an IP for discovery.

50

Yes, it is using mDNS.

51

Homey cannot connect / reach your unit. Restart your unit, make sure it is connected to your network, and try again.

53

Hi, I want to create a Homey flow based on the last used RFID token from my Peblar Home charger. However, the variable ‘Last used RFID Peblar EV charger’ always returns ‘empty’. The variable ‘Last read RFID token’ throws an error. Is there a way to retrieve the RFID token that was used to start the charging session?

54

Hi,

I wasn’t aware that flow and variable were still available. I need to delete those, as that functionality is not available though their system.

I did implement that in the beginning, but when reading that data, it puts the unit in learning mode, and the unit stopped working.

55

Thanks. Is there a workaround you know of?

56

@evdpol Thanks for the app. I ran into three issues that may share a cause, so I am reporting them together. This is a public charger on my own house connection, so it sees regular use by different drivers.

1. evcharger_charging is set to true and never returns to false

Right now, with no car connected and nothing charging:

Capability Value
evcharger_charging_state plugged_out
measure_power.phase_1/2/3 0 W
measure_current.phase_1/2/3 0 A
evcharger_charging true

In Homey Insights this capability has exactly one entry: 7 August 2026, 20:53 UTC, changed to true. Nothing after that, so 27 days without a single change, while the charger was idle for most of that period.

There have been two normal sessions since: 2 September 15:20 to 18:20 UTC (32.7 kWh) and 5 September 10:27 to 13:52 UTC (35.4 kWh), both around 11 kW across three phases. evcharger_charging did not change at the start or the end of either one.

Effect: the flow triggers “Started charging” and “Stopped charging” never fire, because both depend on a transition that no longer happens. The cards look perfectly healthy in the flow editor, so this is easy to miss.

Workaround: use “The charging state of the EV charger changed” with state “Charging” instead. That capability updates correctly in both directions.

2. The device is marked unavailable while the app keeps polling it

Today the device showed “Apparaat onbeschikbaar / Dit apparaat is nu niet beschikbaar” in the Homey app, with no reason text.

At the same moment, measure_voltage.phase_1 in Insights was still receiving a fresh value every 5 seconds, with no gap at all. Screenshot taken at 11:13 local time, Insights entries continuing through 11:13:10 local and beyond. The values were live, not frozen: 230 V at 10:19 rising to 239 V over the hour.

So the driver is polling the charger successfully while the device is presented as unavailable. It looks like setUnavailable() is called somewhere and setAvailable() is never called again.

Restarting the app earlier today did not clear issue 1, and the unavailable state appeared after that restart.

3. alarm_problem fires briefly and clears itself, roughly once a day

Since 25 August, alarm_problem has gone true and back to false 25 times. Every single time it cleared itself within 5 to 10 seconds. A few examples from Insights (UTC):

2026-08-28 07:58:45  true      2026-08-28 07:58:50  false
2026-09-04 20:38:45  true      2026-09-04 20:38:50  false
2026-09-05 05:57:28  true      2026-09-05 05:57:38  false
2026-09-06 03:22:05  true      2026-09-06 03:22:10  false

Several of these happened while the charger was idle with nothing plugged in, so there was no real fault to report. Any flow on “A problem has been detected” produces a push notification each time.

A possible common cause

measure_voltage receives a new value every 5 seconds, so the polling interval appears to be 5 seconds. All three issues would be explained by a single failed poll being written into device state: the failed poll raises alarm_problem and calls setUnavailable(), the next successful poll clears the alarm but never calls setAvailable() again. That is a guess from the outside, not something I can prove, but the 5 second alarm duration matching the poll interval is hard to ignore.

Environment

  • App version: 1.0.7
  • Homey Pro Early 2023, firmware 13.4.1
  • Peblar firmware: 1.9.2+1+WL-1
  • Peblar API version: 1.0
  • Charger is on ethernet, connection stable throughout

Both issues have the same shape: a state that gets set one way and never set back. Happy to pull more Insights data or test a fix if that helps.