powerwall2 VS powerwall_monitor

FWIW the API (https://github.com/vloschiavo/powerwall2) reports a state of energy greater than 0 (5% I think) when the app shows you 0%. i.e. there’s a lower buffer. I understand the anxiety seeing them at 0% though.

umm, there is... https://github.com/vloschiavo/powerwall2

You can see individual powerwall stats using the local gateway API: https://github.com/vloschiavo/powerwall2

See here for documentation: https://github.com/vloschiavo/powerwall2 Additionally, Home Assistant has out-of-the-box integration using this API. Note that you must have a backup gateway/powerwall for this to work.

I use powerwall_monitor to capture the data from my Powerwall on a minute by minute basis and send it into an InfluxDB database. Thus, even my numbers are a bit of estimate because I'm only using one sample a minute. To get these numbers, I filtered my data for June through September of last year. To determine if there was an event, I looked at times when I was outputting more than 5kWh to the grid between 2 and 7pm. It's pretty rare when there would be an event and I would be doing under 5kWh. Likewise, it's rare when there wouldn't be an event and I'd be pumping out more than 5kWh.

You can connect directly to the IP address of your powerwall. It will present a certificate for https://powerwall/, but after you accept that, it’s pretty self explanatory on how to use it. It also present a set of REST APIs that you can use a project such as powerwall_monitor to grab information from and forward it to a dashboard.

Fair point and I saw your PRs too. Nice work! I needed to pivot to a different caching proxy to reduce load on my gateway and decode the protobuf payloads to get to string and freq data. I opened an issue last October to see if there was interest since it would have been a significant breaking change for anyone using the current version, but I didn't get a response ( https://github.com/mihailescu2m/powerwall_monitor/issues/23 ). It's not easy being maintainer and I have a great deal of respect for anyone willing to open source and support those efforts. Thanks for contributing! Your code lives on.

There are a lot of people who use InfluxDb (https://www.influxdata.com) and Grafana (https://grafana.com). There are also some pre-built solutions (e.g. https://github.com/mihailescu2m/powerwall_monitor) but all of them require some tech knowledge (either in setting up the system or in installing the app). Hope this helps.

How good are ya with severs / containers ? powerwall monitor

yah thanks I’m still trying to figure that out.. have you set this up before - https://github.com/mihailescu2m/powerwall_monitor? I can’t seem to get my cookieproxy to work? thanks

I've used it, but I've found the integration to be odd. Sometimes it just starts failing for no apparent reason and then it will work again later. I already had powerwall_monitor up and running, which connects everything to InfluxDB and Grafana, and from there it was pretty simple to just publish the readings to an MQTT topic and bring them into HomeAssistant.

3rd party. Simple to set up if you know the basics of docker https://github.com/mihailescu2m/powerwall_monitor

People have built data loggers around both APIs so that you can track some of the data from your system and via it. You have to set up and run the software yourself (self hosted) and it requires some fiddling. This is a good example project that uses the local API: https://github.com/mihailescu2m/powerwall_monitor

Check out the powerwall_monitor project on GitHub. This sets up a complete stack with a Grafana dashboard, influxdb backend, and telegraf to grab the data. Of note, as u/kairojya also mentioned, the local API has been becoming more difficult over the last few months. It not uses a non-standard authentication channel that breaks direct access with telegraf - but the project has a workaround.