Wallbox EV charger Pause/Resume switch functionality

Feature Requests
1

Comments

@storacm

storacm commented 19 hours ago

Feedback

Hi,
I have been using the Wallbox Integration for my Commander 2 since beginning of 2023. It seems it operates differently since some time back. The Pause/Resume function is unavailable unless one has unlocked the wallbox first (it did not use to be like this). BEfore the pause/resume swithc was available as soon as the car was connected.
This new behaviour screws up the the function with automatic charging thru EV Smart Charging integration as the automatic charging of the Wallbox starts as soon as one unlocks the Wallbox. It would be better if one could get the functionallity like before that you can pause/resume the charging once the car is connected without havin to unlock first.
As the Wallbox Integration needs the admin Wallbox credentials when setting it up , this means the one who can use the pause/resume button is Admin anyway. Therefor it makes no sense in my opinion to first have to unlock before the pause/resume button gets accessable.

If I first unlock the Wallbox it will automatically start charging even if the EV Smart Charging integration does not require charging for the moment.

It would be great if we could have the old functionality your Wallbox Integration back again where the pause/resume button is available all the time :slight_smile:

Anyone else having similar trouble with the charging setup?

2

Would recommend to solve this with automations. The on/off is cloud related and doesn’t work unless the charger is unlocked. I also use EV smart charging, my wb Pulsar plus is rooted though so i control it locally.

For inspiration my automation below:


alias: EV Smart Charging
description: ""
trigger:
  - platform: state
    entity_id:
      - sensor.ev_smart_charging_charging
    to: "on"
    for:
      hours: 0
      minutes: 0
      seconds: 0
    id: "on"
  - platform: state
    entity_id:
      - sensor.ev_smart_charging_charging
    to: "off"
    id: "off"
  - platform: state
    entity_id:
      - sensor.wallbox_status
    id: check charging
    to: Charging
    for:
      hours: 0
      minutes: 0
      seconds: 0
  - platform: homeassistant
    event: start
    id: restart
  - platform: state
    entity_id:
      - sensor.wallbox_status
    from: unavailable
    id: restart
condition:
  - condition: or
    conditions:
      - condition: state
        entity_id: sensor.wallbox_status
        state: Paused
      - condition: state
        entity_id: sensor.wallbox_status
        state: Charging
action:
  - choose:
      - conditions:
          - condition: trigger
            id: "on"
          - condition: not
            conditions:
              - condition: state
                entity_id: sensor.wallbox_status
                state: Charging
        sequence:
          - service: switch.turn_on
            data: {}
            target:
              entity_id:
                - switch.wallbox_charging_enable
      - conditions:
          - condition: trigger
            id: "off"
          - condition: state
            entity_id: sensor.wallbox_status
            state: Charging
        sequence:
          - service: switch.turn_off
            data: {}
            target:
              entity_id:
                - switch.wallbox_charging_enable
      - conditions:
          - condition: or
            conditions:
              - condition: trigger
                id: check charging
              - condition: trigger
                id: restart
        sequence:
          - if:
              - condition: and
                conditions:
                  - condition: state
                    entity_id: sensor.ev_smart_charging_charging
                    state: "off"
                  - condition: state
                    entity_id: sensor.wallbox_status
                    state: Charging
            then:
              - type: turn_off
                device_id: 011eb97a0b27faf7ac9c7378ef475dff
                entity_id: 70ff19bf5027b240420492032eacb858
                domain: switch
            else:
              - if:
                  - condition: and
                    conditions:
                      - condition: state
                        entity_id: sensor.wallbox_status
                        state: Paused
                      - condition: state
                        entity_id: sensor.ev_smart_charging_charging
                        state: "on"
                then:
                  - type: turn_on
                    device_id: 011eb97a0b27faf7ac9c7378ef475dff
                    entity_id: 70ff19bf5027b240420492032eacb858
                    domain: switch
    default: []
mode: queued
max: 10

You could in your case play around with the availability of the switch, eg make it a condition or a trigger:

  - condition: not
    conditions:
      - condition: state
        entity_id: switch.wallbox_portal_pause_resume
        state: unavailable
    enabled: false

Alternatively you can try to root your wallbox, information is available on this forum:

or github:

1 Like
3

Thank you for your reply. Then I probably will have to try with automation.

I did not know it is cloud related. the thing is it used to be differrently.
I had issues with my Commander 2 with LTE, that it started charging without unlocking and resuming. It simply started charging when the car was connected.
SO I contacted Wallbox and their support said it shoudl not be like this, and then all the standard questions / answers with rebotting in whic order to what etc.
About a month later there was a firmware update and it did not start charging when simply connecting the car. But shortly after the problem with the inaccessable pause/resume button occurred. So I thought it was something that the maker of the Wallbox Integration had added.

I will maybe even add a zone function and or charger connected from the car in the automation for it only to run when the car connected at home.

Thanks again

4

The functionality is indeed that the on/off button is only available if the wallbox is unlocked. Standard way of working is that the wallbox auto locks to prevent abuse. In order to start charging you would need to unlock first after which charging commences and the on/off switch becomes available.

I have another automation available which does what you suggest. Based on the car API itdetermines the location of the car. If the car API reports home and the charger is connected then the Wallbox unlocks. The earlier automation shared will subsequently arrange auto pause (unless the EV Charging integration Boolean is on in which case it continues charging)

It also relocks but that predates the auto lock feature which Wallbox now supports natively.

alias: Unlock and relock Wallbox charger
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.charging_cable_connected
    to: "on"
    for:
      hours: 0
      minutes: 0
      seconds: 0
  - platform: zone
    entity_id: person.skoda_enyaq
    zone: zone.home
    event: enter
condition:
  - condition: and
    conditions:
      - condition: zone
        entity_id: person.skoda_enyaq
        zone: zone.home
      - condition: state
        entity_id: binary_sensor.charging_cable_connected
        state: "on"
action:
  - device_id: 2f3e39789d7661c5a47178ebf0b0d608
    domain: lock
    entity_id: lock.wallbox_portal_locked_unlocked
    type: unlock
  - delay:
      hours: 0
      minutes: 2
      seconds: 0
      milliseconds: 0
  - device_id: 2f3e39789d7661c5a47178ebf0b0d608
    domain: lock
    entity_id: lock.wallbox_portal_locked_unlocked
    type: lock
mode: single
5

One more question.
When I look at the sensor.ev_smart_charging_charging entity in an UI automation I can only see “available” or “unavailable” as state. But when I look at the actual entity it shows “on” or “off”. Why is this?
It mkae sit impossible to use UI when trying to make an automation.

I woud prefer to setup an automation thru UI so other in the family can follow it easier if I am not home than having to look at yaml.

6

Same for me, it’s probably because the sensor does not provide the possible states to HA.

If you use the gui you can just type on or off. It will work, no need to use yaml

7

Thanks for the confimation. I tried just putting the “on” / “off” etc. in manually and it works like a charm.

Thanks so much for all the support :slight_smile:

1 Like