[BUG] Login for VW account failed!
StefanoGiu opened this issue · 245 comments
Before you post a new issue - you must first check the following (and check the boxes with an "X" below)
- [V] 1.) Can you login using the smartphone app We Connect (not We Connect ID or We Connect GO) and interact with your car?
- [V] 2.) Please make sure that you can login into https://vwid.vwgroup.io/ and make sure that any "Terms and Conditions" are all checked
- [V] 3.) I do not have MFA enabled.
Environment
- Volkswagencarnet release with the issue: 4.4.65
- Last working homeassistant-volkswagencarnet release (if known): ??
- Home Assistant Core release with the issue: 2023.10.3
- Operating environment (Home Assistant OS/Supervised/Container/Core/venv): Core
- Car model and year: Golf 2022
- Country where the car was bought: IT
- Valid We Connect subscription: Y
- Have you verified that the We Connect service works via VW´s portal?: Y
Describe the bug
2023-11-17 12:44:21.181 WARNING (MainThread) [volkswagencarnet.vw_connection] Login for VW account failed!
2023-11-17 12:44:21.181 WARNING (MainThread) [custom_components.volkswagencarnet] Could not query update from volkswagen WeConnect
Steps to Reproduce
Restart HA or try to restart integration
Expected behavior
Integration to work properly
Traceback/Error logs
2023-11-17 12:44:21.181 WARNING (MainThread) [volkswagencarnet.vw_connection] Login for VW account failed!
2023-11-17 12:44:21.181 WARNING (MainThread) [custom_components.volkswagencarnet] Could not query update from volkswagen WeConnect
2023-11-17 13:05:07.087 ERROR (MainThread) [custom_components.volkswagencarnet.config_flow] Failed to login due to error: 'identity'
2023-11-17 13:05:14.144 ERROR (MainThread) [volkswagencarnet.vw_connection] Login failed for VW account, Token exchange failed
2023-11-17 13:05:14.144 ERROR (MainThread) [volkswagencarnet.vw_connection] Token exchange failed
Traceback (most recent call last):
File "C:\Users\stefa\AppData\Roaming.homeassistant\deps\Python311\site-packages\volkswagencarnet\vw_connection.py", line 348, in _login
raise Exception("Token exchange failed")
Exception: Token exchange failed
2023-11-17 13:05:15.014 ERROR (MainThread) [custom_components.volkswagencarnet.config_flow] Failed to login due to error: 'identity'
Yep, broken again
me too
Hello,
I've had the same problem for 6 hours. I guess after the WeConnect app was replaced by the Volkswagen app, the WeConnect servers were switched off. Login is currently no longer possible in Home Assistant. If I log in manually at https://vwid.vwgroup.io/ then everything works. Location here is Germany.
Having the same issue.
Has someone got another integration to work?
I have a Passat GTE 2018
Same issue.
I have a e-up! 2022
Has someone got another integration to work?
I have weconnect-mqtt running. If you can see your Passat in the new VW app, I am confident that you should get data with weconnect-mqtt.
It requeres more configuration though.
Same here. Location NL. With Passat GTE (2015) and e-Golf (2020)
Same
Same here, since today. Location D, Golf 8 (2020)
Log from HA:
Could not query update from volkswagen WeConnect
20:34:29 – (WARNUNG) Volkswagen WeConnect (benutzerdefinierte Integration) - Die Nachricht ist zum ersten Mal am 17:23:47 aufgetreten und erscheint 39 mal
Login failed for VW account, Token exchange failed
20:34:29 – (FEHLER) Volkswagen WeConnect (benutzerdefinierte Integration) - Die Nachricht ist zum ersten Mal am 17:23:47 aufgetreten und erscheint 78 mal
Token exchange failed
20:34:29 – (FEHLER) /usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py - Die Nachricht ist zum ersten Mal am 17:18:52 aufgetreten und erscheint 43 mal
[...]
Error fetching volkswagencarnet data: Failed to update WeConnect. Need to accept EULA? Try logging in to the portal: https://www.portal.volkswagen-we.com/
17:23:47 – (FEHLER) Volkswagen WeConnect (benutzerdefinierte Integration)
[...]
Could not login to volkswagen WeConnect, please check your credentials and verify that the service is working
17:19:01 – (WARNUNG) Volkswagen WeConnect (benutzerdefinierte Integration)
Login failed for VW account, Token exchange failed
17:18:59 – (FEHLER) Volkswagen WeConnect (benutzerdefinierte Integration) - Die Nachricht ist zum ersten Mal am 17:18:52 aufgetreten und erscheint 3 mal
same here. e-UP 2023.
log in manually at https://vwid.vwgroup.io/ works.
Instead of posting "I also have this issue", please give thumbs up on the first post instead. It's a much better way to confirm the bug, than annoying every other subscriber to this issue with no relevant info.
Thank you!
Same problem, I'd like to add that my car (Golf 8 ehybrid) had a software update. It's possible that the car itself isn't talking to the we connect servers anymore
again me too.
volkswagen t roc... of course manual login on web site works
I have the same problem.
I have removed and reinstalled the integration, I have verified the accout loging at WeConnect. If more information is needed, I'm happy to assist.
Logger: volkswagencarnet.vw_connection
Source: /usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py:367
First occurred: 14:40:54 (1 occurrences)
Last logged: 14:40:54
Token exchange failed
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py", line 348, in _login
raise Exception("Token exchange failed")
Exception: Token exchange failed
I hope it won't be the end of this beautiful integration, but I think the aren't so many possibilities as VW switched off We Connect (see #502).
It would be great to rewrite it to use https://pypi.org/project/weconnect as a backend instead of https://github.com/robinostlund/volkswagencarnet because the alternatives like https://github.com/mitch-dc/volkswagen_we_connect_id doesn't provide binary_sensors to enable/disable charging, requires the VIN when using the services and so on... Anyway a lot of work has to be done 😥
I solved it for now by triggering charge at the same time as my other car smart charges:
alias: Volkswagen MANUELL start
description: ""
trigger:
- platform: time
at: sensor.tesla_start_charging_time
condition:
- condition: device
device_id: 95XXXXXXXXXXXXXX
domain: device_tracker
entity_id: acXXXXXXXXXXXXXX
type: is_home
action:
- service: automation.trigger
data:
skip_condition: true
target:
entity_id: automation.test_uppfart_garage_start
mode: single
I hope it won't be the end of this beautiful integration, but I think the aren't so many possibilities as VW switched off We Connect (see #502).
It would be great to rewrite it to use https://pypi.org/project/weconnect as a backend instead of https://github.com/robinostlund/volkswagencarnet because the alternatives like https://github.com/mitch-dc/volkswagen_we_connect_id doesn't provide binary_sensors to enable/disable charging, requires the VIN when using the services and so on... Anyway a lot of work has to be done 😥
VW We Connect ID integration is also currently not working
VW We Connect ID integration is also currently not working
But that's due to the VW servers being down in the past hours, in fact the Volkswagen app wasn't working too. They are a lot unreliable recently!
VW We Connect ID integration is also currently not working
But that's due to the VW servers being down in the past hours, in fact the Volkswagen app wasn't working too. They are a lot unreliable recently!
I don't know if it's just me but for the last 14 days (since turning off the WeConnect app) the Volkswagen app has been down for about 8-10 hours every day
Like everyone here says, the "Volkswagen We Connect" service has been closed. Replaced by the "Volkswagen" service.
I hope work can be done as I really miss this.
Same happened to Skoda connect a few weeks ago when they updated platform (and its the same as VW uses). If so: maybe this thread could help? skodaconnect/homeassistant-skodaconnect#227
If so: maybe this thread could help? skodaconnect/homeassistant-skodaconnect#227
I've tried changing this line to the same value on your linked topic (i.e. "OneConnect/000000148 CFNetwork/1485 Darwin/23.1.0") but it still fails with Token exchange failed. Pretty predictable, as that's a Skoda API.
Probably we should extract the new values from the Volkswagen app connecting if someone is able to grab them.
Hi Folks, I have found a great solution provided by [Till Steinbach]
https://github.com/tillsteinbach/WeConnect-mqtt
I simply created a docker from the compose file provided and bingo, many more entities too. To get it into Home Assistant I created some MQTT entities and templates to convert to Miles from KM. Working well so far.
Hi Folks, I have found a great solution provided by [Till Steinbach]
(https://github.com/tillsteinbach)https://github.com/tillsteinbach/WeConnect-mqtt
I simply created a docker from the compose file provided and bingo, many more entities too. To get it into Home Assistant I created some MQTT entities and templates to convert to Miles from KM. Working well so far.
I am pleased this works for you. Sadly this link has gone. And I don't know how to use MQTT. Never mind.
Keep up the good work folks.
I have found a great solution provided by [Till Steinbach]
This is a MQTT variation of https://github.com/mitch-dc/volkswagen_we_connect_id, based on https://pypi.org/project/weconnect too. They are not comparable, unfortunately... this integration is way way better and start/stop charge commands, for example, are binary_sensors (i.e. switches instead of buttons).
IMHO this integration is the best one, it just needs to comply with the new VW API, but the UI still overlooks the others.
Had the same problem with EVCC after we connect app was disabled.
In EVCC I had to switch the vehicle template to ID instead of vw and now it works again.
See evcc-io/evcc#10832 - maybe ist helps or is an idea how to solve the problem here.
Same here, someday VW is the new Chamberlain :-)
Good evening,
I'm not sure if this is generally known, but VW closed "We Connect" and switched to "Volkswagen APP", so I think access to the Volkswagen portal has also changed.
And the software needs to be adjusted.
The same thing happened a few days ago in the ioBroker adapter vw-connect.
With kind regards
Bernd
Hi Folks, I have found a great solution provided by [Till Steinbach]
(https://github.com/tillsteinbach)https://github.com/tillsteinbach/WeConnect-mqtt
I simply created a docker from the compose file provided and bingo, many more entities too. To get it into Home Assistant I created some MQTT entities and templates to convert to Miles from KM. Working well so far.I am pleased this works for you. Sadly this link has gone. And I don't know how to use MQTT. Never mind.
Keep up the good work folks.
Correct link is https://github.com/tillsteinbach/WeConnect-mqtt
I am trying to set this up. I think I am missing something. I have the docker running. Logging is empty... with all logging ON (in portainer).
I do not see anything arriving in Home Assistant. I do have a working Zigbee2MQTT integrations but VWconnect is not showing in Home Assistant onder 'MQTT'. The addon in which the Zigbee2MQTT entities are available.
Does someone has description how to do this. The documentation here is too little for me I fear. https://hub.docker.com/r/tillsteinbach/weconnect-mqtt
Any help welcome! Thanks!
As you have MQTT loaded, in the Configuration.yaml file under mqtt: Sensors. I created the entities I wanted. By using MQTT Explorer which is a free download it is easy to find the relevant topic. I then used templates to convert to miles as in the UK.
Example Sensors
-
name: "VW_Odo_km"
unique_id: "VW_Odo_km"
state_topic: "weconnect/0/vehicles/WVxxxxxxxx/domains/measurements/odometerStatus/odometer"
unit_of_measurement: "Km" -
name: "VW_doorlockstatus"
unique_id: "VW_doorlockstatus"
state_topic: "weconnect/0/vehicles/WVxxxxxxxx/domains/access/accessStatus/doorLockStatus"
Thanks for the quick and helpful reply! Now I know it is working!
As you have MQTT loaded, in the Configuration.yaml file under mqtt: Sensors. I created the entities I wanted. By using MQTT Explorer which is a free download it is easy to find the relevant topic. I then used templates to convert to miles as in the UK. Example Sensors
- name: "VW_Odo_km"
unique_id: "VW_Odo_km"
state_topic: "weconnect/0/vehicles/WVxxxxxxxx/domains/measurements/odometerStatus/odometer"
unit_of_measurement: "Km"- name: "VW_doorlockstatus"
unique_id: "VW_doorlockstatus"
state_topic: "weconnect/0/vehicles/WVxxxxxxxx/domains/access/accessStatus/doorLockStatus"
How can you compare the whole MQTT broker and its Docker image + the WeConnect-mqtt Docker image with the simplicity of this integration?
You can't it was great!. Kudos to the Dev's. However it broke and now I have a working solution and happy! with putting a bit more effort it. Learnt a great deal in the process too. Already had MQTT and Portainer so was very quick to deploy. But agree not for everyone.
I tried to use MQTT integration, but it doesn't log anything on my MQTT server except two topics (status active and refresh timing). I have no info about my Golf car on MQTT server...
It works now, but on Oil level I get: Bad Gateway... Something went wrong. Please try to re-login. If the problem persists, please contact our support.
Btw, this mqtt module uses the weconnect module, that is using the "https://emea.bff.cariad.digital/vehicle/v1/vehicles" API.
I would appreciate if you'd continue your support for another plugin in another thread - this one here is for this HA-plugin.
You can't it was great!. Kudos to the Dev's. However it broke and now I have a working solution and happy! with putting a bit more effort it. Learnt a great deal in the process too. Already had MQTT and Portainer so was very quick to deploy. But agree not for everyone.
Hi, I can confirm the mqtt based integration (I am running in docker) seems to be really stable and I can read all those hundreds of topics.
One question though: did you try to also use some writables? I am mainly interested in enabling and disabling charging times and changing of charging current (I have some automations based on location). The topics are visible but I am not sure about the correct payload.
I would be nice to have a statement of one of the maintainers about the future of this HA-plugin. Does it make sense to wait for a fix or should I look for another solution; e.g. MQTT as mentioned above?
@squonk11 check the readme.md file in this repository: https://github.com/robinostlund/volkswagencarnet
Help is wanted due to that i can't keep maintaining this as i don't have any compatible car anymore.
@squonk11 check the readme.md file in this repository: https://github.com/robinostlund/volkswagencarnet Help is wanted due to that i can't keep maintaining this as i don't have any compatible car anymore.
o.k. thank you for the fast reply. For me this is probably too tricky to do - I do not even have an idea about how the login to WeConnect was working previously. And maybe some insider knowledge about the new login-scheme is needed.
I released a new beta version now with updated user agent headers as that seems to have solved it for the skoda integration. That is what i can do for now, so please try it. I am holding my thumbs 😄
@robinostlund thanks for the update, but I am still getting the same error:
2023-11-21 16:17:28.325 ERROR (MainThread) [volkswagencarnet.vw_connection] Login failed for VW account, Token exchange failed
2023-11-21 16:17:28.325 ERROR (MainThread) [volkswagencarnet.vw_connection] Token exchange failed
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/volkswagencarnet/vw_connection.py", line 348, in _login
raise Exception("Token exchange failed")
Exception: Token exchange failed
2023-11-21 16:17:28.328 INFO (MainThread) [volkswagencarnet.vw_connection] Something failed
2023-11-21 16:17:32.672 ERROR (MainThread) [custom_components.volkswagencarnet.config_flow] Failed to login due to error: 'identity'
Crap, then they probably have changed the whole login flow. Anyone here with python skills that can help out to identify the necessary changes that needs to be done in this repository? https://github.com/robinostlund/volkswagencarnet
I have some Python experience, but as already mentioned: I have on idea how the login worked in the past and I also don't know how it should be now...
@robinostlund Please check my comment: "this mqtt module uses the weconnect module, that is using the "https://emea.bff.cariad.digital/vehicle/v1/vehicles" API."
If you open the weconnect module, you will find how it logins and uses the https://emea.bff.cariad.digital/vehicle/v1/vehicles API to get the car update. This login works properly.
Crap, then they probably have changed the whole login flow. Anyone here with python skills that can help out to identify the necessary changes that needs to be done in this repository? https://github.com/robinostlund/volkswagencarnet
Tried the python module from master branch, using the example from the readme, got the same error. I sent you an email as well if I can make of any help let me know.
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:volkswagencarnet.vw_connection:Using service https://msg.volkswagen.de
DEBUG:volkswagencarnet.vw_connection:Initiating new login
DEBUG:volkswagencarnet.vw_connection:Got authorization endpoint
DEBUG:volkswagencarnet.vw_connection:Authenticating with email and password.
DEBUG:volkswagencarnet.vw_connection:Parsing login response.
DEBUG:volkswagencarnet.vw_connection:Login successful, received authorization code.
DEBUG:volkswagencarnet.vw_connection:Trying to fetch user identity tokens.
ERROR:volkswagencarnet.vw_connection:Login failed for VW account, Token exchange failed
ERROR:volkswagencarnet.vw_connection:Token exchange failed
Traceback (most recent call last):
File "/home/goodman/.local/lib/python3.10/site-packages/volkswagencarnet/vw_connection.py", line 348, in _login
raise Exception("Token exchange failed")
Exception: Token exchange failed
INFO:volkswagencarnet.vw_connection:Something failed@squonk11 check the readme.md file in this repository: https://github.com/robinostlund/volkswagencarnet Help is wanted due to that i can't keep maintaining this as i don't have any compatible car anymore.
I can give you @robinostlund a guest user on my car, VW e-Golf 2019 , just send me a pm and i will add you. This would be the smallest problem to contribute with.
New "Volkswagen" app uses. That we recenly had to change to from the "We connect"
GET /vehicle/v2/vehicles HTTP/1.1 and GET /vehicle/v1/vehicles/***
Host: emea.bff.cariad.digital
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf
Just use this repository https://github.com/distwave/volkswagen_we_connect_id
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
@distwave This is working great for a 2020 T-Roc and a 2021 Tiguan (both no EV) :) Thanks
P.S. Maybe to many entites were created which are maybe specific for an EV.
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
Awesome! Works like a charm for me!!
@distwave it worked like a charm with my Golf!! I had to rename some of the sensors I'm using in the UI/automation, but that was low effort stuff :)
Thank you so much!!
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
For my Tiguan e-Hybrid (2023) the login works, but I see many entities with status "unknown" or "unsupported". Maybe since this plugin is not well suited for Hybrid cars (because it is named: "..._ID"?
but I see many entities with status "unknown" or "unsupported"
And others are also missing, like the last trip distance for example.
EDIT: there are also other behaviours that I don't like, such as to stop charging you have to call a service (this is OK) and supply the car VIN (this is NOT OK, the integration should do this work for me); the charging state is a string (which might change from charging, readyForCharging and so on...), and not a switch like on THIS integration.
@distwave Will you fix them too?
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
Integration setup, but my E-golf is not loaded :-(. Working fine in App
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
Also, feedback from me, although I've only been familiarizing myself with HA for a few days, I've managed to get my Tiguan now available in HA.
Thanks
Same issue here, also with the new 66 version.
Want to keep this integration.
Already a plan to get it back managed?
Thanks for your support.
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
Also, feedback from me, although I've only been familiarizing myself with HA for a few days, I've managed to get my Tiguan now available in HA.
Thanks
It works with my e-Golf. :-) - Testing now...
Thanks.
This works for my VW Tiguan 2021. Thank you so much.
@robinostlund started looking at https://github.com/robinostlund/volkswagencarnet but couldn't figure out the details that were needed to resolve the login flow - it gets part way through then fails (on line 269 of vw_connection.py - post_action = re.search('"postAction":\\s*"([^"\']*)"', d.string)[1]) - it can't find postAction in the JSON.
I came across this https://github.com/tillsteinbach/WeConnect-python - it sits behind https://github.com/tillsteinbach/WeConnect-mqtt and https://github.com/mitch-dc/volkswagen_we_connect_id - both of which have been mentioned above (@MrNice2028 has forked the latter and removed the lock-in to specific iD models, so it now works with other models).
My question was, do you have any sense of how big a task it would be to change your HA component to run using the WeConnect-python library to do its connection to VW instead of using your volkswagencarnet library? I like your HA component and how it presents the various sensors, but obviously it can't currently connect, so I'm wondering if we could resurrect the HA part and just abandon the volkswagencarnet library?
@robinostlund actually I just realised that the WeConnect-python library may well contain the info needed to patch up the volkwsagencarnet library, as it must be successfully doing a login process - I'll look at that too.
This works for my Tiguan 2020. Thanks
@robinostlund started looking at https://github.com/robinostlund/volkswagencarnet but couldn't figure out the details that were needed to resolve the login flow - it gets part way through then fails (on line 269 of vw_connection.py -
post_action = re.search('"postAction":\\s*"([^"\']*)"', d.string)[1]) - it can't find postAction in the JSON.I came across this https://github.com/tillsteinbach/WeConnect-python - it sits behind https://github.com/tillsteinbach/WeConnect-mqtt and https://github.com/mitch-dc/volkswagen_we_connect_id - both of which have been mentioned above (@MrNice2028 has forked the latter and removed the lock-in to specific iD models, so it now works with other models).
My question was, do you have any sense of how big a task it would be to change your HA component to run using the WeConnect-python library to do its connection to VW instead of using your volkswagencarnet library? I like your HA component and how it presents the various sensors, but obviously it can't currently connect, so I'm wondering if we could resurrect the HA part and just abandon the volkswagencarnet library?
Just to clarify, I did not change any code.
I tested the version that was linked and it works for my e-Golf.
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
Integration setup, but my E-golf is not loaded :-(. Working fine in App
Mee too… probably it’s not only for all models… I have TROC 2020
No problems anymore with e-up! 2023. Thank you. Great work.
Sorry to keep this off-topic but the integration of @distwave doesn't offer discussions:
For me it worked for about an hour, then it was causing too many timeouts and logins and I even cannot access the volkswagen app anymore. Maybe it was because I have two e-Ups and I installed it on two HA installations. I now try to limit the API to call every 240 seconds instead of 120. But first I need to wait until the app is unblocked... thanks VW
But first I need to wait until the app is unblocked... thanks VW
Faced similar symptoms, seems to reset at midnight UTC+1
Hello, I guess VW is currently the "worm" in it. At first WeConnect no longer worked. I then switched to the Volkswagen We Connect ID integration. Not all measured values were there, but certainly 90% of WeConnect. Now that no longer works either and the "brilliant new app" ;-) no longer works either. A white screen is displayed when loading. Absolute chaos at the moment. App data is currently not working in Germany.
Guys, I had to disable the ID version of the integration as it seems to have completely drained the 12V battery of my VW e-Golf. The alarm went off in the morning and I have been here before so I guessed this was what had happened overnight. So be careful with this as something seems to be not quite OK with it. On a side note, I also already noticed from the start that initializing the integration is taking much longer that you would expect. I haven't looked at the code but could it be that it's going out to my vehicle way too many times which will kill the 12V battery in the end!?
Bad news then, I'll remove my repository to prevent more issues, sorry for the inconveniences.
Bad news then, I'll remove my repository to prevent more issues, sorry for the inconveniences.
Noooo It's working like a charm for non electric cars like my 2022 Taigo
Hello, I guess VW is currently the "worm" in it. At first WeConnect no longer worked. I then switched to the Volkswagen We Connect ID integration. Not all measured values were there, but certainly 90% of WeConnect. Now that no longer works either and the "brilliant new app" ;-) no longer works either. A white screen is displayed when loading. Absolute chaos at the moment. App data is currently not working in Germany.
When I had the app that read data from the API on, I also had the Volkswagen app crash every day after a few hours and maybe 8 hours of not working and only a white screen. When I stopped using all apps except Volkswagen, the app works fine 24/7. I suspect that there is a limit set on the number of API calls and when it is exceeded, there is a timeout for a few hours and then everything starts working again.
Today I also noticed that (after one day) the Volkswagen We Connect ID plugin and the App do not show any values any more. Maybe this is due to the fact that it is logging in too often? Also the hybrid battery seems to be a bit more empty than it was yesterday. So I disabled this plugin for the time being and wait for further info.
If anyone wants to try, I modified the we_connect_id integration removing the car model check, now it's working for my e-Golf Just use this repository https://github.com/distwave/volkswagen_we_connect_id
@distwave
As I could see from this thread, your code seems to work at least for non-e-vehicles. Would you please provide the code again with this restriction?
@oneteam2win It may work but it seems the integration hits the ratelimit of the API and makes both the app and the extension unusable. I need to dig a bit more about this, it seems that non-ID models have a tighter ratelimiter. Also one user claims his 12v battery was discharged (maybe a coincidence, but better safe than sorry)
@andreasbartl
How did you get the E-UP to work?
@andreasbartl How did you get the E-UP to work?
I installed it yesterday with HACS via custom repo and found 71 entities (but not everything is useful)
It works directly after installation, but unfortunatly today it does not work anymore sind since a few hours. Seems to be the same problem as described in earlier posts. (ratelimiting of the API and locked account)
@andreasbartl How did you get the E-UP to work?
I installed it yesterday with HACS via custom repo and found 71 entities (but not everything is useful) It works directly after installation, but unfortunatly today it does not work anymore sind since a few hours. Seems to be the same problem as described in earlier posts. (ratelimiting of the API and locked account)
Same here. e-UP worked instantly but now App+Integration are not responding
It stopped working to me aswell.
After disabling the plugin (https://github.com/distwave/volkswagen_we_connect_id), the app started to work correctly again after one night.
It was good while it lasted. Thank you for trying
@distwave i saw a commit to change interval, maybe changing that to a (much) higher value helps? mitch-dc/volkswagen_we_connect_id@5981529
The API/App appears to be limited so if there are too many hits, think Tronity, the app, various HA integrations it will stop and reset at midnight. For the ID version I have changed the polling to 90 secs and that resolved for my ID.3 (although as of this moment it has stopped!).
Just chiming in here to say that I noticed that I had 15 calls (or at least write changes) per 24 hours with my e-UP when this integration worked. So polling every 90 secs is way too much.
I also remember that as long the app was working there was an entity "Verbleibende Aktualisierungen = 15" aka ( Remaining requests = 15 ) per Day.
But in another Topic i read that this counter is reset every time the car is moving. https://github.com/skodaconnect/homeassistant-skodaconnect/issues/26#issuecomment-804325801
Disclaimer: Comment was not referring to this integration, but the volkswagen_we_connect_id.
I adapted the above mentioned volkswagen_we_connect_id to be able to use the e-Golf and set the update to 5 minutes, just to be hopefully on the safe side.
I am getting errors:
/vehicles/xx/domains/measurements/rangeStatus: Unknown attribute totalRange_km with value 184
Unknown attribute fuelLevelStatus with value {'value': {'carCapturedTimestamp': '2023-11-26T07:37:15Z', 'currentSOC_pct': 100, 'primaryEngineType': 'electric', 'carType': 'electric'}} in domain measurements
I think both originate from the underlying python library.
Two things I mainly used, was the location of the car (I don't see it available in the other solution) and the ability to trigger a climatisation. So looking into those to see if that is possible.
Edit: found the option to set climatisation in the service. You can trigger manually in developer tools / services, or use the example given below:
volkswagen_id_set_climatisation:
name: Volkswagen ID Set Climatisation
description: Sets climatisation in Volkswagen ID cars.
fields:
vin:
name: VIN
description: Vehicle identification number for the car.
required: true
example: WVGZZZA1ZMP001337
selector:
text:
start_stop:
name: Start or Stop
description: Starts or stops climatisation.
required: true
selector:
select:
options:
- "start"
- "stop"
target_temp:
name: Target Temperature.
description: Sets target temperature in celsius.
required: false
selector:
number:
min: 10
max: 30
unit_of_measurement: "ºC"
Why are you posting modifications of another integration in here instead of the issue page of that other integration? I don't get it. Please post solutions to THIS integration in here.
Of course, posting something like "this other integration still works" helps. But not how to modify the OTHER integration.
Just chiming in here to say that I noticed that I had 15 calls (or at least write changes) per 24 hours with my e-UP when this integration worked. So polling every 90 secs is way too much.
I think this is mixing two things up. It's 15 calls that go to the car itself, it's a max to avoid running the battery down.
But the original HA integration would call the cloud service, not the car, and generally the cloud service would return whatever the car last sent to it, without polling the car for fresh data, even if that data was a few hours old.
I'm sure there will be a different limit for doing read only cause to the cloud service.
Why are you posting modifications of another integration in here instead of the issue page of that other integration? I don't get it. Please post solutions to THIS integration in here.
Fair. I thought this integration was finished due to VW stopping its old service and multiple people were looking for workarounds or alternatives. But indeed it might fit better in the other integration and open an e-Golf experience there.
I also remember that as long the app was working there was an entity "Verbleibende Aktualisierungen = 15" aka ( Remaining requests = 15 ) per Day.
But in another Topic i read that this counter is reset every time the car is moving. https://github.com/skodaconnect/homeassistant-skodaconnect/issues/26#issuecomment-804325801
I think the reset is done by turning the car on, rather than the car moving, I've done it with it on my drive.
Fair. I thought this integration was finished due to VW stopping its old service and multiple people were looking for workarounds or alternatives. But indeed it might fit better in the other integration and open an e-Golf experience there.
This here is the issue page of the integration of @robinostlund and not a community help center for other integrations.
I think @robinostlund is doing everything he can, and as i have stated before, i am willing to give @robinostlund guest access to my volkswagen e-Golf 2019 for testing, i can run out to the garage and restart the car when he needs etc. And i agree with the people stating that this is a thread for volkswagencarnet integration, lets keep the discussion around that. And discuss other integrations on their respective threads. When someone posts "a possible solution to get the volkswagenconnect id could be ...." can be misunderstood as a suggested solution for this integration. I think they all are trying to do their best, and be as helpful as possible.
Why are you posting modifications of another integration in here instead of the issue page of that other integration? I don't get it. Please post solutions to THIS integration in here. Of course, posting something like "this other integration still works" helps. But not how to modify the OTHER integration.
Because this integration connects to a server that doesn't exist anymore so it will never work again. The only alternative we have is to adapt the other integration to let it work with our cars, as Volkswagen did with the mobile app.
The only alternative we have is to adapt the other integration to let it work with our cars
Or, better, adapt this integration to work with the "other" backend python library so we can get the best of the two worlds. I really miss the quality of this integration (meaning having the correct switches, services and instrumentations) and I'm pretty sure this can ben almost restored by changing the underlying backend library. I wish I could be more skilled on that 😢
The only alternative we have is to adapt the other integration to let it work with our cars
Or, better, adapt this integration to work with the "other" backend python library so we can get the best of the two worlds. I really miss the quality of this integration (meaning having the correct switches, services and instrumentations) and I'm pretty sure this can ben almost restored by changing the underlying backend library. I wish I would be more skilled on that 😢
My guess is that this integration can be fixed by updating the Python library that it already uses, but by replicating the web login flow that the other back-end library uses. I think it's a case of figuring out each page's content, and posting the right things to the right pages. I think the login flow has failed, probably broken into more steps, and we need to know the flow (which the other back-end library will provide), then alter this library's back-end library to match.
That way, the changes to this integration would be much smaller, I think.
Sorry to add my slightly off-topic rant here.
First of all: Thanks to all contributors and maintainers of plugins like this one.
Second: What a poorly designed API by Volkswagen this is. How can you implement a solution with such a puny rate limit? I'm paying a subscription fee for remote access to my data and all I get is this? Furthermore, even worse: How can a backend system like the API endpoint allow the car battery to drain if "too many" frontend requests come in? It's a 2 hour job to implement something like an AWS CloudFront distribution or similar in front of the API and deliver cached results if the client requests come in too frequently. Volkswagen is an enterprise with processes and legal department etc. so let's say it's not a 2 hour task but would take 2 weeks.
Third thing, slightly more on topic: I'll switch to WeConnect-MQTT for now as this seems to be working still and I am able to integrate this into Home Assistant easily. I just think Volkswagens responsibility would be to make it feasible for everyone to access their own data - which they even pay for - the way they prefer.
Sorry again for interrupting this comment thread with this rant.