Tessie to TeslaMate Migration

[giterdone509]

Former Tessie user. I would love a feature to migrate my old Tessie data to TeslaMate. Tessie has a function to export data to a csv for import to TeslaFi.

[cwanja]

Could go Tessie > TeslaFi > TeslaMate since TeslaFi importing is supported.

[giterdone509]

I was incorrect with my statement. You can go TeslaFi to Tessie, but not the other way around.

[DrMichael]

If I could get a sample output, I would have a look...

[giterdone509]

Attached the drives and charges csv. Removed my location data. Let me know if you need anything further.
VIN-drives 2.csv
VIN-charges.csv

[DrMichael]

I don't see any location data in them. So, tables positions and addresses would be empty, also geofences, states and updates.

And, not sure, how to deal with charging_processes and charges.

So, migration probably does not make sense.

[giterdone509]

There is location data. I removed the data in the columns for privacy. Do you have an email or something that I can send the file with location data to?

[DrMichael]

Drop it here (link removed) and tell me, when done please.

[DrMichael]

So, I took a closer look at the drives data. One could fill in the columns of drives and positions partially (the blue fields come from Tessie):

Not sure, what one could get then in the dashboards though. Any thoughts?

(I am unsure about the 'location' in the Tessie data. What is it?)

[cwanja]

Feel like the juice is not worth the squeeze there. More negative downstream impacts by having partial data.

[giterdone509]

Uploaded everything to dropbox. Let me know if this helps fill in some of the gaps. Will trust your discretion if this would provide benefit to TeslaMate. From my POV, I have a bunch of data sitting in Tessie that I would love to migrate in to get a more comprehensive view of my all my data.

[DrMichael]

Well, obviously a lot of information, which teslamate collects, will be missing. E.g. teslamate records the positions during a drive. With this data, we will have only start and end of a drive...
I twiddled with the drives data. I used a fake car... The car should definitely be already in teslamate before importing.
Well, some results:
Drives:

Drive Stats:

Charges:

Charing Stats:

Statistics:

Overview:

Not sure, whether it is worth ist...

[giterdone509]

The Tessie devs must be listening. They have changed the available export options. The files I sent you are no longer available. They now just have an export all function that exports all data. The new data includes files that report on the states. Seemingly this state data is what you're referring to (recording the position during the drive). Apologies for the work you have done with the old exports. Hopefully this data positions you better for a more comprehensive data migration. I have uploaded the new files to your dropbox as a zip. Really appreciate your work on this!

[DrMichael]

Hmmm, that data is not usable. No way to get the necessary informations for charges and drives out os that. (At least no obvious...)

Can't the Tessi guys provide a teslamate export? I attach the ER model, which should help with that.

[edwinstol]

I would not expect support from Tessie on getting the data our of their systems and into TeslaMate. The other way around is supported by them (https://help.tessie.com/article/70-import-from-teslamate) since they would like people to start using Tessie and stop with TeslaMate, not the other way around.

[jlestel]

I understand that Tessie does not offer any export, it is up to us to work. And when I see what they export, I confirm that Teslamate is much more complete in terms of data!!

To import third-party data, I base myself on the format required for TeslaFi import. So I have prepared a CSVFiddle to show how we can transform the CSV files provided by Tessie with an SQL query that will generate a "TeslaFi" type file.

[jlestel]

I made a grinder to compile the Tessie files and create a CSV import file compatible with Teslamate. It is based on the TeslaFi format.

It is available here if you want to try: https://www.myteslamate.com/tessie-to-teslamate/

The data imports correctly, I've seen drives but I have not yet verified the completeness.

You can see the BigQuery query that creates the final file here

[jlestel]

charging_states.csv was not found. You needed to create an archive ass described on website.

[ptiagosequeira]

I get the same error. charging_states.csv exists but fails to read the start date of charging
Thanks

Query error : { "error": { "code": 404, "message": "Not found: Table tessie-438008:LRW3E7EK2MC326451.charging_states was not found in location US", "errors": [ { "message": "Not found: Table tessie-438008:LRW3E7EK2MC326451.charging_states was not found in location US", "domain": "global", "reason": "notFound" } ], "status": "NOT_FOUND" } } Fail to read date start / end

[luschmidt93]

I have exactly the same issue, tried everything with the charging_states.csv... the original one, an empty one, one with just a few entries, but remains the same. Any suggestions?

[jlestel]

Ask on the myteslamate.com chat with your VIN.

[lipov3cz3k]

I created my own google BigQuery and use linked sql query to convert my data and it worked fine.

[giterdone509]

Amazing! I will give it a try. On Oct 8, 2024, at 10:50, jlestel ***@***.***> wrote:  I made a grinder to compile the Tessie files and create a CSV import file compatible with Teslamate. It is based on the TeslaFi format. It is available here if you want to try: https://www.myteslamate.com/tessie-to-teslamate/ The data imports correctly, I've seen drives but I have not yet verified the completeness. You can see the BigQuery query that creates the final file here<https://github.com/MyTeslaMate/tessie-to-teslamate-import/blob/master/bigquery.sql> — Reply to this email directly, view it on GitHub<#4112 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKHZAWZRCKYNWQVPNZJ2KFDZ2PWKDAVCNFSM6AAAAABLZUD6OSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBYGEZTIMY>. You are receiving this because you were mentioned.Message ID: ***@***.***>