After updating from 4.8.1 to 4.8.3 pypowerwall fails to start with a access denied issue

[Meowcat285]

After updating to 4.8.3 from 4.8.1 I now get a access denied error from pypowerwall. I am using the TEDAPI method and am using a RPi as a relay to the powerwall. When I downgrade back to 4.8.1 by restoring a backup, pypowerwall is suddenly able to connect just fine. Below is the log output from pypowerwall after upgrading to 4.8.3

07/20/2025 12:43:52 PM [proxy] [INFO] pyPowerwall [0.13.2] Proxy Server [t78] - HTTP Port 8675
07/20/2025 12:43:52 PM [proxy] [INFO] pyPowerwall Proxy Started
07/20/2025 12:43:52 PM [proxy] [INFO] Network error rate limiting: 5 errors/minute per function
07/20/2025 12:43:52 PM [proxy] [INFO] Graceful degradation enabled (PW_GRACEFUL_DEGRADATION=yes) - cached data TTL: 30s
07/20/2025 12:43:52 PM [proxy] [INFO] Connection health monitoring enabled (PW_HEALTH_CHECK=yes)
07/20/2025 12:43:52 PM [pypowerwall.tedapi] [ERROR] Access Denied: Check your Gateway Password
07/20/2025 12:43:52 PM [pypowerwall.tedapi] [ERROR] Failed to connect to Powerwall Gateway
07/20/2025 12:43:53 PM [pypowerwall.tedapi] [ERROR] Access Denied: Check your Gateway Password
07/20/2025 12:43:53 PM [pypowerwall.fleetapi.pypowerwall_fleetapi] [ERROR] Failed to retrieve sitelist - MissingSchema("Invalid URL '/api/1/products': No scheme supplied. Perhaps you meant https:///api/1/products?")
07/20/2025 12:43:53 PM [pypowerwall.fleetapi.pypowerwall_fleetapi] [ERROR] No sites found for 
07/20/2025 12:43:53 PM [pypowerwall] [ERROR] Failed to connect to Powerwall with all modes. Waiting 30s to retry.

[jasonacox]

It looks like it attempted to connect to the TEDAPI address (192.168.91.1) and failed and then proceeded to attempt FleetAPI. Can you provide the pypowerwall details you currently see with verify.sh? I wonder if you are using local mode. Also, to test the new code, can you try this (will not change your current install):

pip install pypowerwall -U
python -m pypowerwall.tedapi

In your pypowerwall.env file make sure it lists the correct password for PW_GW_PWD.

[Meowcat285]

It looks like it attempted to connect to the TEDAPI address (192.168.91.1) and failed and then proceeded to attempt FleetAPI. Can you provide the pypowerwall details you currently see with verify.sh? I wonder if you are using local mode. Also, to test the new code, can you try this (will not change your current install):

pip install pypowerwall -U
python -m pypowerwall.tedapi

In your pypowerwall.env file make sure it lists the correct password for PW_GW_PWD.

Here's the out put from verify.sh pre-upgrade

----------------------------------------------------------------------------
This script will attempt to verify all the services needed to run
Powerwall-Dashboard. Use this output when you open an issue for help:
https://github.com/jasonacox/Powerwall-Dashboard/issues/new


Checking pypowerwall
----------------------------------------------------------------------------
 - Config File pypowerwall.env: GOOD
 - Container (pypowerwall): GOOD
 - Service (port 8675): GOOD
 - Version: 0.13.1 Proxy t75
 - Powerwall State: CONNECTED - Firmware: 25.18.4
 - Site Name: My Home
 - Gateway TEDAPI: Available (192.168.91.1)
 - TEDAPI Vitals: Connected - Mode: hybrid
 - Cloud Mode: NO

Checking telegraf
----------------------------------------------------------------------------
 - Config File telegraf.conf: GOOD
 - Local Config File telegraf.local: GOOD
 - Container (telegraf): GOOD
 - Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

Checking influxdb
----------------------------------------------------------------------------
 - Config File influxdb.conf: GOOD
 - Environment File influxdb.env: GOOD
 - Container (influxdb): GOOD
 - Service (port 8086): GOOD
 - Filesystem (./influxdb): GOOD
 - Version: InfluxDB shell version: 1.8.10

Checking grafana
----------------------------------------------------------------------------
 - Config File grafana.env: GOOD
 - Container (grafana): GOOD
 - Service (port 9000): GOOD
 - Filesystem (./grafana): GOOD
 - Version: Grafana CLI version 9.1.2

Checking weather411
----------------------------------------------------------------------------
 - Container (weather411): GOOD
 - Service (port 8676): GOOD
 - Weather: {"temperature": 92.39}
 - Version: 0.2.3

All tests succeeded.

And here's the output after the upgrade

Verify Powerwall-Dashboard 4.8.3 on Linux - Timezone: America/New_York
----------------------------------------------------------------------------
This script will attempt to verify all the services needed to run
Powerwall-Dashboard. Use this output when you open an issue for help:
https://github.com/jasonacox/Powerwall-Dashboard/issues/new

Tip: If colors are hard to read, try: ./verify.sh --no-color, --lightbg, or --darkbg


Checking pypowerwall
----------------------------------------------------------------------------
 - Config File pypowerwall.env: GOOD
 - Container (pypowerwall): GOOD
 - Service (port 8675): ERROR: Not Listening
 - Version: Unknown
 - Powerwall State: ERROR: Not Connected - Firmware: Unknown
 - Gateway TEDAPI: Available (192.168.91.1)
 - TEDAPI Vitals: Not Connected
 - Cloud Mode: NO

Checking telegraf
----------------------------------------------------------------------------
 - Config File telegraf.conf: GOOD
 - Local Config File telegraf.local: GOOD
 - Container (telegraf): GOOD
 - Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

Checking influxdb
----------------------------------------------------------------------------
 - Config File influxdb.conf: GOOD
 - Environment File influxdb.env: GOOD
 - Container (influxdb): GOOD
 - Service (port 8086): GOOD
 - Filesystem (./influxdb): GOOD
 - Version: InfluxDB shell version: 1.8.10

Checking grafana
----------------------------------------------------------------------------
 - Config File grafana.env: GOOD
 - Container (grafana): GOOD
 - Service (port 9000): GOOD
 - Filesystem (./grafana): GOOD
 - Version: Grafana CLI version 9.1.2

Checking weather411
----------------------------------------------------------------------------
 - Container (weather411): GOOD
 - Service (port 8676): GOOD
 - Weather: {"temperature": 92.97}
 - Version: 0.2.3

One or more tests failed.

No settings were changed in between the versions

When I use python -m pypowerwall.tedapi and try to use the password I was previously using it now fails to connect in the newer version

/app $ python -m pypowerwall.tedapi
pyPowerwall - Powerwall Gateway TEDAPI Reader [v0.13.2]
 - Connecting to https://192.168.91.1... SUCCESS

Enter Powerwall Gateway Password: *****

Connecting to Powerwall Gateway 192.168.91.1
Access Denied: Check your Gateway Password
Failed to connect to Powerwall Gateway

ERROR: Unable to connect to Powerwall Gateway. Check your password and try again

But if I use the full password instead of just using the last 5 characters of the password like before with python -m pypowerwall.tedapi it seems to work

/app $ python -m pypowerwall.tedapi
pyPowerwall - Powerwall Gateway TEDAPI Reader [v0.13.2]
 - Connecting to https://192.168.91.1... SUCCESS

Enter Powerwall Gateway Password: **********

Connecting to Powerwall Gateway 192.168.91.1

 - Configuration:
   - Site Name: My Home
   - Battery Commission Date: 2022-12-03T11:31:19-05:00
   - VIN: ****************************
   - Number of Powerwalls: 3

 - Power Data:
   - Battery Charge: 93.14% (40512Wh of 43497Wh)
   - Battery: 5640W
   - Site: -16W
   - Load: 14001W
   - Solar: 8330W
   - Solar_Rgm: 8394W
   - Generator: 0W
   - Conductor: 0W

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.10/site-packages/pypowerwall/tedapi/__main__.py", line 139, in <module>
    run_tedapi_test()
  File "/usr/local/lib/python3.10/site-packages/pypowerwall/tedapi/__main__.py", line 131, in run_tedapi_test
    with open('status.json', 'w') as f:
PermissionError: [Errno 13] Permission denied: 'status.json'

But when I update pypowerwall.env to use the new password it still fails.

Output from pypowerwall:

07/21/2025 03:52:30 PM [proxy] [INFO] pyPowerwall [0.13.2] Proxy Server [t78] - HTTP Port 8675
07/21/2025 03:52:30 PM [proxy] [INFO] pyPowerwall Proxy Started
07/21/2025 03:52:30 PM [proxy] [INFO] Network error rate limiting: 5 errors/minute per function
07/21/2025 03:52:30 PM [proxy] [INFO] Graceful degradation enabled (PW_GRACEFUL_DEGRADATION=yes) - cached data TTL: 30s
07/21/2025 03:52:30 PM [proxy] [INFO] Connection health monitoring enabled (PW_HEALTH_CHECK=yes)
07/21/2025 03:52:30 PM [pypowerwall.tedapi] [ERROR] Access Denied: Check your Gateway Password
07/21/2025 03:52:30 PM [pypowerwall.tedapi] [ERROR] Failed to connect to Powerwall Gateway
07/21/2025 03:52:30 PM [pypowerwall.tedapi] [ERROR] Access Denied: Check your Gateway Password
07/21/2025 03:52:30 PM [pypowerwall.fleetapi.pypowerwall_fleetapi] [ERROR] Failed to retrieve sitelist - MissingSchema("Invalid URL '/api/1/products': No scheme supplied. Perhaps you meant https:///api/1/products?")
07/21/2025 03:52:30 PM [pypowerwall.fleetapi.pypowerwall_fleetapi] [ERROR] No sites found for
07/21/2025 03:52:30 PM [pypowerwall] [ERROR] Failed to connect to Powerwall with all modes. Waiting 30s to retry.

And verify.sh still fails as well

Verify Powerwall-Dashboard 4.8.3 on Linux - Timezone: America/New_York
----------------------------------------------------------------------------
This script will attempt to verify all the services needed to run
Powerwall-Dashboard. Use this output when you open an issue for help:
https://github.com/jasonacox/Powerwall-Dashboard/issues/new

Tip: If colors are hard to read, try: ./verify.sh --no-color, --lightbg, or --darkbg


Checking pypowerwall
----------------------------------------------------------------------------
 - Config File pypowerwall.env: GOOD
 - Container (pypowerwall): GOOD
 - Service (port 8675): ERROR: Not Listening
 - Version: Unknown
 - Powerwall State: ERROR: Not Connected - Firmware: Unknown
 - Gateway TEDAPI: Available (192.168.91.1)
 - TEDAPI Vitals: Not Connected
 - Cloud Mode: NO

Checking telegraf
----------------------------------------------------------------------------
 - Config File telegraf.conf: GOOD
 - Local Config File telegraf.local: GOOD
 - Container (telegraf): GOOD
 - Version: Telegraf 1.28.2 (git: HEAD@8d9cf395)

Checking influxdb
----------------------------------------------------------------------------
 - Config File influxdb.conf: GOOD
 - Environment File influxdb.env: GOOD
 - Container (influxdb): GOOD
 - Service (port 8086): GOOD
 - Filesystem (./influxdb): GOOD
 - Version: InfluxDB shell version: 1.8.10

Checking grafana
----------------------------------------------------------------------------
 - Config File grafana.env: GOOD
 - Container (grafana): GOOD
 - Service (port 9000): GOOD
 - Filesystem (./grafana): GOOD
 - Version: Grafana CLI version 9.1.2

Checking weather411
----------------------------------------------------------------------------
 - Container (weather411): GOOD
 - Service (port 8676): GOOD
 - Weather: {"temperature": 92.97}
 - Version: 0.2.3

One or more tests failed.

So I'm a bit stumped on what's going on here

[jasonacox]

Firmware: 25.18.4

I should have asked this before. How are you connected to the 192.168.91.1 endpoint? You mentioned using a RPi but are you using routing or directly connected? As of Powerwall Firmware version 25.10.0, network routing to the TEDAPI endpoint (192.168.91.1) is no longer supported by Tesla. You must connect directly to the Powerwall's WiFi access point to use TEDAPI features. If you previously set up a static route for TEDAPI, you will eventually need to remove it (e.g. ./add_route.sh -disable)

On your working system if you go to http://localhost:8675/tedapi/status - do you get a result?

If not, that means that you are no longer getting the TEDAPI enhanced metrics, just the core basic metrics that the hybrid mode will allow. If so, that DOES highlight a problem witht he 4.8.3 release that it won't fall back to "local" mode data if the hybrid "TEDAPI" access point is erroring. Ironically, I have the same setup as you and my hybrid upgrade worked without a problem. There is something about your setup that is tripping on a but that I want to fix.

[Meowcat285]

You mentioned using a RPi but are you using routing or directly connected?

The RPi is connected to the powerwall directly over WiFi and to the rest of my network over ethernet, and I have a routing rule on the server to route traffic to 192.168.91.1 via the RPi.

I moved over to using the Pi for this a few months back, even before the 25.10.0 update as I saw in the issues about people having trouble with it due to them making that change.

On your working system if you go to http://localhost:8675/tedapi/status - do you get a result?

Yep, I get a response with all the details there

[jasonacox]

@Meowcat285 thank you! Do you have another system where you could try to install from scratch to see if it behaves differently? I simply can't reproduce anything similar so I'm wondering what is so different about your installation.

Has anyone else had a problem with the upgrade? Please chime in.

[Meowcat285]

@Meowcat285 thank you! Do you have another system where you could try to install from scratch to see if it behaves differently? I simply can't reproduce anything similar so I'm wondering what is so different about your installation.

Has anyone else had a problem with the upgrade? Please chime in.

I'll give that a try, I'll let you know if it happens there as well

[jasonacox]

I don't think there is anything in the new pypowerwall that would change your experience, but I have updated to v4.8.4 with the new pypowerwall v0.14.0. Focus of that update is more about Cloud and FleetAPI access vs TEDAPI local access.