I’m testing the version with the is_parked capability. But even when the car is parked for more than 30 minutes, the value is still false.
I already see what the problem is. If my wife or my son use their own profile in the car I, as main user, cannot see the is_parked status anymore.
Yes, that’s correct. Unfortunately, when other users use the car, it seems that Volkswagen protects their privacy and also blocks certain data. I’m the case of the parking position, this is done via a http status, meaning I cannot distinguish between different situations.
The is_parked capability is now live for everyone! 
2 Likes
Thnx, any idea how to deal with that? I tried to add a new car with my wife’s account, but no ‘new’ car is available.
That’s because I register the device in your Homey by its VIN, meaning you cannot add the same car twice, even through different accounts. With 500+ active users, I cannot change this anymore to an account ID + VIN identifier. Sorry.
Theoretically, you can run your own copy of this app on your device by following these steps:
-
Clone the repository from GitHub.
-
Add the following line to the
drivers/volkswagen/driver.mtsfile. -
Install it on your Homey with
homey app install.
But that also means that you have to manually pull in any future changes that I push to this app.
I’ve added the line and installed bij CLI, after that installing the ‘second’ car was possible.
But the is_parked capability is now only available for the primary car, not for the just added new one.
That’s probably because you didn’t switch to that account yet. Every polling interval (default 10m), it checks if new data became available and if so it adds new capabilities. If the data wasn’t available during a poll, then the capability is missing.
Hi Casper,
I have a question regarding your app and the Homey ABRP app. I use your tokens to sync with abrp, however Some tokens are not recognized by Homey as numeric values according to the ABRP dev. I get an error with following tokens:
- actieradius
- Kilometerstand
- Lengtegraad
- Breedtegraad
Is this a Homey issue or something else?
There’s indeed a possibility that the values aren’t casted to the correct types. I know that Volkswagen sends float values as string to avoid floating point errors. I don’t have time this weekend to take a look, but I started this session to attempt to write a fix. If that doesn’t work, I’ll try to fix it myself before next Friday.
Link to the agent session: [WIP] Fix token values not recognized as numeric in Homey by Copilot · Pull Request #14 · Bloemendaal/app.bloemendaal.volkswagen · GitHub
Thnx for your swift reply. Do I have to install the app from github with cli?
Yes, you can checkout that branch and install it with homey app install, but I haven’t reviewed the code yet
1 Like
I installed the branch but get the same error. I will patiently wait for the fix. Have a nice weekend !
The app only updates the value if the Volkswagen provides a newer updated at timestamp. I think it might be patience or try re-adding your device to reset these values.
Or reset the timestamps on init with the custom app version.
But it can also be broken 
Hi @Bloemendaal I have a another request for a trigger ‘data is updated’. I want to use it to push the data to ABRP.
Do you have to have the vw connect plus contract or does it work without? On my golf gte some function doesn’t work.
can you see the data you expect being updated in the VW app on your phone
if not you might require the Plus to get the data….
Could we get more flows like checking if the car is home or not? and get some AND flows?
You can make a boolean variable you can set with the card distance from home is less than x meters.
1 Like
Hmm i should probably try the app before asking lol.. But i wish homey would show the variables you get in the app and with the devices.. @Doekse
@Bloemendaal the card that should be easy to add is when “kilometerstand” has changed.
Could you consider that?
