Open BadgerLoaf opened 1 year ago
@BadgerLoaf I'd strongly recommend using the built-in HA integration for the Powerwall, which includes all these sensors. It talks to the Gateway on your local network, so will be much more reliable than going through the Tesla API. That integration is rock solid (as long as your Gateway has a good network connection).
Thanks @craigrouse.
That integration also doesn't have these sensors (unless I have missed something... quite possible! lol), but I will see if I can put a feature request in for that one too.
As you say, a direct connection is best where possible
@BadgerLoaf re-reading, I think you want some more granular ones than these? I.e., if the solar goes directly to the house and bypasses the battery, you want to know about that? I think you could probably derive those figures by calculating deltas between each of the sensors. The default integration has a huge number of sensors, plus a load that are disabled by default that you can optionally enable. Do you think these can do what you need?
Hi @craigrouse - You are correct, I would be looking a more granular detail.... showing where the power is actually going.... for example if solar is being produced, how much is going to the house, how much to the battery and how much to the grid.
Looking at the sensors on both integrations (this and the default), there are no sensors that do that.
Maybe I just need to work on my own template sensor calculations again, see if I can make them more reliable/accurate
The templates to correctly calculate this are actually quite complex.
But are documented here: https://github.com/reptilex/tesla-style-solar-power-card#tesla-powerwall-usage
Is your feature request related to a problem? Please describe. I'm trying to calculate savings made by using the battery and solar on my house, and for this I need to use information such as the number of KW's going from: Grid To Battery, Grid to House, Solar to Battery, Solar to House, Solar to Grid, Battery to House and Battery to Grid. Currently I need to create some somewhat clunky sensors that try to figure out that detail.
Describe the solution you'd like I don't know if it would be possible from the API, but I was hoping there might be a way to create reliable sensors for the following:
Describe alternatives you've considered As above, I have tried creating some template sensors for the above, using some calculations using the currently available "Now" sensors. Which work to a certain point, though are not 100% accurate