Sure will defenitely send you those 
1 Like
@matrover When you go to object you should see the VW adapter there and it should list your car. It’s like a folder structure.
One other thing.
It’s more app store related.
I’m doubting between:
creating one app for all car brands OR a app per brands.
The core of each app will be the same and use the same logic. Only different look and feel
Any preference here? 
Keep it simple? If it is more or less the same, do a VAG app?!
1 Like
Are there any other benefits, eg. possible smaller memory footprint ?
OR from your perspective, isn’t it better to maintain only one app instead of several ? 
1 Like
keep it simple - one app for all vag products
let me know if you need help for translations into german language
1 Like
Ok then a VAG app it will be as it’s all the same 
The only reason I was thinking about it was because of different apps in the app store.
1 Like
You already have too many apps in the app store.
Sorry! 
4 Likes
Great to hear you are building this app!
I actually build my own app based on Iobroker to control my Seat Leon hybrid. I have no plans to release it, just a hack for my self to start the heating in the car.
But if you want any help with testing for Seat or help with coding please let me know!
1 Like
@Emil_Ohman sounds good!
I’m also building this based on IObroker.
Any interest in sharing a github link with me?
For the people with ioBroker.
How is the update interval?
For me it seems like the updates are not really coming trough. (might be that i’m blocked ofcourse)
Last update of data was yesterday evening but It seems like even an force Update is not working.
Edit: when I force the update form the VW app it works.
I have seen the same sluggish behavior with iobroker. With Home Assistant integration it is more or less instant. Don’t know how the implementations differ though
1 Like
The HomeAssistant version is nice. Only it’s limited to the ID cars.
ioBroker has it all. However i’m doubting to rewriting it myself as it doesn’t behave that nice…
1 Like
I also had the delays when I played around with IO broker. Locking the door sometimes did work and sometimes it didn’t do anything
1 Like
Yeah so in the VW app. You can pull down to refresh and it will get the last known state.
But if you pull down and hold for 2 sec it will actually get the car out of standby.
in iobroker that force refresh is done every 360 min
1 Like
I have similar experience, ioBroker stop getting updates in about 2 hours (didn’t measure it exactly), it get’s back when the car is “started”. But also original app can refresh the state indeed.
1 Like
The problem there is that you are not allowed to execute limitless actions against the car. What I am seeing in the We connect app is that it will start to complain that there are only 3 actions left to preserve the 12V battery (all cars still seem to have). Also note that if the main battery is full and the 12V is empty you will have to push 
.
I think the force should be used as a last resort as it may make the number of actions counter reduce by these actions as well as you are “waking up” the car for an actual update. Same goes for the altering of departure times, charge current or pre-heating the car.
If actions are depleted the ad-hoc pre-heating will also refuse until the car has been started again.
Long story short, have the force update as an option button and possibly optionally configureable with a very long force refresh time. (I guess a longer configurable regular refresh time should also be fine)
Owner of a Golf GTE and grateful that you are diving into this.
1 Like
Thanks @Bug
Makes sense indeed. The current implementation has a force update of 6 hours. Probably in the first version that won’t be configurable.
Just curious as you have the GTE. Do you also have ioBroker running?
Not sure yet, but I think I have to add a hybrid model to the list. So curious what values you have
