This should be fixed please make sure you have test version 4.2.0
I added nearly all features you requested besides:
Do you know if it is possible to retrieve the authorized rfid card from the API? the official app does that.
As of right now that doesnt seem to be possible
Cool, I see the extra metrics now. And the total kwh charged value is now in sync with the meter of the Peblar. This does kill the current session meter, I thing its best to add a special meter for that one, one that can reset.
I also cant find the rfid in my charger. But I am OCPP managed.
I did notice you can retrieve that info also:
SessionManagerChargeWithoutAuth: false — autorisation is required
SeccOcppActive: true — OCPP managed
PredefinedCpoName: "my provider" — Name of OCPP provider.
That is usefull to check if you can allow the authorize endpoints with own RFID (those points are in the local API).
If seccOccpActive is true, dont register those flow cards else register them (could be done with a filter maybe).
I’ll look into that,
I seem to have introduced a bug in 4.2 I’ll fix that tonight. With the half steps it now halves the Amps which is totally not intended so instead of 16000 amps it now sets the max to 8000. Will patch that up tonight.
I believe you just needed to change the step in the UI component from 1 to 0.5 no calculations etc
I thought it was a bug but it seems to be an issue related to my load balancing not being picked up. So it should be good.
Let me know if you run into any issues with 4.2
One found 
the cable connected condition when inverted doesnt show if it is inverted or not in its label. Other than that going strong 
The current session metric would be a nice wish still
Current Session = Charged Engergy it resets everytime you charge your vehicle or what do you mean specifically?
The charged energy aligns with the peblar total and should just increase, like it does now.
But on the dashboard of the peblar you can see the current session charged, if you stop the session, unauthorized, it goes back to 0.
So a different one, it was the metric you had linked tot charged energy in 4.0 but as a seperate capability.
I need to redo that anyways since Homey specified pretty well how the EV Charger capabilities should work.
And i believe charged energy should be session energy and for the total I should just create a new capability
I also just read up on the new(ish) target_power en target_power_mode capabilites Homey introduced. These make sense to implement next to the A target this one is Watt based and designed for Homey to support Energy Management Systems. The mode tells the EMS if it is allowed to control versus device own control. So in the Peblar case the Homey mode would force the Peblar into default mode where the target_power determines how fast to (dis)charge. While the Automatic mode allows the Peblar to work in one of the solar modes.
I am working on this one for my Marstek battery app also.
I like they did this, does make the UI a bit more complex with these linked capabilities though
I believe you did the meter_power.charged correct btw:
By default the
meter_powercapability will be used to determine the energy charged by the EV charger.{
“name”: { “en”: “Home Battery” },
“class”: “battery”,
“capabilities”: [
“measure_power”,
“measure_battery”,
“meter_power.charged”,
“meter_power.discharged”,
“target_power”,
“target_power_mode”
],
“capabilitiesOptions”: {
“meter_power.charged”: {
“title”: { “en”: “Charged Energy” }
},
“meter_power.discharged”: {
“title”: { “en”: “Discharged Energy” }
},
“target_power”: {
“min”: -5000,
“max”: 5000
}
},
“energy”: {
“homeBattery”: true,
“meterPowerImportedCapability”: “meter_power.charged”,
“meterPowerExportedCapability”: “meter_power.discharged”
}
}
Since currently we dont have discharge yet, what you did matches their expectation. THe behavior in my dashboards are also fine.
The
meter_powercapability (ormeter_powersub capabilities) represents energy in kilowatt-hours (kWh) and can be used in two ways:
- Cumulative energy
Tracks the total amount of energy consumed or generated over time, with values that continuously and only increase. It is typically reset only when the device is reset or reinstalled. Example : A smart meter displaying 12,345 kWh since installation.
- Non-cumulative
Represents energy used or generated during a specific time interval, without accumulating past values. Example : Energy consumed in the last 24 hours, or current battery state of charge in kWh.
In the following sections, when
meter_poweris referenced, it always refers to cumulative energy, unless explicitly stated otherwise. In this context,meter_powertracks the total energy consumed or generated over time, measured in kilowatt-hours (kWh).Energy calculates energy consumption over a given period by analyzing the difference in the
meter_powervalue over time. If the values are periodically reset to zero or decrease unexpectedly, it may lead to data loss or invalid interpretations.
FYI, I found out you can add your own modes to the target_power_mode so you can merge it into the other Peblar modes.
Hi All,
I just hooked up my Peblar Business and ready to get it into Homey. I already decided to install this app and not the official one, but now I’m wondering, should I install stable (3.1.2) or test (4.2.0)?
Can anyone using the app, or perhaps @Kyle_Michiels, advise me what to do?
Thanks!
The test version is way more extensive and im definitely looking for testers. So if you want more get the test version its also supposed to be more stable
Thanks, I will install the test version.
Still have to wait a bit until my car arrives though
Not known to me! Ill see if I can fix it
Hi, using your app and I really love it.
Is there a way to enable it to let us see it in the Energy tab ? To be show as EV Charger ?
Not on my side, I don’t know why. Only way for me until now was to use Share Your Device! - Advanced Virtual Devices from Device Capabilities - #31 by RogerSt and reflect data which is in fact a bit crappy.
Report: b3087ff5-6324-496f-90e6-13121f89f482
