Custom Integration: Volkswagen WeConnect ID (Europe)

wil · November 24, 2025, 9:15pm

I have looked into this. This error message is from the weconnect python package that the Custom integration uses. This is available at GitHub - tillsteinbach/WeConnect-python: Python API for the Volkswagen WeConnect Services

It clearly states:

WeConnect-python will reach end of life this year. It will be repalced by CarConnectivity which will provide equal functionality but for more brands such as Volkswagen, Skoda, Seat, Cupra. Developers should start to check if moving to CarConnectivity is an option.

Looks like we reached the point and Volkswagen disabled the old API. There seems to be no chance for this old integration to work again.

To bad. It worked very well the last years. Bye. Bye!

ColinRobbins · November 24, 2025, 9:17pm

I did not worry about keeping history or entity names. I added the new integration, updated my dashboards and automations, then deleted the old integration.

wil · November 24, 2025, 9:19pm

Before I will migrate to this, please tell us how to change the entry names. Did you change any sources of the new integration? If yes, would you provide us with the changes please?

Any help is appreciated.

sigvind · November 24, 2025, 9:46pm

Also, if anyone here tried both CarConnectivity with plugins, and home-assistant-volkswagencarnet it would be useful with a short point of view of what would be the best solution to migrate to.
I liked the idea of a docker container sending updates via MQTT, but maybe its somewhat more complicated to set up?

wgumaa · November 25, 2025, 6:10am

I have both but running only the volkswagencarnet at the moment as it has a lot more sensors and entities. CarConnectivity - addon has some other features but still needs more.

BennyOtt · November 25, 2025, 9:09pm

I’ve been looking into this since yesterday:

The Python package seems to be still being updated by Till Steinbach, so it might work again once the new version is installed.

github.com/tillsteinbach/WeConnect-python

Authorisation sometimes returns a 303 response

offen 08:41PM - 24 Nov 25 UTC

HughMacdonald

I've been having some issues with my app today, and I've tracked it down to the …auth url returning a 303. What I end up seeing is this: ``` requests.exceptions.MissingSchema: Invalid URL '/u/login?state=<redacted>': No scheme supplied. Perhaps you meant https:///u/login?state=<redacted>? ``` This is coming back from this line: https://github.com/tillsteinbach/WeConnect-python/blob/7ffb9beee5253f4ee0268b663a1af930abae3b78/weconnect/auth/vw_web_session.py#L101 The `location` coming back with this 302 response is only a relative URL, so on the second loop around, it raises the exception listed above.

I’ve already tinkered with it a bit myself, and with AI assistance, I managed to fix the Python problem, but it seems the connection only lasts for 1.5 hours, and then the entire integration terminates. I can’t say for sure what’s causing this yet, but it could also be an API issue at VW, because I was already experiencing this before the login change.

Regarding robinostlund’s product:

Generally, it seems to work well, but I’m missing some entities that I had with the We Connect ID integration (e.g., Charging Mode and Charging State).

wil · November 25, 2025, 10:17pm

Thats what I already mentioned. Looks like the WeConnect API is discontinued by Volkswagen.

If you get it worked again it would be a big surprise for me. Just post the code changes here and make many people happy!

sigvind · November 28, 2025, 7:43am

For others:
I went for the homeassistant-volkswagencarnet integration following @ColinRobbins steps, after first listing out all the old entity names to keep a reference to them.
Then, after removing the old integration, I made template sensors with the old entity names translating from the new corresponding sensors, for a couple of sensors that I’m particularly interested in keeping consistency of long term data stored separately in InfluxDb.

Each of these templates look like this, where vw_id4 is the prefix I configured in the new integration, and id_4_pro_4motion is the prefix of the old ones:

# Odometer
      - name: "sensor.id_4_pro_4motion_odometer"
        unique_id: id_4_pro_4motion_odometer
        state: "{{ states('sensor.vw_id4_odometer') }}"
        state_class: measurement
        device_class: distance
        unit_of_measurement: "km"
        icon: mdi:car-cruise-control
        friendly_name: "ID.4 Pro 4MOTION Odometer"

The new integration works alright and seems to offer very similar sensors as the old one.

wgumaa · December 18, 2025, 1:36pm

Hi all,

Since this add on is no longer supported and probably doesn’t work I have moved to the VW Connect (Carnet) integration.

I writing because an important feature seems to have been removed from the either the repo or the api. And that is the “parked” entity. Why this is important is that I use it in automations to control the gate and garage of the house.

Has anyone figured a way to identify whether a car is moving or parked?

dwp · December 19, 2025, 8:53pm

I have also moved to VW Connect for my ID.3
Not sure what you are looking for but I can see a sensor for Parking time along with Vehicle Moving along with a position sensor which reports that the car is currently on my driveway.

wgumaa · December 20, 2025, 5:06am

Interesting because i dont have it for my ID5! I see the sensors but they are greyed out and says not being provided by the integration

I am using this integration.

Are we using the same?

https://github.com/robinostlund/homeassistant-volkswagencarnet

dwp · December 21, 2025, 4:02pm

Yes GitHub - robinostlund/homeassistant-volkswagencarnet: Volkswagen Carnet Component for home assistant v5.3.4

I see today that the Electric_Climitisation switch is no longer being provided in the latest version. I just checked an an issue has been raised for this one. Perhaps there are issues also for yours if you look on GitHub?

wgumaa · December 22, 2025, 5:45pm

@dwp for me the climate has become a “climate” entity

dwp · December 22, 2025, 6:04pm

Thanks yes I spotted that when I dug a bit deeper into what had changed.

pplucky · December 22, 2025, 7:40pm

Have you tried reloading the integration, removing/adding the device or even reinstalling rhe custom component?

I have an Id3 and it appears properly to me.

jeromarsan · January 5, 2026, 6:11pm

The same for me since today with homeassistant-volkswagencarnet

binary_sensor.wvxxxxxxxxxxxxxxxxxxx_doors_locked
sensor.wvxxxxxxxxxxxxxxxxxxx_odometer
device_tracker.wvxxxxxxxxxxxxxxxxxxx_position

Removed from the integration or removed by VW Carnet ?

pangadogu · January 12, 2026, 12:23pm

Hi Sebu, I have the same problem. Have you found a solution?

Sebu · January 12, 2026, 2:50pm

I ended up removing the charging locations from the car. As all my charging features are controlled through HA, I actually don’t need the functionality from the car at the end of the day.

jopl · January 13, 2026, 1:05pm

Hi, it’s true, everything works fluently well and better, but the “preheating” state, which precedes approx. 15 minutes before “heatingAuxiliary” is not appropriately signalized by the plugin. It’s there any chance to change it with new update, please?

wgumaa · January 13, 2026, 6:43pm

@jopl I am not the owner of the itegration! I just use it like you.

You need to raise the issue here:

https://github.com/robinostlund/homeassistant-volkswagencarnet