Skoda is not at a point where it is ready for testing. If you’re a programmer, I’ll soon merge this branch into the VAG branch. Feel free to submit PRs to make it better! But for now, I just don’t have the time to build cars I don’t own 
Cupra and Seat should work with that VAG branch thanks to Jaspers hard work 
, but Skoda uses yet another API.
I tried to login with my seat id but get a message login failed. Is it already active for seat? I can also only choose a volkswagen as product.
Is reduced AC charging current setting in VW app similar to reduced current of this app? Flows won’t trigger reduced or maximum settings.
Isn’t it possible for the e-Golf to report battery percentage through the app? I can only get two flow-cards, «timestamp created» and «polling interval»
Great app, but a couple of questions. The tokens/tags remaining climate time and remaining charge time is mixed up.
I also dont get why range and electric range is same. Its possible to change the electric range to set the estimated total range.
Do you also have a description on what all tokens means
have a look in the linked post to see some of the tokens and why they are there. that should also explain why two tokens might be the same as there are hybrid cars that do use them as different values.
Can’t connect to the car anymore, getting an error “Missing Capability Listener button_wake” when trying to wake the vehicle. Anyone else with this issue?
I have the same problem
Volkswagen changed their login page (again). I pushed a fix that works for me to testing. Please let me know if you still encounter issues after installing the test version. I’m aiming to release this tomorrow in the afternoon (because I really want to go to bed). In the meantime, thanks everyone for the diagnostic reports, but please stop sending them on version 1.1.29 or lower because my mailbox is overflowing 
I still seem to get the same error with “missing capability listener” on all the buttons and sliders after the update. I have tried to restart the app, re-enter my login info and just wait a few hours without any change. Anything else I should try?
I sent a diagnostic report.
Today, Volkswagen released another update that makes it even harder to log in. I haven’t found a work-around yet…
(I don’t need diagnostic reports anymore, I’ll post here when a solution was found)
https://drivesomethinggreater.com/newsroom/short-news/2026-4-02-Transition
looks like all this was announced by them ~2 months ago, is’s just that they’re 1 week late
Source: Issue · GitHub
Unfortunate news:
As @Jeroen_van_den_Booga already mentioned, this was announced. I’ll translate the marketing talk about security in the article: We want money for your own data.
Here’s what I figured out: I intercepted all transactions that the app made and found one that isn’t listed in any of these other integrations: A call to https://emea.bff.cariad.digital/auth/v1/android/challenge. This endpoints gives the app a UUID that is (likely) sent to Google to and then signed with their own Google Cloud key to prove that you’re on an legit Android phone. This is why all requests outside of this Google environment fail. I cannot verify that part because the emulator that I use to intercept doesn’t have Google Play Services installed.
Anyway, since they’re planning to monetise their API (to sell you your own data), this’ll probably become a cat and mouse game between VAG and Homey/HA developers. I’m not going to participate in that. If someone finds a fix and publishes it for smart home users like us, VAG will immediately know how we did it and patch it.
It’s been a great time creating this app for you all, 1437 installs! 
I’m going to ask Homey to remove it from the store. If you’re a developer and want to know more in depth details about this issue, feel free to send me a DM.
Not happy? I found this petition to change things. English version below.
This is so sad. I just started reading this thread as I’m considering the ID3 neo, but just a simple battery percentage readout is the minimum requirement. And it seems that even that is not possible anymore.
For my current Peugeot e208 I run a docker with a complicated login I have to redo every couple of months, but then it works again. I’m not buying the car if I have to enter the battery level manually every single time I connect the car to my charger.
Thanks for all the effort you’ve put into creating this app @Bloemendaal! It’s a real shame that Volkswagen Group has decided to take this direction, making it impossible not only for Homey users, but also for Home Assistant users and many other smart home platforms to connect to their vehicles and access their data.
I’ve recently been in contact with Volkswagen Group as well, and unfortunately it does seem that they are asking for a substantial fee to gain access to these APIs.
I’ll definitely be signing the petition!
Came across this on Tweakers (in Dutch). Sad to see this end, but I understand your frustration as a developer. Thank you for all the effort you put into this @Bloemendaal
I updated the app to version 1.1.32. Someone found a solution by skipping the last token exchange! This means the apps reauthenticates every 2 hours using the login flow instead of using a refresh token.
It’ll probably get patched out soon, but for now you can enjoy this fix 
Thanks for your efforts @Bloemendaal 
GM Casper
I found an “interesting” article; maybe it will help you with future inquiries or issues regarding the app:
or in German:
BDW: I worked as a software engineer for the Swiss VAG importer in the early 2000s, and I have to say that they still haven’t learned anything.
.
Chris
Thanks a lot @Bloemendaal, indeed!
Sad to see how much effort it takes to keep what should be a basic function for all EV’s alive.
