Replies: 2 comments 1 reply
-
Hi @damclarkd - I think you have a great point here. My original thought was to pull the Regardless of the above, there it may still make sense to add /api/system_status to InfluxDB. I would be happy to add that to telegraf and influxdb.sql unless you want to do that and submit a PR. ;) |
Beta Was this translation helpful? Give feedback.
-
Hello Jason, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Jason,
As I stated in a separate post, I am looking to consolidate a couple of running Tesla Powerwall Dashboard solutions into one instance. In the post I mentioned I have started a new install of your Powerwall Dashboard and moved my historical data into that instance. However I am not finding some of my data in your current configuration and would appreciate any suggestions on how to proceed.
The data in question all comes from the api/system_status call. Specifically - nominal_full_pack_energy and energy_charged, energy_discharged. energy_charged and energy_discharged are both lifetime values (I believe).
Looking at pypowerwall, it looks like api/system_status would be available.
So would I amend the telegraf.conf to include this call?
Then add my retention policy batts_lt and cq for the test system data in influxdb.sql?
I do realize these changes move me out of sync with your code and I would not be able to use your upgrade.sh.
Does this sound like the way to go or am I missing something?
Any thoughts are appreciated.
Cheers!
Beta Was this translation helpful? Give feedback.
All reactions