PowerWall 3 Local API

[JEMcats]

I was using my Tesla app one day and went to look in settings. I noticed:

So I connected my phone to Proxyman on my Mac and saw it making requests to https://192.168.200.195/tedapi/v1r which when looked up on my router is the IP of one of my two PowerWall 3's (I have a Gateway 2 but it is not on the network because the Powerwall seems to have taken them over as explained by the diagram below).

I looked closer at the requests and saw one header that might be useful:

sentry-environment=tesla,sentry-public_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,sentry-release=com.teslamotors.TeslaApp%404.46.0-3376,sentry-trace_id=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The request body was in OCTET-STREAM format and I am not sure how to decode that but I do have a Hex of it.

The response had no special headers but the body was formatted like:

{
  "components": {
    "root": {
      "signals": [
        {
          "boolValue": null,
          "name": "SITE_SM_offGridFaultState",
          "textValue": null,
          "timestamp": "2025-06-21T16:17:31-04:00",
          "value": 0
        }
      ]
    }
  },
  "control": {
    "islanding": {
      "contactorClosed": true,
      "customerIslandMode": "BACKUP",
      "gridOK": true,
      "microGridOK": true
    },
    "meterAggregates": [
      {
        "location": "BATTERY",
        "realPowerW": 1
      },
      {
        "location": "SITE",
        "realPowerW": -4311
      },
      {
        "location": "LOAD",
        "realPowerW": 5057.75
      },
      {
        "location": "SOLAR",
        "realPowerW": 9391
      },
      {
        "location": "SOLAR_RGM",
        "realPowerW": 0
      },
      {
        "location": "GENERATOR",
        "realPowerW": 0
      },
      {
        "location": "CONDUCTOR",
        "realPowerW": 0
      }
    ],
    "systemStatus": {
      "nominalEnergyRemainingWh": 27450,
      "nominalFullPackEnergyWh": 27450
    }
  }
}

It also had some, what looked like binary, characters at the beginning of the response body.

If anyone could try to replicate this with their system and try to decode the request body, or provide me with information on how to decode the request body. It would be appreciated, thank you.

Note

I did see #104, but in my case the gateway is not connected to my network only the PowerWalls and if I try to run sudo route add -host 192.168.91.1 192.168.200.195 and python3 -m pypowerwall.tedapi I get:

- Connecting to https://192.168.91.1... FAILED

Also I am running firmware version 25.18.1 so I cannot use add_route.sh because it is not for Powerwall Firmware 24.10.0 and later as it no longer allows routed access to the TEDAPI interface.

[jasonacox]

HI @JEMcats - the https://192.168.200.195/tedapi/v1r is interesting. The one we use to fetch config is /tedapi/v1 without an "r" suffix. It is looking for a POST method and likely needs a protobuf request. Without the POST data, it just responds with a 6-byte binary:

curl -k -X POST https://192.168.91.1/tedapi/v1r -o v1r.bin

When I have time, I'll see about testing the URI with our regular framework but if you are interested, here is how we are handling the /v1 endpoint:

pypowerwall/pypowerwall/tedapi/__init__.py

Lines 234 to 269 in 808ecfd

	# Build Protobuf to fetch config
	pb = tedapi_pb2.Message()
	pb.message.deliveryChannel = 1
	pb.message.sender.local = 1
	pb.message.recipient.din = self.din # DIN of Powerwall
	pb.message.config.send.num = 1
	pb.message.config.send.file = "config.json"
	pb.tail.value = 1
	url = f'https://{self.gw_ip}/tedapi/v1'
	try:
	r = self.session.post(url, data=pb.SerializeToString(), timeout=self.timeout)
	log.debug(f"Response Code: {r.status_code}")
	if r.status_code in BUSY_CODES:
	# Rate limited - Switch to cooldown mode for 5 minutes
	self.pwcooldown = time.perf_counter() + 300
	log.error('Possible Rate limited by Powerwall at - Activating 5 minute cooldown')
	return None
	if r.status_code != HTTPStatus.OK:
	log.error(f"Error fetching config: {r.status_code}")
	return None
	# Decode response
	tedapi = tedapi_pb2.Message()
	tedapi.ParseFromString(r.content)
	payload = tedapi.message.config.recv.file.text
	try:
	data = json.loads(payload)
	except json.JSONDecodeError as e:
	log.error(f"Error Decoding JSON: {e}")
	data = {}
	log.debug(f"Configuration: {data}")
	self.pwcachetime["config"] = time.time()
	self.pwcache["config"] = data
	except Exception as e:
	log.error(f"Error fetching config: {e}")
	data = None
	return data

I did see #104, but in my case the gateway is not connected to my network only the PowerWalls and if I try to run sudo route add -host 192.168.91.1 192.168.200.195 and python3 -m pypowerwall.tedapi I get:

• Connecting to https://192.168.91.1... FAILED

If you connect your computer directly to the WiFi of the Powerwall access point (the leader SSID e.g. TeslaPW_xxxxxxxx), it should work.

[JEMcats]

When I paired my phone to the powerwalls it prompted me to join the “TeslaPW_XXXXXX” network, it never asked for a password but I would assume that something in the Tesla app gets a password or a token or something to join the network.

[JEMcats]

If I post to, https://192.168.200.195/tedapi/v1r I get back:

b����

If I post to, https://192.168.200.195/tedapi/v1 I get back:

{
    "code": 403,
    "error": "Unable to POST to resource",
    "message": "User does not have adequate access rights"
}

is there any authorization used in the requests to 192.168.91.1 usually?

Note:

Keep in mind 192.168.200.195 is over the LAN, not over the TeslaPW_XXXXXX network like 192.168.91.1

[jasonacox]

is there any authorization used in the requests to 192.168.91.1 usually?

Yes, the password. 😞 See https://github.com/jasonacox/pypowerwall/tree/main/tools/tedapi

Essentially, this is what pypowerwall is currently doing:

# Request DIN
curl -v -k -u "Tesla_Energy_Device:GW_PWD" https://192.168.91.1/tedapi/din

# Request Config Data from Powerwall
curl -v -k -H 'Content-type: application/octet-string' -u "Tesla_Energy_Device:GW_PWD" --data-binary @request.bin https://192.168.91.1/tedapi/v1 > response.bin

# Decode Config Data
python3 decode.py response.bin

[JEMcats]

I did try curl -v -k -u "Tesla_Energy_Device:GW_PWD" https://192.168.200.195/tedapi/din over my local network with the password from the gateway and got back:

* Connection #0 to host 192.168.200.195 left intact
{"code":403,"error":"Unable to GET to resource","message":"User does not have adequate access rights"}%                                                         

[JEMcats]

Where is the password for the powerwalls usually located, is it behind the front panel?

[heynorm]

The password to use for the PW3 (i.e GW_PWD) is the same password that is used for the TeslaPW_XXXXXX network. The information is listed on a sticker behind the front cover.

[JEMcats]

Thanks, I don't think it is possible for me to take the front panel off. Should I contact Tesla support?

[jasonacox]

Well, I don't have a PW3, but from what I can tell the QR code can be on the side or inside:

SPAN actually has a good instruction page on it: https://techportal.span.io/s/technical-documents/app-note-commission-tesla-powerwall-3

[heynorm]

On my PW3's, the QR code on the outside is the Serial Number. The only place I have found to get the password in the sticker in the front (after the cover has been removed). Cover can be removed via some torx heads screws (glass cover, so be careful).

…

________________________________ From: Jason Cox ***@***.***> Sent: Sunday, June 22, 2025 3:51 PM To: jasonacox/pypowerwall ***@***.***> Cc: heynorm ***@***.***>; Comment ***@***.***> Subject: Re: [jasonacox/pypowerwall] PowerWall 3 Local API (Discussion #187) Well, I don't have a PW3, but from what I can tell the QR code can be on the side or inside: image.png (view on web)<https://github.com/user-attachments/assets/69f416ea-685a-42a5-b860-d454c5186d87> image.png (view on web)<https://github.com/user-attachments/assets/a315b2b6-38d5-4558-b983-b8d586702362> image.png (view on web)<https://github.com/user-attachments/assets/17d24bd6-9688-4af7-b4d5-ef1a97e22a87> SPAN actually has a good instruction page on it: https://techportal.span.io/s/technical-documents/app-note-commission-tesla-powerwall-3 — Reply to this email directly, view it on GitHub<#187 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APUXY3F6N6ULUTH6XUMJ5233E4XONAVCNFSM6AAAAAB72QRDJ6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJUGUYTGNA>. You are receiving this because you commented.Message ID: ***@***.***>

[jasonacox]

The two PW3 systems I looked at here in Los Angeles had the WiFi QR code on the outside, left side towards the bottom (similar to the photo I have above). They also have the S/N QR code on the same side but at the top. I wonder if this is done by the installer or by Tesla at the factory? I suspect the "new" way may be to install it inside behind the Torx screws to signal that this is "for installers only".

[JEMcats]

Good news 🎉, I have the password to my leader Powerwall's network, I tested it and got data back. I am in the process of setting up a raspberry pi to host Powerwall Dashboard. Question, does the TEDAPI return data on individual strings and individual batteries?

[jasonacox]

does the TEDAPI return data on individual strings and individual batteries?

I hope so. I feel like we had some good feedback from PW3 owners, some with one PW3, others with several. Let us know what you find out. :) As a test you could run:

# get script
curl -O https://raw.githubusercontent.com/jasonacox/pypowerwall/refs/heads/main/example.py

# create the .env file
cat > .env <<EOF
POWERWALL_HOST=192.168.91.1
POWERWALL_GW_PWD=xxxxxxxxx
POWERWALL_MODE=other
EOF

# runt example
pip install -U pypowerwall
python example.py

[JEMcats]

Thank you so much. It has been great chatting with you. I will test that and follow up in the morning.

[JEMcats]

I ran that command and got tons of data back!

[JEMcats]

When I am setting up Powerwall dashboard I get:

Setting America/New_York timezone...
-----------------------------------------

Attempting to determine your location...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.12/json/__init__.py", line 293, in load
    return loads(fp.read(),
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 2 column 1 (char 1)

Any ideas?

Update.

I ran verify.sh and got:

Checking pypowerwall
----------------------------------------------------------------------------
 - Config File pypowerwall.env: GOOD
 - Container (pypowerwall): ERROR: Missing
 - Version: Unknown
 - Powerwall State: ERROR: Not Connected - Firmware: Unknown

[JEMcats]

Yes

[JEMcats]

I think I will just try setup from scratch in case something got messed up.

[jasonacox]

Good plan. Make sure you also remove all the containers in case they managed to get corrupt:

cd Powerwall-Dashboard
docker-compose -f powerwall.yml down -v

[JEMcats]

Data is loading now!

[jasonacox]

woohoo! Great job!