[APP][Pro] myAudi - Connect your Audi EV or PHEV

Apps
,
101

Hi Menno

Thank you for the feedback :slight_smile:

Error E:CV.PA.29 on the myAudi App seems to be a vehicle communication time-out error indicating that your smartphone app cannot reach the car’s cellular/data module. It typically happens when the car enters a deep sleep state or cellular connection drops during a remote command (That’s what I found out googling the error message).

At the moment there is no possibility in my app to change the charge mode. Is that something you use often?

I let control my Wallbox when and how it charges my car.

Andi

102

Hi Andy - re. the error reported, very strange indeed as I got the impression that the myAudi app was able to communicate with the car on other information. At the moment, I frequently use the different charge modes but maybe need to look into switching to controlling the way the car is charged to the charger indeed (although the integration of my Alfen charger in Homey is not without issues).

103

Hi Andy,

I’ve noticed that you also published a “VW Group Vehicles” app. Will you be maintaining these in parallel or will you move the Audi support into the group app? In the meanwhile would either one have an advantage over the other?

104

Hi Jurgen

Good question — they’re built on completely different foundations, so they’re not really competing.

myAudi talks to Audi’s connected-car backend, the same one the official app uses. That gives you remote control (start/stop charging, pre-climatisation, ventilation, window heating, charge target, battery care) and on-demand refreshes. Around 39 action cards, 54 triggers.

VW Group Vehicles is built on the EU Data Act portal instead — a regulatory data-export channel that hands out a dataset roughly every 15 minutes. It’s read-only by design: no remote commands are possible through that channel at all. What it gives you instead is brand coverage — Volkswagen, VW Commercial, Škoda, SEAT, Cupra and Bentley, for which nothing else exists on Homey.

So for an Audi specifically, stick with the myAudi app — it does strictly more. The group app only makes sense for Audi if you’d rather not have the app authenticate against your myAudi account, or if you also own a car from one of the other brands and want everything through one app.

I’ll keep maintaining both.

Andi

105

Trying to configure and add my Q4, but just getting this?

image
image470×467 16.1 KB

Should I start the process with adding the car or configure the app?

thanks!

106

@kaieivind

Audi has closed third-party API access — pairing and Repair are currently blocked

Since ~Sept 3rd, Audi has blocked the login method this app uses (unauthorized_client — client is not allowed to use the device_code grant). This is on Audi’s servers, not a bug in the app — and it’s independently confirmed by several other open-source Audi/VW integrations this week too.

Already paired? You’re fine — your device keeps running on its saved login, no action needed. 1.0.95 makes sure the app never discards that login unnecessarily.

Pairing a new device or need Repair? Not possible right now. I’ve tested every login path Audi still accepts, including a full re-implementation of the original flow — all blocked by a device-attestation check only Audi’s own app can pass. No workaround exists on my end.

Technical details
Password login broke in July (Play Integrity attestation). The app moved to Device Code (RFC 8628) as a fix. Audi has now revoked that grant too. The authorization-code flow still issues a login, but the token exchange is rejected without genuine Play Integrity attestation, which only the real myAudi app can produce.

I’m looking into alternatives, but honestly: the best option so far covers reading data only, or basic charge control — not climate or lock/unlock. If data-only is enough for you, my VW Group Vehicles app (EU Data Act portal) still works and isn’t affected.

Will update this thread as things develop. Sorry for the bad news.

Andi

107

Thanks for the detailed answer. Hope you find a suitable login or Audi changing on their side.

108

i @Andi,

I’m trying to set up the myAudi app with my new Audi Q5 PHEV, but I’m unable to complete the initial authentication.

I’m using myAudi v1.0.95 on Homey Pro 13.4.1, in Spain.

When adding Audi – Hybrid / PHEV / Combustion, the pairing wizard reaches “Sign in to myAudi” but returns:

Device Code sign-in not available for your account

unauthorized_client — client is not allowed to use the device_code grant

The app then suggests using the legacy username/password login. However, I cannot find any way to complete the pairing wizard and create the Audi device, so I never reach the Device Settings where the legacy credentials could be entered.

I also tried:

Apps → myAudi → App Settings → API Helper → Start login

but this immediately returns:

Could not start login: Request failed with status code 403

No authorization code is generated.

The Debug Log remains empty, as no Audi device can be created and therefore I cannot enable device-level debugging.

Diagnostic Report ID:
6e13d5a1-746b-4365-b877-0463f85225ea

Could you please let me know how I should proceed with the legacy username/password authentication when Device Code authentication is rejected?

I’ve attached screenshots showing the complete process and the errors.

Thanks for your help,
Jaime

109

There are currently issues as Audi closed the access to their API :frowning:

110

I’m afraid that the “already paired” cars are also having issues. My car has become “unavailable”.

111

You are right. :frowning:

If data-only is enough for you, my VW Group Vehicles app (EU Data Act portal) works.

112

Thanks, yes i know but would have prefered being able to send commands as well. Thank you for the time you have put into this app.