EVSE Keba P30 integration

[kurt-Biesemans]

@vic

slider-entity-row

@vic Thank you for your support. I’m new to HA so learning a lot

[kurt-Biesemans]

Got your dashboard up-and-running except for 1 error that I still have. Any idea what I’m doing wrong?

[vic]

Hi,

that is an input_number that I have created as helper.
You can go under setting/devices/helpers and create a new input_number as shown here below:

[kurt-Biesemans]

Wonderful!! It works. Thank you

[kurt-Biesemans]

And do you have an automation that sets the max_current when changing the slider?

[vic]

Hi, sorry for the late reply, I was traveling…
Yes, I forgot to mention that I have created an automation to update the max current based on the input_number:

alias: Set Keba max current slider
description: ""
mode: single
triggers:
  - entity_id: input_number.keba_set_max_current
    trigger: state
conditions: []
actions:
  - data_template:
      current: "{{states.input_number.keba_set_max_current.state | round(0)}}"
    action: keba.set_current

I have also another automation to set the message to be sent to the Keba display:

alias: Set Keba message
description: ""
mode: single
triggers:
  - entity_id: input_text.keba_set_text_display
    trigger: state
conditions: []
actions:
  - data_template:
      message: "{{states.input_text.keba_set_text_display.state}}"
      data:
        min_time: 2
        max_time: 600
    action: notify.keba_notifier

[kurt-Biesemans]

Hi Vic,
Sorry to come back but…I don’t get it to work. Would you mind to share a screenshot of your automation? Hereby mine that is not working

[vic]

Hi Kurt,

which error(s) are you getting?

Can you share the code of your automation?
You can get the code going on the 3 dots inside the automation and pressing “Edit in YAML”.

The effect should be that when you move the slider “Changing current”, the element “Set max current wallbox” should also change accordingly.

[AmphereB]

Hi @dannerph
Couple weeks ago i saw your earlier card (the one with withe BMW i3) and that inspired me to make something similar.

I’m not satisfied yet
For ex; “Fastvakt Av” is an on and off function for a automation that check all 3 phases while charging and adjust the output to the charger while charging from the grid. Basically not to overload 25A in winter when sauna is on

Now I will like to do the same but to watch PV production and once again saw your post.
Is it possible to see your automation and helper for this?
(and yes the ugly stop button also have to be fixed )

[AmphereB]

And here is a automation.
CAUTION!!
This is not the same thing as the real load balancer!

alias: Lastbalaserare billaddare
description: Control EV charger amps to avoid overcurrent
triggers:
  - entity_id:
      - sensor.smart_meter_ts_65a_3_strom_fas_1
      - sensor.smart_meter_ts_65a_3_strom_fas_2
      - sensor.smart_meter_ts_65a_3_strom_fas_3
    trigger: state
conditions:
  - condition: state
    entity_id: sensor.bmw_wallbox_connect_charging_power
    state: Charging
    enabled: false
  - type: is_powered
    condition: device
    device_id: 8052e68d00690dc5742ba0e64bb23f9a
    entity_id: b63a9990e916d6864e2b4a843dfdd7d9
    domain: binary_sensor
actions:
  - data:
      value: >-
        {% set min_charge_current = 6 %} {% set max_charge_current = 16 %} {%
        set max_total_current = 17 %}

        {% set c1 = states('sensor.smart_meter_ts_65a_3_strom_fas_1')|float %}
        {% set c2 = states('sensor.smart_meter_ts_65a_3_strom_fas_2')|float %}
        {% set c3 = states('sensor.smart_meter_ts_65a_3_strom_fas_3')|float %}
        {% set measured_current = [c1, c2, c3] | select('is_number') |
        map('float') | max | default(none) %}

        {% set current_charger_setting =
        states('number.bmw_wallbox_connect_charging_current')|float %}

        {% set new_current = max_total_current - measured_current +
        current_charger_setting %} {% if new_current >max_charge_current %} {%
        set new_current = max_charge_current %} {% endif %} {% if new_current <
        min_charge_current %} {% set new_current = min_charge_current %} {%
        endif %}

        {{ new_current|round(0, 'floor') }}
    target:
      entity_id: number.bmw_wallbox_connect_charging_current
    action: number.set_value
    enabled: true
mode: restart

[iak (Kai)]

Modbus and web page feature is now available for Keba P40, did anyone already played around with it?

[Patrick2P (Patrick)]

Hi everyone,
I’m using a Keba P30 x-series wallbox with Home Assistant (core 2026.x, HA OS).
The integration is configured via configuration.yaml:

text

keba:
  host: 192.168.188.xxx
  rfid: "xxx"

The RFID xxx is configured in the wallbox as a local RFID card and has status ACCEPTED.
Authorization settings in the Keba web UI:

• Authorization: ON
• Online authorization mode: FirstLocal
• Offline authorization mode: OfflineLocalAuthorization

In Home Assistant I have an automation that calls:

text

actions:
  - action: keba.authorize
    data: {}
  - action: notify.family_phones
    data:
      message: BMW Laden gestartet

The automation is triggered correctly (notification arrives), but:

• the car does not start charging
• in the Keba web UI the RFID list does not update the “Last used” timestamp for xxx
• in the HA logs I sometimes see Command rejected: TCH-ERR:no need for start

Keba is reachable via UDP and the integration shows status / sensors correctly.
I also had a short Modbus config, but I removed it again after seeing Modbus keba contain no entities warnings.

Has anyone got keba.authorize working reliably with P30 x-series and current HA versions?
Do I misunderstand the purpose of keba.authorize, or is there a known workaround (e.g. using keba.enable only, or a specific authorization mode / firmware requirement)?

Any hints or working examples would be highly appreciated.

Best regards

Patrick