Release 4.6.0 - No temps for Powerwall 3

[jasonacox]

I upgraded to the 4.6.0 release and unfortunately I am not getting any temperature readings from my PW3. Dashboard says "No data" and http://pypowerwall:8675/temps returns "{}". Seems like maybe something is different with PW3. Is there anything I can do to help debug?

Originally posted by @jplewis2 in #392 (reply in thread)

[jasonacox]

Thanks @jplewis2 take a look at http://pypowerwall:8675/tedapi/controller and scroll down. Do you see anything that looks like this? If you can, share the payload you get (remove serial numbers).

{
"activeAlerts": [],
"partNumber": "2012170-25-E",
"serialNumber": "TG1213456778901",
"signals": [
{
"boolValue": null,
"name": "THC_AmbientTemp",
"textValue": null,
"timestamp": "2024-12-01T21:37:45-08:00",
"value": 18.900000000000006
}
]
},

[martinmanyhats]

In case it helps, output from a PW3/GW2 installation, not showing temp data in dashboard.

martinmanyhats.json

[farberm]

I have the same output for temp.

PW 3, Firmware 24.36.1. Gateway info etc...

[proxy] [INFO] pyPowerwall [0.12.0] Proxy Server [t66] - HTTP Port 8675
proxy] [INFO] pyPowerwall Proxy Started
[proxy] [INFO] pyPowerwall Proxy Server - Local Mode
[proxy] [INFO] Connected to Energy Gateway 192.168.91.1 (Home)
[proxy] [INFO] TEDAPI Mode Enabled for Device Vitals (full)

This is a direct connection thru a LAN port. Redirect thru unifi static route.
{
"boolValue": null,
"name": "THC_AmbientTemp",
"textValue": null,
"timestamp": null,
"value": null
}

[jplewis2]

I am getting the same as @martinmanyhats and @farberm for my output:

      {
        "activeAlerts": [],
        "partNumber": "",
        "serialNumber": "",
        "signals": [
          {
            "boolValue": null,
            "name": "THC_AmbientTemp",
            "textValue": null,
            "timestamp": null,
            "value": null
          }
        ]
      },

Full output:
tedapi_controller.json

[jasonacox]

Thank you all.

It seems like this is a consistent report from Powerwall 3 owners. I haven't heard of a working PW3 yet.

There is a possibility that the temperature sensor was removed from the PW3, but that seems unlikely as they would want it on the CAN bus to trigger resistance heat during freezing weather conditions (required to make the batteries work). It could be stored under a different payload which also seems odd if they are both using the Tesla One app for setup and troubleshooting.

Are any of you with Powerwall 3 systems able to see temperature data in the Tesla One app? If so, if you are able to analyze the network traffic during that session, it may point us toward the right query needed to get PW3 temps.

I should update the PR and notes to indicate that the 4.6.0 release only works for PW, PW2 and PW+ systems.

[petersloan]

I can confirm that in Tesla One with Powerwall 3 and Gateway 2, there are no temps anywhere that I can find. If someone can confirm where exactly in Tesla One you find temps, I will check again.

I would have expected them in System -> Powerwall where the vitals are listed. Its possible that they are no longer exposed with PW3.

[jplewis2]

Yeah, I also can't find temp information anywhere (PW3 + GW2). According to @ygelfand who provided the code to get temp information, he actually looked at the source code for Tesla One to find the new protobuf fields that provide the temperature - he's never used the app himself: #392 (reply in thread)

It's possible the app is querying the data anyway, just not displaying it. So maybe a network traffic capture would still work? But that seems like a lot of work for something that seems unlikely.

[ygelfand]

just to clarify, the app doesn't actually use/collect it, it just opens up the avenue for it. I don't have a pw3 to test with unfortunately, only have2+'s. I know powerwall3 is combined pod/pinv? does it have a separate device type?

[jplewis2]

@ygelfand You said you looked at the source code for Tesla One to find the temp data - does that mean you used a tool to disassemble/decompile the app binaries?