Weird thing I noticed: The set of Superchargers in the "Nearby Superchargers" section of the Tesla app seems to be non-deterministic, or at least not solely dependent on the car's location. Maybe this is only observable in places that have a high density of Superchargers. I've observed this in the Tesla iOS app and by exercising some of the API calls, so I don't think it's peculiar to the iOS app.
Example: When my car is at home in Lafayette, CA, I'm accustomed to seeing the stall counts for Concord, San Ramon, Dublin, and Alameda. That's a pretty reasonable set. Yesterday I drove over to Corte Madera to get a quick charge there, and the app started showing results for Concord, San Ramon, Corte Madera, and Daly City. It stayed that way even after I got back home and parked my car in the garage. These results aren't necessarily wrong, just...interesting.
I wonder if the back-end servers are implementing some kind of hysteresis so that the result set maintains some consistency as you drive around.
Anyone else notice this?
Bruce.
Example: When my car is at home in Lafayette, CA, I'm accustomed to seeing the stall counts for Concord, San Ramon, Dublin, and Alameda. That's a pretty reasonable set. Yesterday I drove over to Corte Madera to get a quick charge there, and the app started showing results for Concord, San Ramon, Corte Madera, and Daly City. It stayed that way even after I got back home and parked my car in the garage. These results aren't necessarily wrong, just...interesting.
I wonder if the back-end servers are implementing some kind of hysteresis so that the result set maintains some consistency as you drive around.
Anyone else notice this?
Bruce.