[App][Pro] OCPP Server - Run any OCPP 1.6 EV charger from Homey

Apps
23

@nogren

Thanks so much for this app! It will allow me to move away from the cloud based NexBlue app to local control.

Although I am new to this and may have missed something, I do have a question: Why is there an 11kW maximum on set target power? Does the OCPP get this from the charger or is it hardcoded?

I have a 25A circuit so I could do 16kW charging (some cars have a 22kW OBC).
Perhaps an option to set the maximum allowed in the app?

image
image309×113 10.1 KB

24

Hi,

I am using OCPP Server v1.0.5 with a Ratio EV charger using OCPP 1.6J.

The charger connects successfully to the Homey OCPP Server, and remote start/stop charging works correctly.

However, whenever I try to set a charging power limit, either using the device slider or the Homey Flow card, I receive:

“Charger reported ‘Rejected’ for charge limit”

The charger continues charging at full power.

Could you please check the OCPP messages in my diagnostic report and see exactly why the Ratio charger rejects the SetChargingProfile request?

In particular, could this be related to using TxDefaultProfile rather than a TxProfile associated with the active transaction?

Being able to dynamically control the charging limit is essential for my setup, as I want Homey to regulate EV charging based on available solar power.

Diagnostic report ID:

abc4cef7-d01c-4d12-998d-7305ad2dc012

If needed, I would be happy to test a modified/beta version of the app with my Ratio charger.

Best regards,

Claus

25

Hi Claus

This is fixed on newer version (under test)

Can you please try with the test version?

If you send an email to homey@dnetlabs.co i can provide you the latest test version of the app.

26

Hi

This is very interesring. Does the OCPP Server app support a Ctek Chargestorm Connected 2 with two charging cables?

27

I can only confirm that it supports the one with one outlet. But perhaps Dnetlabs can confirm that there is code in the app to support two outlets?

28

Hi!

That I have understood, but thanks for confirming. It would be great of someone can confirm that it works with two outlets.

29

Can you also implement OCPP passtrough? I’d like to use this app, but also keep the possibility to connect to a reimbursement backoffice (2nd OCPP server)

30

Hi @DnetLabs

Hi Guys,

First of all, thanks for your awesome job on this integration!

So I’m eager to report some bug which if solved the app would shine better. :slight_smile:

When I add the Wallbox (Pulsar Plus) charger, firstly there are no all the capabilities included. Per phase data is missing (V/A) while combined values are slip in immediately. If I connect the car and start a charging session, still these tags are missing, even if I restart the app. But after restarting Homey, all data comes in. I experienced this behaviour four times at different installation sites after charger deployment.

Time by time, roughly weekly, OCPP device in Homey goes Unavailable, so after an automated app restart, it comes back but with the same issue, there are no Amper and Voltage data per phases. Even the tag goes unavailable and disappear form the device tile in Homey, so advanced flows what are calculating available power fails to run, an app restart can’t bring back these values, only if a charging session starts.

Isn’t it possible to keep these tags in the system even, if charger does not update them for a while. based on the face, If once these were existing, they surely will in the future.

31

Hi!

Thanks for your kind comments.

If you can drop a note to homey at dnetlabs dot co we can provide you a test release for testing :wink:

32

Thanks guys! This update was important.

33

It looks like ive managed to get this setup with a Salus EV charger. Its pretty basic but supports OCPP and does the job for last year with plug and charge and a schedule setup on the car.

Couple of queries, would it not be best if the charge power on the app was maybe in a setting somewhere rather than a bar on one of the main tabs? seems a little unnecessary being so easily available and also doesn’t explain what it is until you make a change and can kinda assume. Just a discussion/suggestion on this one.

Also any explanation what the tab of Automatic/Homey does? was looking intently at this one and assume maybe automatic charge when plugged in? but not sure.

Appreciate the app as now I can have my relatively dumb charger a little more integrated with my homey setup and potentially down the line work with a solar/battery setup

34

Subject: OCPP Server 1.0.10 - Energy value falls back to an old reading (NexBlue, OCPP 1.6J)

@DnetLabs_BV
The Energy value (meter_power) sometimes jumps back to an older reading and stays there until the next charging session, when it jumps up to the real value again. Any kWh total based on it counts the same energy twice.

The charger itself is fine: its session kWh match, and a fresh install of the app read the correct
value (933.6 kWh) while the old install still showed 838.0.

What we see (7 times since mid-Sep):

  • The old reading is always one from between two sessions, often the value at an earlier Homey restart.
  • Most cases happen right after a Homey restart; two happened during a charge, after which the value stopped updating until the next session.

Suggestions:

  • Don’t restore meter_power from a stored value at start-up or reconnect.
  • Never accept a lower register value (it only counts up), or one with an older timestamp.
  • Keep using MeterValues after a restart, even for a transaction the app no longer knows.

Happy to send the Insights data or run a test.
PS will also send to homey at dnetlabs dot co

35

Hi @KevRae , the Automatic/Homey picker isn’t “charge when plugged in.” It’s Homey’s standard setting for who controls the charge power, added in Homey 12.13:

  • Automatic: the charger uses its own logic and limits.
  • Homey: the charger follows the target power, which is the power bar.

It’s also a flag that flows can check before they change the power (“The target power mode is …”).

I tested it on my NexBlue with app 1.0.10:

  • Switching to Automatic removes Homey’s limit: the charger went straight back from 8 A to 16 A, the most my car takes (11 kW).
  • The “Set the target power” flow card switches to Homey by itself, and it starts or stops charging.
  • Moving the power bar by hand does not switch the mode. The charger still followed the bar even on Automatic.

For solar or battery control later, use the “Set the target power” flow card. To give control back to the charger, set the mode to Automatic.

@DnetLabs_BV, is it intended that a power-bar change still applies while on Automatic? Homey’s developer docs say Automatic should ignore it.

And thanks for the “Maximum charge current” setting in 1.0.10, which answers my earlier question about the 11 kW maximum (post 23). With 32 A set, the “Set the target power” card now goes up to 22 kW. Works perfectly.

36

Thanks for the reaction. We are sending you a new test release lets debug this together and if it works, we can publish an update.

Regards,

Dnet Labs

37

Hi all,

Thank you for everyone reaching out to us with feature requests.
After validation, we’ve submitted version 1.0.16 of the OCPP app to Homey for certification.

Everything in it comes from customer requests and reports, and each change was tested on real chargers by the customers who asked for it.

The main changes are mostly about enabling you to do your load balancing with Homey Pro (i.e. Charge car with the PV surplus amount at a given time, pause charging when there is no surplus, etc)

What’s cooking?

  • Chargers with two outlets (e.g. Chargestorm Connected 2): each outlet is added as its own device.
  • Fix: Per-phase L1–L3 current and voltage no longer disappear when the charger is idle.
  • Fix: Power and current go to 0 as soon as charging stops.
  • Fix: The energy meter no longer jumps back to an old reading after a restart.
  • Charge current limits keep working after an app restart during a charge.