Feature request: Add direct Tessie CSV import support

[ThomasGrl]

Feature request: Add direct Tessie CSV import support

Currently, TeslaMate supports importing data from TeslaFi exports, but Tesla Tessie users have no direct way to get their data into TeslaMate. Tessie exports 5 separate CSV files that don't match TeslaMate's expected format.

The gap

Tessie provides data exports as 5 files:

• charging_states.csv
• driving_states.csv
• battery_states.csv
• vehicle_states.csv
• climate_states.csv

TeslaMate's import page expects the single-file TeslaFi format.

A community solution

I've created a Python converter script that bridges this gap: tessie-to-teslamate-converter

It handles all the technical requirements:

• Required id column (without it TeslaMate returns "No complete vehicle data was found")
• AC/DC session classification (peak power > 15 kW = DC)
• Consistent charger_phases values (critical for PostgreSQL mode())
• Cumulative charge_energy_added using Energy Remaining from battery_states
• Monthly file splitting (TeslaFiMMYYYY.csv)

Why consider native support?

Adding direct Tessie import to TeslaMate would:

1. Eliminate the need for intermediate conversion tools
2. Reach Tessie users who currently can't use TeslaMate
3. Simplify the data flow for users who switch from Tessie to TeslaMate

Questions for maintainers

1. Would the team be open to a pull request adding Tessie import support?
2. Are there any architectural concerns about supporting additional import formats?
3. If this is not planned, would you be open to linking community tools in the documentation?

Happy to contribute code or discuss implementation details!

---

Link to converter tool: https://github.com/ThomasGrl/tessie-to-teslamate-converter

[JakobLichterfeld]

Thanks for your idea. Not sure what I'm missing, but the docs clearly describe individual import files: https://docs.teslamate.org/docs/import/teslafi and include a python script for many files.

[ThomasGrl]

@JakobLichterfeld Thanks for the response! I think there might be a slight misunderstanding — perhaps I didn't explain it clearly enough.

The script I built doesn't help with importing multiple files. It converts Tessie's proprietary export format (5 separate CSVs: charging_states.csv, driving_states.csv, etc.) into the TeslaFi CSV format that TeslaMate already accepts for import.

The docs/script you linked are for downloading data from TeslaFi into TeslaMate — which is the opposite direction. Tessie users currently have no reliable way to get their historical data into TeslaMate. The web-based converters keep breaking when Tessie changes its schema, and BigQuery is complex to set up.

This Python script runs locally and just converts the format. No external services involved.

Would the project ever consider a native Tessie import option?

[JakobLichterfeld]

Sorry my bad, I thought you were talking about TeslaFi, I'm not into either of those so got often confused.

[JakobLichterfeld]

Seems to be duplicate of #4432