Aggregating data for historical purposes #79
Replies: 2 comments 3 replies
-
You can download the historic data from Tesla via the Tesla app. I would think just doing this occasionally would be your best option.
From: ViktorJp ***@***.***>
Sent: Tuesday, 16 August 2022 7:29 AM
To: vloschiavo/powerwall2 ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [vloschiavo/powerwall2] Aggregating data for historical purposes (Discussion #79)
Again, thank you very much for all this awesome documentation out on your github page, and for answering my last question about grid outages. I was wondering if I could please get your wisdom on this issue:
* Like with the Tesla app, you are able to see a plethora of historical power information over the past 24hrs, days, weeks, months, etc. I'm guessing that a constant stream of data is heading over to Tesla, and they are aggregating all that info there to display on their apps. I'm not seeing anything in this API documentation that would give me the same kinds of historical power info (other than the total lifetime kwH going to/from Grid I believe).
* My question is, what is the best practice in gathering this data, storing and calculating it without the means of being able to use a database? I was going to take periodic snapshots (like every 10s), add it up and average it out over a total span of time for each piece - grid, home, pw and solar, and saving/reading this from a file. I know it probably won't be as accurate as what we can get from the Tesla site stats. Is there a better way I'm not seeing?
Would love your input! :) Thank you!
—
Reply to this email directly, view it on GitHub<#79>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIBGMVSC264KK5KQ7NVCH4DVZKZAZANCNFSM56TROJ7Q>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
2 replies
-
If you don’t want to go the Telsa app route then sure, you will need to do all that coding and data analysis work yourself. It will be less accurate as you can only sample at a rate which will always be lower than the Powerwall can internally, but that’s your only option.
The gateway API does provide some aggregates but there are no details I know of that detail what time frame they are calculated over.
From: ViktorJp ***@***.***>
Sent: Tuesday, 16 August 2022 11:25 AM
To: vloschiavo/powerwall2 ***@***.***>
Cc: Guy Barwood ***@***.***>; Comment ***@***.***>
Subject: Re: [vloschiavo/powerwall2] Aggregating data for historical purposes (Discussion #79)
OK... but what if you don't want to go the Tesla app route, and all you have is the gateway API to play with... ie. accumulating stats through that. What's the simplest way to go? My object is to build a simple method that doesn't rely on a database that calculates stats over time for display purposes using the gateway API as the only source.
—
Reply to this email directly, view it on GitHub<#79 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIBGMVQ5GIQ2Z6EWPT6DKSTVZLUVPANCNFSM56TROJ7Q>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
ViktorJp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Again, thank you very much for all this awesome documentation out on your github page, and for answering my last question about grid outages. I was wondering if I could please get your wisdom on this issue:
Would love your input! :) Thank you!
Beta Was this translation helpful? Give feedback.
All reactions