When I moved the server, I used a 'trick' to get static IP from an outside server room to the location where the server were. It seem to work fine, but I kept hearing from you saying the site was slow (which run pretty good on my end).
I've decided to change it this weekend to a local IP address and apparently I got comment that it fast again now ! So I'll leave it like this instead.
A bonus, the google map kml work again... So the trick I used probably was at fault for this issue.
I've done lot of tweaking on the backend, and I noticed that my code to resume a trip was when I restart it based itself on the timestamp of the current time instead of the time the entry was received, which would surely create new trip.
So actually lot of the things I've been spending hours and hours the past 2 week are related to my ip address trick (Which I think I know why It didn't work correctly). And lot of the issues in the past 2 week are because of my trying to do changes that might improve it.
So check starting today at 2:15 PM eastern time, check if you still have issue on anything and let me know. As far as I can tell.
I say 2:15pm because I just did a change on the trip capture system. Tesla server seem to send me partial information on car live statistics. I had this issue with my python capture system and now with my native C capture. I've also look further and tesla server send me the number of byte he wish to send me, and even that byte number show missing data. Because of this missing 'D'rive in the live data, I will close the trip (no 'D' mean the car if Off normally). So I've changed it so that if I get nothing and it was less than 60 second that I received a 'D'rive, then take it as a drive anyway, since it take more than 1 minute for a car to switch from Park to sleep. That should take care of that issue.
Moc logging off !
I've decided to change it this weekend to a local IP address and apparently I got comment that it fast again now ! So I'll leave it like this instead.
A bonus, the google map kml work again... So the trick I used probably was at fault for this issue.
I've done lot of tweaking on the backend, and I noticed that my code to resume a trip was when I restart it based itself on the timestamp of the current time instead of the time the entry was received, which would surely create new trip.
So actually lot of the things I've been spending hours and hours the past 2 week are related to my ip address trick (Which I think I know why It didn't work correctly). And lot of the issues in the past 2 week are because of my trying to do changes that might improve it.
So check starting today at 2:15 PM eastern time, check if you still have issue on anything and let me know. As far as I can tell.
I say 2:15pm because I just did a change on the trip capture system. Tesla server seem to send me partial information on car live statistics. I had this issue with my python capture system and now with my native C capture. I've also look further and tesla server send me the number of byte he wish to send me, and even that byte number show missing data. Because of this missing 'D'rive in the live data, I will close the trip (no 'D' mean the car if Off normally). So I've changed it so that if I get nothing and it was less than 60 second that I received a 'D'rive, then take it as a drive anyway, since it take more than 1 minute for a car to switch from Park to sleep. That should take care of that issue.
Moc logging off !
