-
Notifications
You must be signed in to change notification settings - Fork 781
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TeslaFi Import fails if one line is mailformed #4477
Comments
FYI: I have similar issues when migrating from TeslaFi as TeslaFi battery_level column is decimal instead of integer since 22 Nov 2024 - every monthly export file one would like to import is throwing errors. |
The same happened to me. What you can do before the import is to open the CSV file, find the |
I tried this already but failed. Can you tell me which editor worked for you? Excel import destroys several column formats so I was struggling to fix the battery_level numbers (to integer) and import the data to teslamate after transforming it. |
Wanted to add to this. All of my TeslaFi imports work until September of 2024. Anything newer than that fails. I tried to reformat the battery_level column, but either I was not successful or it didn't solve the problem. |
My updated script to generate backups from TeslaFi so they can be imported into TeslaMate will now deal with this condition and fix it automatically.
TL;DR Use https://gist.github.com/TheLinuxGuy/e8c85e59226014087159c5d36c0a1272 to dump your TeslaFi data into proper .csv files that will be ingested by TeslaMate without issues (as of March 3, 2025). |
Is there an existing issue for this?
What happened?
I'm trying to import teslaFi data, import process fails. Tested with latest and edge releases.
Console logs (removed coordinates):
Web error:
CVS line:
Expected Behavior
Should import the rest of the file
Steps To Reproduce
create a cvs file with that line
Relevant log output
Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
1.32 and edge
The text was updated successfully, but these errors were encountered: