Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alfen solar charging boost switch #1288

Open
Rep-Hueman opened this issue Aug 25, 2024 · 6 comments
Open

Alfen solar charging boost switch #1288

Rep-Hueman opened this issue Aug 25, 2024 · 6 comments

Comments

@Rep-Hueman
Copy link

Feature request switch boost charging Alfen in HA

alfen solar charging boost

I don't know if there is already a back office key for it.
I have the latest firmware version 7.0. 2-4322.
Charging on the generated power from the solar panels works perfectly.
I just want to be able to charge quickly every now and then. (Boost Charging)
This is currently only possible via ACE Service installer or the MyEve app, but it would be nice if there was a switch for this in Home Assistant

@drc38
Copy link
Collaborator

drc38 commented Sep 11, 2024

You'd need to create a switch and automation in HA, then use ocpp configure action. Assuming there is a custom configuration key for it.

@netmikey
Copy link

netmikey commented Sep 14, 2024

Hi, I'm also interested in this functionality.

I had a look at the specification document from Alfen ACE NG9 Backoffice Configuration keys 7.0.0.pdf. I didn't find anything related to boost but I found these 3 configuration keys:

SC-Mode

SolarCharging optimizes locally generated, excess power as measured by the smart meter. Must have Active Loadbalancing configured.

  • Green: SC-GreenShare is configurable
  • Comfort: SC-ComfortLevel is configurable

Possible values: Off / Green / Comfort

SC-GreenShare

Only used if "SC-Mode" is configured as 'Green', value in percentages.

  • If set to 0%, charging at minimum power is always possible.
  • If set to 100%, charging will only take place if minimum power to charge is measured as excess power on smart meter

Charging speed will increase to match excess power as measured on smart meter.

Values between: 0 - 100

SC-ComfortLevel

Only used if “SC‐Mode” is configured as 'Comfort'. Charging will always start irrespective of amount of excess power as measured on smart meter. Value, in kW, is configured as desired minimum charging power.
Charging speed will increase above Comfort Level to match excess power as measured on smart meter, never exceeding configured maximum current. If Comfort Level exceeds maximum available current, charging will not exceed maximum.

Values between: 1,4 - 22

From reading this, it seems to me that SC-GreenShare and SC-ComfortLevel could be set to the desired values once and that it might be enough to control SC-Mode from HomeAssistant. Setting this to Off and resetting it to one of the other modes (maybe using an automation) could give the same functionality as the boost knob in the Alfen apps.

This is just from reading the docs, I'll try this out when I have time. ;-)

@netmikey
Copy link

@drc38 Are the ocpp actions documented somewhere? Is there a way to add an entity for reading a custom configuration key?

@drc38
Copy link
Collaborator

drc38 commented Sep 14, 2024

The general actions are documented in the ocpp standard. If you select one from the list there is example input data also. The response, if any, for configuring a field is returned in the timestamp_config_response sensor attributes.

@netmikey
Copy link

Putting together an entity based on an attribute of timestamp_config_response (which will hold responses for different configure actions) seems to be a bit tedious.

Would you guys consider adding Alfen's custom configuration keys as entities?

@netmikey
Copy link

netmikey commented Nov 11, 2024

Just for reference if someone needs to solve this particular problem:

I managed to work around the lack of support for the Alfen-Specific OCPP keys by adding a template select and an automation.

The template select represents the SC-Mode and allows changing it while the automation polls the charger for the current SC-Mode value so that if it decides to change the mode from outside HA for whatever reason, the new value ends up in HA eventually. Note that the delay between asking for the value and the value actually appearing in the "special response entity" sensor.ev_charger_timestamp_config_response might be up to somewhat around 20 seconds.

My template select looks like this (sorry, created via the UI):

Screen Shot 2024-11-11 at 21 33 45

My automation looks like this:

alias: Poll Solar Charging Mode from EV Charger
description: >-
  This non-OCPP-standard, custom manufacturer value doesn't get read/polled by
  the OCPP integration so it has to be polled manually.
triggers:
  - trigger: time_pattern
    minutes: /10
conditions: []
actions:
  - action: ocpp.get_configuration
    data:
      ocpp_key: SC-Mode
    alias: >-
      Perform action 'Open Charge Point Protocol (OCPP): Get configuration
      values for charger' for ocpp_key 'SC-Mode'
mode: single

I'd still welcome it if this integration made it easier to add custom OCPP keys somehow.

@Rep-Hueman : if you add this, you can create something like Alfen's "boost" feature by setting the SC-Mode select to "Off" to remove the Solar limit (=boosting) and then putting it back to "Green" or "Comfort" after some delay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants