This addresses a bug in the current pypowerwall release on how 404 HTTP status codes are handled.
Background
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 is a bug in the older pypowerwall code that will treat this 404 like an authentication failure which will result in 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.
Closes #421
NOTE: IF YOU HAVE FIRMWARE 23.44.0 YOU ARE IMPACTED AND SHOULD UPGRADE AS SOON AS POSSIBLE.
🔥 UPGRADE RECOMMENDED 🔥
cd Powerwall-Dashboard
./upgrade.sh
Customized or manual installations should modify their powerwall.yml and use the latest pypowerwall container:
This addresses a bug in the current pypowerwall release on how 404 HTTP status codes are handled.
Background
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 is a bug in the older pypowerwall code that will treat this 404 like an authentication failure which will result in 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.
Closes #421
NOTE: IF YOU HAVE FIRMWARE 23.44.0 YOU ARE IMPACTED AND SHOULD UPGRADE AS SOON AS POSSIBLE.
🔥 UPGRADE RECOMMENDED 🔥
Customized or manual installations should modify their
powerwall.ymland use the latest pypowerwall container: