I’ll round it to 0.5 increments 
Strange, but yes seems like it
Good one. Can you sent a report whenever that happens.
It is connected to the first issue of the todo list (password change)
Yes it should. Can you try it in the remote controls of ioBroker? It should do the same. If that doesn’t work then the functionality is broken.
As far as I saw is that sending commands does wake up the car. 
Well, I have it set up for Iobroker since a year and even though it was problematic from time to time it usually worked. Will double check.
My go-to solution as if late have been HA integration which is flawless. But let’s focus on iobroker now. Will get back to you
Hey @Joka
Yes that’s a good one. Maybe set the driver to unavailable whenever the connection is down and mark it as available when it is up.
Ok thanks!
Yes we can always alter the ioBroker data with some additions from the Homey side. ( I’m already doing that 
)
Yeah, sounds perfect. I will check, and hopefully some more ID driver’s can add their comments
Sadly, al lot seems not to work for my A3 hybrid (2018) yet
Why is the panel in the webversion of Homey sometimes blue or orange?
Especially the first one would be great if that would come to work sometime, then I could optimze loading against my solarpanels and rates
Hey @zakraket
Ah pity
I’ll check that. The remote controls are not working on more Audi models it seems.
Will come back on that
The blues/Orange is coming from the temperature selector. This is Homey functionality
Sorry, I can’t get it to work with Iobroker either. It seems that I have an older version of the adapter and I can’t update now due to dependencies.
Need to investigate that.
I hope more people with ID cars and Iobroker can step forward?!
Strange enough the button and flow to start the airco don’t work (neither in IO broker) but the stop action (button and via flow) does work.
As for ID’s.
EDITED!
The climatisation stop (version 1) works.
The climatisation start doesn’t work. Tested with all the three versions and also tested the ventilation all the three versions. The climatisation start and stop works with iobroker, but as I said before the start and stop climatisation in Iobroker should be set multiple times in order it to work (I have set it three times). I tested also the start multiple times with the homey app, but it doesn’t work.
The start and stop charging works great. But the button doesn’t follow the charging status when the charging is started somewhere else. I would change this so that the charging status is it’s own status and there would be separate buttons for start and stop charging. Toggle button can loose it’s correct status. Same goes for climatisation button. Just my 2 cents.
The set temperature doesn’t work. I also tested the set temperature through Iobroker and the temperature can be changed in Iobroker, but it doesn’t change the temperature in the car. Or at least I didn’t find the setting for that. Though the temperature can be changed through the android we connect ID app, so I would assume that it should be settable. The set temperature changes in the homey VW ID device when the temperature is changed through the android we connect ID app.
The plug connected now shows the correct status. And all other statuses are also working. Great work!
For me it doesn’t change but what is changing regularly (like new time / date stamp every minute or so) in iOBroker for me is following parameter - maybe that’s the way forward ? Would be the best to validate against some api documentation … it seems it’s changing according to real state, so not staying connected all the time :
{
"_id": "vw-connect.0.info.connection",
"type": "state",
"common": {
"role": "indicator.connected",
"name": "Device or service connected",
"type": "boolean",
"read": true,
"write": false,
"def": false
},
Actually I found following parameter :
{
"type": "state",
"common": {
"name": "Refresh All States",
"type": "boolean",
"role": "boolean",
"write": true
},
This seems to “re-read” the basic status, at least based on updated timestamps. Problem with Homey is that timestamp is updated only when value changes, right.
First column is Timestamp, 2nd is when value changed - seems eg. that outdoor temperature is not updated when the car is sleeping.
Will try later some remote control via iOBroker but already out of attempts left (and car is not near to me 
) .
Maybe there is an easy fix for this, if you let Homey app send this command 3 times (climatisation = true) just to make sure it “sticks”?!
I know I had a similar solution when I used iobroker to start climatisation, I had 3 cards for the start in the “Then”-part.
It might be a weakness for iobroker, because Home assistant seems more seamless. One command is enough and it starts immediately.
This is indeed not working. Good one. Will add it to the to-do list.
Nice 
So remote controls are not really working. I’ll check it with my car. Only function I can test is lock and flash . Lock is working for me, flash is not. So when I get that working it will probably work for multiple remote controls.
@Sharkys thanks.
The info.connection is the field I use.
The Refresh all states button is the same in the Homey app 
But might be the same issue as mentioned above with remote controls.
Will add it to the todo-list (hopefully I get a own topic soon )
Correct, so hard to validate that indeed. But I have the same with outdoor temp
I’ll defenitely check that. Only issue is that the home-assistant plugin is ID only
@Exile82 can you try it with flows? So put in the THEN field you put the start charging 3 times each with a delay so they are sent after each other.
The point is that even when I initiate refresh in the ioBroker, the values actually didn’t get updated - they stay the same but datestamp indicated the latest were loaded. The same for connected state - it’s TRUE when connected but the fresh timestamp indicates with “fresh” 'true" “connected” - if you know what I mean. But it’s switching between statues like 1x per 1 min - so if it’s disconnected within 5 mins refresh time, it’s actually always TRUE in Homey.
Ok so the refresh call in ioBroker is not the same as the vw connect app. When I force update from the VW connect app on my phone it updates in Homey.
Check got that. I think this is also related to the force refresh. As the iobroker adapter gets stuck at some point and then it needs to restart. In homey I refresh the whole instance (which might have caused a memory leak). So not sure if Homey and ioBroker are the same now.
Yes, that is a clever approach. Just tested with 3 commands with 30 sec interval. Unfortunately it don’t work. Maybe @peltsi51 might have a go with this?
great work @martijnpoppen
faster than a speeding bullet
