Availability Log for Vehicle Information
Every 1-2 monthy some of my charging sessions are not recorded properly or are not recorded at all.
I would assume, that is not a problem with the TRONITY infrastructure but with availability of VW/SKODA Servers (in my case).
TRONITY interacts with lots of car manufacturers. Tracking the availibility and making that visible would allow comparing such crucial infrastructure.
-
You mean an overview about whether a connection to the respective APIs of the car manufacturers are working as expected.
There is this: https://tronity.statuspal.io/
0 -
Lineflyer exactly.
I was not aware of that status page. For future mailfunctions of the (Skoda) App I will have a look on that status page. Thanks for that hint!
I'm curious: have you recognized major outages for the OEM APIs? E.g. some hours per month? Are there differences for the different OEMs?
Most probably just checking the availability of the technical endpoint will not result in the real availability. It seems as if (at least in the VW/SKODA case) the backend returns old data during maintenance
https://www.enyaq-forum.de/forum/thread/4162-stabilit%C3%A4t-und-verf%C3%BCgbarkeit-skoda-backend-auswerten/But having the availability of the technical endpoint could be a start.
0 -
> I'm curious: have you recognized major outages for the OEM APIs? E.g. some hours per month? Are there differences for the different OEMs?
There is no history on that status page and I am no employee of Tronity, thus I have no insights.
I do however consider returning old data instead of a proper error message as a no-go.0
Please sign in to leave a comment.
Comments
3 comments