can you tell me the model of the car/cars?
Tesla Y MY 23, KIA EV3 MY 25
and are you sure that both cars are woken up?
Hi. I monitored both cars. Tesla shows the time it sleeps in the app. There you can see that as soon as the VRM opens, it wakes up. Kia has it a little more complicated, the time it took to load the data was delayed by 5 minutes, but it also responds to the VRM. Maybe it’s because it shares position data. In the thread I showed that the description was swapped - the KIA was charging, but the description was Tesla. I will monitor it in more detail and test it at night, when there is no traffic at home, and I will try to describe how it behaves according to my monitoring.
Hi! The Tesla range should show now, there was a change in the Tesla API we weren’t aware of 
As for the KIA: I see that there is a lot of data missing, which leads me to guess that something went wrong in us getting data from the KIA. If that didn’t get better in the last days since you reported this. Maybe you can unlink it and link it again?
yes. I plan to remove the cars and re-integrate and monitor. I will eventually write my findings
Thank you, appreciate it. In the meantime, our developer checked, and we only wake up the Tesla on initial linking, after that it only sends VRM data when it is woken up (by opening the Tesla app, by Sentry mode, by driving). So that seems to be a coincidence.
We wanted to double-check it thoroughly, because this integration should obviously not drain your car battery.
Hi. The integration is now working properly. The problems were probably caused by the original bad cross-connection. I removed the cars from the integration, deleted them from Cerbo from the device list, integrated them again and assigned them individual numbers. Now the Tesla doesn’t wake up and apparently neither does the Kia. So now everything is OK
Can’t connect my VW ID.3 (was connected but removed it for testing).
When I now try to add the vehicle again, it fails with “An error has occurred” (Dev Console showing a HTTP 500 internal server error with a post to link.enode.com/someToken).
Hi, my Ford is in exactly the same situation.
Is it known when the option to modify the charging target will be implemented? Thanks.
Hi Rodrigo,
That depends on whether your vehicle brand support us with this. Some of the brands due, others not, and there’s also brands without any target SOC (it just always defaults to 100%).
If your car brand does not support it right now, I doubt that they will in the future. Perhaps they have their own forum or ‘idea box’ to request a target SOC change through their API.
Hi Miroslav,
That is unfortunate. I will have a look as to why this happens.
But regardless of whether the brand allows it or not, can’t it be implemented in the system so that when the car shows 80%, the charger stops? My car doesn’t have that option, and I’m very interested in it.
Hi @only_one !
Thank you for the report, we have deployed a fix last week so I hope you experienced a better matching last weekend.
Eu Data Act ?
They have to provide for free
Hi. Yes, the change is visible, it seems that now the vehicles are identified correctly after a while. I would say good job 