Releases: jasonacox/Powerwall-Dashboard
Releases · jasonacox/Powerwall-Dashboard
v4.0.2 - Dashboard Updates
What's Changed
- Update default
dashboard.json
to not connect null values over 1hr threshhold (corrctly representing data gaps) by @youzer-name in #430. - Stack powerwall current energy values in Powerwall Capacity panel by @youzer-name in #430.
- Add "Off Grid" indicators to the bottom of the Frequency and Voltages panels by @youzer-name in #430.
Full Changelog: v4.0.1...v4.0.2
v4.0.1 - Powerwall Voltages
What's Changed
- Added CQs and updated
dashboard.json
to include voltages from battery block vitals by @mcbirse in #426. This addresses users no longer seeing Powerwall voltages in the dashboard with firmware 23.44.0 or later - See related #109 (reply in thread)
Full Changelog: v4.0.0...v4.0.1
v4.0.0 - Cloud Mode Support
What's Changed
- Using pyPowerwall for both Local Access and Tesla Cloud mode by @jasonacox and @mcbirse in #414 (replaces Tesla-history service, but the Tesla-history tool will continue to be used to fill in historic data or gaps) - See related jasonacox/pypowerwall#59
- Removal of Docker Compose profiles (helps with some older systems that don't fully support this) and the v1 related legacy support.
- Updated
setup.sh
andupgrade.sh
to support transition to pyPowerwall for Tesla Cloud mode. - Updated
verify.sh
to support Tesla Cloud mode. - Updated dashboard for solar-only users to include Powerflow Animation panel.
Full Changelog: v3.0.8...v4.0.0
v3.0.8 - Critical Bug Fix - HTTP 404 Handling
What's Changed
- Critical Bug Fix - HTTP 404 Handling #421 by @jasonacox in #422
- Fixes bug in pypowerwall proxy containers before
jasonacox/pypowerwall:0.7.6t39
related to API calls and 404 HTTP status codes handling. - Powerwall Firmware version 23.44.0 has eliminated /api/devices/vitals resulting in a 404 response from the Powerwall Gateway (TEG) when this is requested. There was a bug in the pypowerwall code that treated this 404 like an authentication failure causing repeating attempts to log in over and over, eventually hitting the rate limit. This is especially impactful for those using the proxy for things like Powerwall-Dashboard as the rate limit will prohibit other data gathering.
🔥 NOTE: IF YOU HAVE FIRMWARE 23.44.0 YOU ARE IMPACTED AND SHOULD UPGRADE AS SOON AS POSSIBLE. 🔥
Full Changelog: v3.0.7...v3.0.8
v3.0.7 - InfluxDB Environment Variables
- Add support to define InfluxDB configuration options by environment variable by @mcbirse. This allows the default configuration settings to be overridden and addresses #408 raised by @youzer-name
- Change InfluxDB statistics recording to false by default to reduce CPU load by @youzer-name in #410
- Update example backup script to use tar.xz (-J option) by @s-crypt in #404 and #405 see #337
- [Tools] - default to bash in
pwstatus
script for better compatibility by @mcbirse see #249 (comment)
Full Changelog: v3.0.6...v3.0.7
v3.0.6 - Powerflow Animation Update
- Update to latest pypowerwall proxy t29 by @jasonacox in #406
- Default page loaded by proxy (http://localhost:8675/) will render Powerflow Animation. Animation assets (html, css, js, images, fonts, svg) will render from local filesystem instead of pulling from Powerwall TEG portal resulting in faster render time.
Full Changelog: v3.0.5...v3.0.6
v3.0.5 - Bug Fix for MacOS
- README: fix "Powerall" typo in Powerwall 3 section by @kenyon in #399
- v3.0.4 - Fix
upgrade.sh
to address issue where get_profile() function incorrectly reads compose.env causing upgrade failure by @jasonacox in #401 Closes issue #400. - v3.0.5 - Fix
setup.sh
,compose-dash.sh
,verify.sh
andweather.sh
by @mcbrise in 45428ab
Full Changelog: v3.0.4...v3.0.5
v3.0.4 - Bug Fix for MacOS
What's Changed
- README: fix "Powerall" typo in Powerwall 3 section by @kenyon in #399
- V3.0.4 - Fix
upgrade.sh
to address issue where get_profile() function incorrectly reads compose.env causing upgrade failure by @jasonacox in #401 Closes issue #400.
Full Changelog: v3.0.3...v3.0.4
v3.0.3 - Setup Profiles Updates
What's Changed
- Updated
setup.sh
process descriptions to include Tesla Cloud data source in profile options (see below). This is currently the only option for Powerwall 3 owners (see #387) by @mcbirse - Update
setup.sh
to allow config changes in and PR #396 - Added weather data to
dashboard-no-animation.json
dashboard. - [Tools] - Revise
pwstatus
andweather-history
retry handling by @mcbirse.
Powerwall Dashboard (v3.0.3) - SETUP
-----------------------------------------
Select configuration profile:
Current: None
1 - Local Access (Powerwall 1, 2, or + using extended data from Tesla Gateway on LAN) - Default
2 - Tesla Cloud (Solar-only, Powerwall 1, 2, +, or 3 using data from Tesla Cloud)
Select profile:
Full Changelog: v3.0.2...v3.0.3
v3.0.2 - Docker-Compose Fixes
What's Changed
- Add future deprecation WARNING for older docker-compose versions.
- Add support for docker-compose >= 1.28.0 to use compose profiles.
- Change logic in
compose-dash.sh
to default to Docker compose V2.
Full Changelog: v3.0.1...v3.0.2