Cupra Born charging issues

[amzaldua]

Hi,
This issue is not related to this integration, but I need to learn about the experiences and opinions of other Cupra Born users in this regard. Since the software update to version 3.2.1 for the Cupra Born, I have encountered problems with charging. For instance, if I pause the charging for 4 minutes or longer, the car goes into an error state, and I cannot resume the charging process. This problem only arises when I manage the charging with an external charger. I am unable to schedule the charging, use surplus solar energy, or take advantage of the excess power from my home when no appliances are in use. Has anyone faced a similar situation? I can "address" it through automations for now, but the ideal scenario would be for the car to function correctly without requiring external solutions.

Thanks.

[daernsinstantfortress]

Mine is getting 3.2.1 as we speak, so I'll report back after... I've heard similar stories, though, so it's not an unknown issue.

What are you doing in HA to resolve?

[amzaldua]

Yes, I know. I'm also from Spain.
Two common factors among the affected users are: the H43 hardware version and the use of the Wallbox Pulsar Plus charger. Do you have the same variables, or is it different in your case?

[Vayatoalla]

not the same, I don't have the Wallbox.

[amzaldua]

What are you doing in HA to resolve?

I use the following automation to force the car to wake up:

alias: "CUPRA: Cambiar objetivo carga para iniciar"
description: >-  
  Debido a un problema con la carga en la nueva revisión de software 3.2.1 es necesario interactuar con el vehículo para sacarlo del modo de error, en este caso cambiando el objetivo de carga, y así poder iniciar la carga con el WallBox.
trigger:
  - platform: state
    entity_id:
      - sensor.wallbox_portal_status_description
    to: Waiting for car demand
    for:
      hours: 0
      minutes: 5
      seconds: 0
condition:
  - condition: numeric_state
    entity_id: sensor.cupra_born_state_of_charge
    below: 80
action:
  - device_id: 70163440b2315732e77ccbd894d9b09a
    domain: number
    entity_id: 33726c1e14058ec8c85d08411c87ed9d
    type: set_value
    value: 70
    enabled: true
  - delay:
      hours: 0
      minutes: 5
      seconds: 0
      milliseconds: 0
  - device_id: 70163440b2315732e77ccbd894d9b09a
    domain: number
    entity_id: 33726c1e14058ec8c85d08411c87ed9d
    type: set_value
    value: 80
    enabled: true
mode: single

[amzaldua]

Other bugs in 3.2.1 version are:...

I have also noticed that when I connect the car to my home Wi-Fi, it doesn't generate any kind of traffic. Absolutely nothing.
But I'm not sure if this bug is related to the latest update or if it was already present before.

[Vayatoalla]

Hi. Yes I have something similar but with Openhab. I am using Homeassistant only to integrate some devices (like Cupra) with Openhab.

[daernsinstantfortress]

https://www.cuprabornforums.com/viewtopic.php?p=5633#p5633

[amzaldua]

Thanks!
In other Volkswagen forums, ID.3 users seem to be experiencing the same issues as well.

[amzaldua]

Mine is getting 3.2.1 as we speak, so I'll report back after... I've heard similar stories, though, so it's not an unknown issue.

@daernsinstantfortress, have you encountered any issues with the new 3.2.1 upgrade?

[daernsinstantfortress]

So far, so good, but my electricity provider is currently offering a lot of cheap power, so I've not really been able to test delayed charging yet...

[amzaldua]

No need to perform any delayed charge to check if the vehicle charging works normally. Plug the charging cable into the car, pause the charging from the external charger for more than 4 minutes, or its application (it's critical not to interact with the car either directly or indirectly), and try restarting the charge from the charger itself or its application. If the charge restarts, everything is okay; if not, welcome to the club.
The purpose of this is to simulate the charge management as the charger itself would do. We need to set up the car as immediate charging to prevent its own manager from interfering with the test.

[daernsinstantfortress]

What's interesting is that the car has been stopping and starting charge repeatedly during a charging session (Octopus controlling the charging means very odd charge cycles!) but this has not reported a failure yet. In my case, Octopus is integrated with the charger as well, so the car plays no part in any of this and is just set to 100% target.

My guess is that it's a special case when first connected to the charger. I'll give it a test later though.

[Yorkie71]

I don't have a charger which I can schedule so I've never had this experience but I recall reading somewhere (but can't remember where now), that the MEB cars can throw up an error if it initiates a call for a charge but the charger does not supply it, as in the schedule is not active but not having a smart charger, I have not been able to test that. I'm getting the GivEnergy EV charger fitted soon so that will change.