Yeah, same here… You have a valid audi connect service?
You mean if the app works for instance? Yes, the app is fully functional and shows fuel level, etc.
1 Like
Anyone else facing issues with double device (car + entities) creation? I have now 2 cars 
Well, at some point of time all entities were renamed following scheme:
binary_sensor.audi_q5_2017doors -> binary_sensor.audi_q5nf_doors
All nf marked entities were used in the past, all new and active are 2017. At least for the moment…
Now, the problem is that even if I delete all these unused entities and remove corresponding device from devices registry it sooner or later reappears in my HA instance. Problems started I think in 0.118 (did not noticed it earlier) and it was strange, as both set of entities were existing, but it was somehow random which one was used by integration to report car status - changing after HA restart. Found this troubleshooting why I do not see data for my car in dashboard, but no errors in log. So, I deleted one, inactive set at some point of time and for a moment it worked fine, but just today I noticed that it is back again. Is there any way to make permanent cleanup? BTW I already tried to remove and add again integration.
A few days ago I restarted my HomeAssistant instance to update to the latest version…Ever since my Audi Connect integration has been at fault. I’ve tried removing/adding it a few times now with different regions selected but I always end up with the same error in the logs (see below) - Am I doing something wrong or did VW break the integration again?
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 236, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/config/custom_components/audiconnect/__init__.py", line 106, in async_setup_entry
return await data.update(utcnow())
File "/config/custom_components/audiconnect/audi_account.py", line 162, in update
if not await self.connection.update(None):
File "/config/custom_components/audiconnect/audi_connect_account.py", line 105, in update
vehicles_response = await self._audi_service.get_vehicle_information()
File "/config/custom_components/audiconnect/audi_services.py", line 183, in get_vehicle_information
data = await self._api.get(
File "/config/custom_components/audiconnect/audi_api.py", line 72, in get
r = await self.request(
File "/config/custom_components/audiconnect/audi_api.py", line 55, in request
raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url=URL('https://msg.audi.de/myaudi/vehicle-management/v2/vehicles')
I have one that’s labeled sedan and one that’s labeled limousine. The limo one appears randomly on a reboot but another reboot or two and it’s back to normal.
It happened again today… perfectly working configuration for 2017 is now unavailable and sensors for NF reappeared 
Interesting; since all configured sensors gone, I was checking in application if service is available. What I noticed is that now my car in app is also called with prefix NF… Perhaps integration takes this changing name from Audi service?
OK, I think I sorted this out (?). I went to MyAudi app on on my iPhone and changed the name of my car in app settings (previously I used one automatically assigned). After that I restarted HA and… I got 3rd entity and 3rd set of sensors in HA integration! So I think this is the point where some of us start (giving custom names to our cars in app) while others, like me having problems, leave it at default name that looks OK.
So, I deleted all orphaned entities and deleted again invalid devices from devices registry… So far so good. I’ll report if it did not helped to control devices/entities changes.
Interesting, i have an issue that only 2 sensors are created, the rest is just gone, seems according to github, there are many others facing this issue…
Dod you also notice 2 sensors at first?
In my case after restart whole set of sensors with new names was recreated instantly. So seems something different…
I am still stuck on only 2 identities… But I think it’s cause of my warranty expired, I don’t see anything in app anymore… But I never had an audi connect subscription, and it worked before warranty
Could be! As you mentioned this, I recall I had some service break, when my car turned 3 years old and base subscription coming with new car expired. From now on it needs to be renewed annually (free of charge, yet need to be activated with ‘Audi Digital Services Center’) and since then works again OK. I think despite services expired, some of them were still working, but in very limited mode.
Yeah, my car is also 3 years old now, but I never had audi connect services, like free gps maps, sending google maps… Just the free edition, that was limited…
Do you think they can reactivate the free service?
No cost to try… just call them and ask for status. This is what I did and was surprised to learn that serices are renewed for free. After 3 years of initial free services only for maps updates are chargeable… and it is ridiculously high (~450EUR).
OK, after few days, HA update to 2020.12 and several system restarts I can confirm that changing the name of the car in mobile application fixed issue with car (device and associated entities) being randomly renamed in HA integration. Everything seems to be perfectly stable for few days, no signs of old setup reappearing.
i had a call with audi, they were not able to extend audi connect for me
i had the free edition, just for fuel state and stuff like that, but seems that one was expired
Sorry to hear that… indeed my one was pretty fully loaded, including all tech staff, so I was lucky to be able to integrate and later extend…
i confirm, i bought a subscrition for 1 month , the audi remote and connect for 4,99
now, i have indeed more entities; so its a license issue that only 2 entitys were created
Works great in US with a new 2021 Q5e.
anyone else getting a failure to setup now?
Yep, same issue too