bassmaster187 / TeslaLogger

TeslaLogger is a self hosted data logger for your Tesla Model S/3/X/Y. Actually it supports RaspberryPi 3B, 3B+, 4B, Docker and Synology NAS.
https://www.teslalogger.de
GNU General Public License v3.0
505 stars 167 forks source link

Better differentiation between SuC V2 and V3 on same location #286

Closed Adminius closed 4 years ago

Adminius commented 4 years ago

AS IS: we've assumed, that each SuC location can be either V2 or V3 but not mixed. But it doesn't work anymore, since https://teslalogger.de/charging_pos.php?pos=Supercharger%20DE-Braak got 4 new additional V3 stalls to old V2 stalls.

TO BE: in geofence.scv file we have already have Supercharger and Supercharge-V3 prefix. Geofence script should look for the same location (Braak in thins case) if there are 2 different versions are provided and than: For all charging session with max. power less/equal 150kW =>Superchager V2 For all charging session with max. power greater 150kW =>Superchager V3

Theoretically, this solution might not be the best vor CH and AT, because lots of SuCs in this countries are limited to 125 oder 138kW. But until now there are no mixed SuC-Locations in that countries.

bassmaster187 commented 4 years ago

We could also use this feature to distinguish between Tesla Supercharger and any other fast Charger, because we get "Tesla" as the brand in the API.

Adminius commented 4 years ago

But only for newer data sets... we have "brand=Tesla" since around november 2019...

I think, we have today a good differentiation between SuC and 3rd party charger. It make sense to update "older" DB datasets to have consistent "fast_charger_brand =tesla" or nor data based on geofence. Something like:

if address == ("Supercharger * or Service Center* or Urban charger*) and max power <= 150kW and
fast_charger_brand == NULL and 
fast_charger_present == NULL than update 
fast_charger_brand = Tesla, fast_charger_present = 1