Not working here also. Since 2 days I’m not able to connect and I don’t get any readings from the sensors. The following error shows up in my HA log:
2019-10-11 10:45:22 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] API error: {‘errorCode’: ‘gw.error.timeout’, ‘description’: ‘Backend Connection Timeout’}
I haven’t changed anything (still on 0.99.3).
Same problem, I also get the same error when using the Audi app on my phone so it looks like something is borked on their side
no issue here , loaded last version of this custom, but still on 99.3
well, actually i have the same error in log file
but its working though, all my sensors are updated
2019-10-10 23:45:59 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] API error: {‘errorCode’: ‘gw.error.timeout’, ‘description’: ‘Backend Connection Timeout’}
somtimes i also see this 
2019-10-11 07:49:33 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] API error: invalid_request
but it works
those errors where always there , i just ignore them
Just restarted HA and guess what. The integration is working again after being dead for almost 48 hours despite multiple HA restarts.
That’s good news. However, i still feel that the integration should never be blocking Home Assistant.
i now always have this error in log on first start :
2019-10-18 16:48:15 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] API error: {'errorCode': 'batterycharge.auth.forbidden', 'description': 'The service: rbatterycharge_v1 for VIN: WAxxx could not be found.'}
I integrated this nice integration and everything works as expected.
I’m missing the identity ‘windows’, although in MyAudi I see ‘windows are closed’.
in MyAudi I have some other stuff which is available, can I integrate them?:
What are the ‘binary_sensor’ identities? these all have an on or off state. I have the following:
Last time I checked, yes. I have since disabled the component as the hangups were driving my girfriend crazy. And that’s, well, dangerous… 
yeah, me too
what kinda hickups did you have? also like that that the website itself was not responing anymore?
i have issues that mu nabucasa remote link is dead, while surfing on local ip was still possible
my guess is that this component is checking something on audi website, but the request is not timing out or just takes too long … while this request doing something, other services fail …
Not really sure which services stopped, but the UI definitely seemed to freeze. Maybe there is indeed something which should be async blocking the system. Unfortunately I don’t have the time to get to the bottom of it right now.
Thomas
ok, gonna disable this also for a while now
this has been affecting my instance for weeks and i even started gain and never suspected that ti was this component because it always seemed to work!!!
going to diable it for now.
Thanks!!
so what issues did you have then? also that your website was not responding or not loading at all ?
Frontend wouldn’t load and was slow, sluggish, wouldn’t respond.
LOTS of HTTP/Network errors in logs and LOTS of messages saying media players were taking longer than 10 secs to update.
I believe it’s the Fault of the ‘myaudi’ app. I have lost all functionality in the app and can’t access any information/services.
It says I need to visit a service centre to be registered as the cars owner before I regain all the features.
Ok, same issues as me then… It’s indeed probably related to the Audi services… But the component should be able to handle the issues/time outs… We need a developer for this
@arjenvr hi , are you still supporting this custom component? i really like it, but i had to disable it for now
it works, but seems when this component is activated, normal other components are failing
my nabucasa is dead after a while, deconz not working anymore after a while, other random errors , lovelace stuck… aftre disabling this component, everything is stable again
seems other people have the issue too
how can i troubleshoot this?
I have had the same issue once, when the Audi service seems to have not been running at all (I could also not connect through the App or website), as well as issues upon (re)starting HA which were caused by this integration. Since then, I’ve made some changes and have been testing it before checking in. I have not had these problems since then. I’ve added some timeout stuff that was missing in the AudiAPI library.
If you guys would like to test it, I’ve committed the changes to github. Please try testing without periodically running the service “refresh_vehicle_data”. This service does not seem so useful anyway, as car position updates are pushed automatically upon certain events (such as parking the car) and the car does not seem to want to send position updates between such events.
ok, loaded the component again
but in my case, i didnt use that refresh_vehicle_data att all, just noticing issues after a while in the overal HA system, just unstable … not sure why
anyway, loaded it again with new code fom github
i still see this error though, was also before update :
2019-11-05 14:51:52 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] API error: {'errorCode': 'batterycharge.auth.forbidden', 'description': 'The service: rbatterycharge_v1 for VIN: WAxxx could not be found.'}