Thank you. I’ll give it a go and share the results!
1 Like
Just FYI for folks and maybe to make things easier for the future, an older integration for volkswagen GitHub - robinostlund/homeassistant-volkswagencarnet: Volkswagen Carnet Component for home assistant seems to now support ID cars which I believe was the reason for this integration?
Maybe might make sense to merge the two now? I have been using it for over a month now with my ID.4 and seems to work good enough and no weird errors in logs
Hi all quick Q.
have got HA up and running with the API. Thank you.
Where I am having trouble is I want it to send me notifications for my car to my phone. And notifications for my wife’s car to her phone.
Is that even possible?
Thanks
Mike
Scrub that, got it working
BUT
Any idea why the “Switch” alongside my Car name (Passat GTE) keeps switching off? Its seems to do it if I switch pages or If I start charging by the car, but also seems to do it at random.
Hello,
since yesterday i have this error:
{‘error’: {‘message’: ‘Bad Gateway’, ‘errorTimeStamp’: ‘2024-10-29T11:23:39Z’, ‘info’: ‘Looks like your service has expired. Please update your service subscription.’, ‘code’: 4104, ‘group’: 4, ‘retry’: False}} in domain climatisation
The Subscription is okay. End is 02.2026 and the VW IPhone App ist Working.
Has Someone a tipp?
Jörg
No, a PHEV is not supported by the current implementation.
See https://github.com/mitch-dc/volkswagen_we_connect_id/blob/97a83609bf2eba94b5f2ba1960609978201384dd/custom_components/volkswagen_we_connect_id/__init__.py:
These cars are supported:
SUPPORTED_VEHICLES = [“ID.3”, “ID.4”, “ID.5”, “ID. Buzz”, “ID.7 Limousine”]
On the other hand, if you are a programmer, you may probably change the code.
I did this for the e-Up. See my contributions in this thread. Works now since August. I am thinking to ask for a pull request at github to integrate my changes.
sorry, wrong reply.
I have the same issue since today. Did it resolve automagically? My subscription is ending at 21-nov-2025, which is a year from now. The VW app isn’t working for me.
Same here. Added integration first time with polling interval 150 seconds on 2024-11-24 and it seem to work but has this specific recurring error messages in the log. It is always prefixed with the reference to attribute climatisationTemperatureOutside, maybe a mismatch in supported sensors somewhere?
App is working OK, so no blocking.
Anyone knows how this can be tuned?
Unknown attribute climatisationTemperatureOutside with value {‘error’: {‘message’: ‘Bad Gateway’, ‘errorTimeStamp’: ‘2024-12-01T09:44:35Z’, ‘info’: ‘Looks like your service has expired. Please update your service subscription.’, ‘code’: 4104, ‘group’: 4, ‘retry’: False}} in domain climatisation
Same here, no contact since yesterday afternoon, subscription still active, App is working.
Had a problem that the integration did no longer start: “OAuth 2 MUST utilize https”
After following Unexpected exception : OAuth 2 MUST utilize https · Issue #285 · mitch-dc/volkswagen_we_connect_id · GitHub
From another post:
Log in to Volkswagen ID and accept new conditions.
everything now works again.
Had the issues as well, to fix it I have done these steps: a) restart HA b) login at: Volkswagen ID
And agree to the new privacy rules. This pop up as first question after login at volkswagen page.
C) go back to HA - the Integration work fine again.
Fixed it for me as well, thanks for the tip!
This worked for me, but last night the integration stopped working again. I logged again in at Volkswagen ID, but no popup this time. App works. Is it just me?
Edit: 5 minutes ago it suddenly started working again…
Could not login to Volkswagen Connect, please check your credentials and verify that the service is working
no matter what i do it keeps giving me this message
who can help me ?
Has anyone been able to configure for the ID.7 Tourer? Even though the Volkswagen app works and all t&c on the website (.be and .de) are accepted the integration comes back with ‘invalid authentication’.
log in to the car-net website, agree with the data privacy agreement, reload the integration, now it should work…
it seems that after my car had a new update it no longer works
i had ver. 3.5 now ver. 3.7
or do people just have it working on 3.7?
Cannot connect. I tried removing the entry and adding it again, I get this error:
Traceback (most recent call last):
File "/config/custom_components/volkswagen_we_connect_id/config_flow.py", line 65, in async_step_user
info = await validate_input(self.hass, user_input)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/volkswagen_we_connect_id/config_flow.py", line 39, in validate_input
await hass.async_add_executor_job(we_connect.login)
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.13/site-packages/weconnect/weconnect.py", line 184, in login
self.__session.login()
~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/lib/python3.13/site-packages/weconnect/auth/we_connect_session.py", line 76, in login
response = self.doWebAuth(authorizationUrl)
File "/usr/local/lib/python3.13/site-packages/weconnect/auth/we_connect_session.py", line 253, in doWebAuth
afterLoginResponse = self.get(afterLoginUrl, allow_redirects=False, access_type=AccessType.NONE)
File "/usr/local/lib/python3.13/site-packages/requests/sessions.py", line 602, in get
return self.request("GET", url, **kwargs)
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/weconnect/auth/we_connect_session.py", line 69, in request
return super(WeConnectSession, self).request(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
method, url, headers=headers, data=data, withhold_token=withhold_token, access_type=access_type, token=token, timeout=timeout, **kwargs
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/weconnect/auth/openid_session.py", line 188, in request
raise InsecureTransportError()
oauthlib.oauth2.rfc6749.errors.InsecureTransportError: (insecure_transport) OAuth 2 MUST utilize https.
I have had the same.
Had to log in to the Volkswagen website and accept T&C changes that are shown right away.
Then reloaded integration and it worked again.