Monitoring Dashboard for the Tesla Powerwall using Grafana, InfluxDB, Telegraf and pyPowerwall.
The default dashboard.json shown above, pulls in the live power flows from the Powerwall web portal and embeds that animation in the Grafana dashboard.
A non-animated version of the dashboard is also available using dashboard-no-animation.json
The host system will require:
- docker (install help)
- docker-compose (works with docker compose (v2) as well)
- You should not need to run
sudo
to install this tool. See Docker Errors below for help. - TCP ports: 8086 (InfluxDB), 8675 (pyPowerwall), and 9000 (Grafana)
Clone this repo on the host that will run the dashboard:
git clone https://github.com/jasonacox/Powerwall-Dashboard.git
Run the interactive setup script that will ask you for your Powerwall details and Local Time Zone (options).
cd Powerwall-Dashboard
./setup.sh
- If you get docker errors during the setup, see the Docker Errors section below.
- For Windows 11 users, see the Windows 11 Instructions below.
Follow the Grafana Setup instructions provided (or see below) to complete the setup.
If you prefer, you can perform the same steps that setup.sh
performs.
Note: some manual configuration is required if you are running a non-standard docker installation (e.g. rootless). Also, ensure that the conf
, env
and sql
files are readable by the docker services (e.g. chmod 644
).
You will want to set your local timezone by editing pypowerwall.env
, telegraf.conf
, influxdb.sql
and dashboard.json
or you can use this handy tz.sh
update script. A list of timezones is available here.
# Replace with your timezone
bash tz.sh "America/Los_Angeles"
-
Copy
pypowerwall.env.sample
topypowerwall.env
and update the following details for your Powerwall:PW_EMAIL=email@example.com PW_PASSWORD=password PW_HOST=192.168.91.1 PW_TIMEZONE=America/Los_Angeles PW_DEBUG=no
-
Copy
compose.env.sample
tocompose.env
- you do not need to edit these defaults unless you are running a non-standard install such as docker rootless. -
Copy
telegraf.local.sample
totelegraf.local
. If you want to monitor custom measurements for your site (most users don't need this), add the required telegraf.conf TOML entries to this file. Once created, this file is not overwritten by upgrades or future runs of setup.sh. -
Copy
grafana.env.sample
tografana.env
- you do not need to edit these defaults. However, there are optional settings for alert notifications and HTTPS. -
Optional: If you want to pull in local weather data, copy
weather/weather411.conf.sample
toweather/weather411.conf
and edit the file to include your location (Latitude and Longitude) and your OpenWeatherMap API Key. To get a Key, you need to set up a free account at openweathermap.org. Make sure you check your email to verify account. API keys can take a few hours to activate.[OpenWeatherMap] # Register and get APIKEY from OpenWeatherMap.org APIKEY = aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa # Enter your location in latitude and longitude LAT = xxx.xxxx LON = yyy.yyyy
-
Start the docker containers with the utility docker-compose script
./compose-dash.sh up -d
-
Connect to the Influx database to import setup commands:
docker exec -it influxdb influx -import -path=/var/lib/influxdb/influxdb.sql
Note: It can take a while for InfluxDB to start. Also the influxdb.sql file is set to use America/Los_Angeles
as timezone. Use the tz.sh
script or manually update the database commands above to replace America/Los_Angeles
with your own timezone.
-
Open up Grafana in a browser at
http://<server ip>:9000
and login withadmin/admin
-
From
Configuration\Data Sources
addInfluxDB
database with:- Name:
InfluxDB
- URL:
http://influxdb:8086
- Database:
powerwall
- Min time interval:
5s
- Click "Save & test" button
- Name:
-
From
Configuration\Data Sources
addSun and Moon
database with:- Name:
Sun and Moon
- Enter your latitude and longitude. You can use this web page to find your GPS location if you don't know).
- Click "Save & test" button
- Name:
-
From
Dashboard\Browse
selectNew/Import
, and upload one of the dashboard files below (in dashboards folder):dashboard.json
- Dashboard with the live trend graph, monthly power graphs, an animated power flow diagram and a Powerwall+ section that includes String data, temperature, voltage and frequency graphs. This also includes a "grid status" graph below the animation to identify and track grid outages.dashboard-new.json
- Same as above but updated with new Grafana 9 time series graph with "grid outage" data on main energy usage graph.dashboard-no-animation.json
- Same as above but without the animated power flow diagram.dashboard-simple.json
- Similar to above but without the Powerwall+ metrics.dashboard-grid.json
- Same as dashboard.json but with a simple grid status instead of the trend data.
- The database queries and dashboard are set to use
America/Los_Angeles
as the timezone. Remember to edit the database commands influxdb.sql, powerwall.yml, and dashboard.json to replaceAmerica/Los_Angeles
with your own timezone.
- The included
upgrade.sh
script will attempt to upgrade your installation to the latest Powerwall-Dashboard version without removing existing data. A backup is still recommended.
Check the logs of the services using:
docker logs -f pypowerwall
docker logs -f telegraf
docker logs -f influxdb
docker logs -f grafana
- Docker terminating with
error 139
: InfluxDB does not run reliably on older models of Raspberry Pi. - Grafana Error: Invalid interval string, expecting a number followed by one of "Mwdhmsy" - This indicates that the Grafana setup for InfluxDB is missing the time unit, "s", in the "Min time interval" field:
- Min time interval:
5s
- Min time interval:
- String data only shows up for Tesla inverters as part of Powerwall+ systems. Unfortunately, non-Tesla inverter data is not available via the Tesla API. If you find a way to pull this data, please submit an Issue or Pull Request to get it added.
- The default dashboard and InfluxDB setup supports up to 6 Tesla Powerwall+ inverters. Support for more can be added by editing the dashboard.json and influxdb.sql files. Open an Issue and we can help (see #2).
If you are getting permission errors running docker, or an error that it isn't installed:
- Ensure docker is installed for your OS (run
docker version
to test) - If you see permission denied, add your user to the docker group and reboot your system:
# Add your user to docker group sudo usermod -aG docker $USER
- If the above step hasn't worked, and you get an error trying to run
docker info
likepermission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock
:# Grant permissions to the docker daemon socket sudo chmod 666 /var/run/docker.sock
- If you can't access the dashboard after a reboot, that means that docker was not set to start on reboot. On many OS distributions you can set it to start on boot with:
# Set docker to start on boot sudo systemctl enable docker.service sudo systemctl enable containerd.service
- See Docker install here for more information.
- If you have docker installed but get "ERROR: docker-compose is not available or not running" make sure it is in your PATH or if needed, install the docker-compose cli tool:
# install sudo pip3 install docker-compose # test docker-compose --version
The savings estimates are based on a $0.19/kWh utility cost and net metering credit. You likely have a different value for this and can edit the queries in that panel to reflect your actual costs and credits. To help, here are the variables used to calculate the savings:
s
= kWh from solar (based on time frame selected)fp
= kWh from powerwalltp
= kWh to powerwalltg
= kWh to grid
The equations that are used to compute the estimated savings:
powerwall>home
=fp
*$/kWh
[assumes all power to home from PW = savings]solar>home
= (s
-tp
-tg
) *$/kWh
[assumes all solar not going to PW or grid is going to the home = savings]solar>grid
=tg
*$/kWh
[assumes all power going to grid = savings]
- If you are having trouble getting this to work on a Synology NAS, view the resolution discovered in Issue #22 thanks to @jaydkay.
- If you are running docker as a non-privileged (rootless) user, please some setup help here thanks to @BuongiornoTexas.
- Most of the issues running the Dashboard on Synology NAS are related to user or file permission issues. Ensure that the
conf
,env
andsql
files are readable by the docker services (most can be setchmod 644
).
Installing Powerwall-Dashboard on a Windows 11 host requires some additional setup. Install and Setup using administrator PowerShell or Windows Command Prompt:
- Install WSL (wsl --install) with an OS (recommend Ubuntu)
- Install Git for Windows (https://gitforwindows.org/)
- Install Docker Desktop for Windows (https://www.docker.com/)
- From Git Bash prompt, Clone repo (
git clone https://github.com/jasonacox/Powerwall-Dashboard.git
) - Run
cd Powerwall-Dashboard
- Run
./setup.sh
Since pyPowerwall proxy is part of this dashboard stack, you can query it to get raw data (read only) from the Powerwall API. This includes some aggregate functions you might find useful for other projects. I use this for ESP32 driven display for example. Replace localhost with the address of the system running the dashboard:
- pyPowerwall stats: http://localhost:8675/stats
- Powerwall firmware version and uptime: http://localhost:8675/api/status
- Powerwall temperatures: http://localhost:8675/temps
- Powerwall device vitals: http://localhost:8675/vitals
- Powerwall strings: http://localhost:8675/strings
- Powerwall battery level: http://localhost:8675/soe
- Key power data in CSV format (grid, home, solar, battery, batterylevel): http://localhost:8675/csv
Since weather411 is part of this dashboard stack (if you set it up) you can query it to get current weather data from its built-in API.
- Current stats of weather411 service: http://localhost:8676/stats
- Current conditions: http://localhost:8676/
- Current conditions in JSON: http://localhost:8676/json
Data Retention and Backups InfluxDB is configured to use a infinite retention policy (see influxdb.sql). It uses continuous queries to downsample Powerwall data and preserve disk space. However, this does not safeguard the data from accidental deletion or corruption. It is recommend that you set up a backup plan to snapshot the data for disaster recovery. See backups for some suggestions.
- This project is based on the great work by mihailescu2m at https://github.com/mihailescu2m/powerwall_monitor and has been modified to use pypowerwall as a proxy to the Powerwall and includes solar String, Inverter and Powerwall Temperature graphs for Powerwall+ systems.
- Grafana at https://github.com/grafana/grafana
- Telegraf at https://github.com/influxdata/telegraf
- InfluxDB at https://github.com/influxdata/influxdb
- pyPowerwall at https://github.com/jasonacox/pypowerwall
- Special thanks to the entire Powerwall-Dashboard community for the great engagement, contributions and encouragement! See RELEASE notes for the ever growing list of improvements, tools and cast members making this project possible.