PW3 access not as bad as expected

[GSV3MiaC]

Just had two dead PW2 replaced with a PW3, and was expecting it to be really hard to get at their data, but a network scan found

pyPowerwall Network Scanner [0.15.10]
Scan local network for Tesla Powerwall Gateways

    Your network appears to be: 192.168.1.0/24

    Enter Network CIDR [192.168.1.0/24]:

    Running Scan on 192.168.1.0/24...
      Host: 192.168.1.16 ... OPEN - Found Powerwall 3 [Cloud and TEDAPI Mode only]
      Host: 192.168.1.20 ... OPEN - Found Powerwall 3 [Cloud and TEDAPI Mode only]
      Host: 192.168.1.50 ... OPEN - Found Powerwall 3 [Cloud and TEDAPI Mode only]
      Host: 192.168.1.52 ... OPEN - Found Powerwall 3 [Cloud and TEDAPI Mode only]
      Done: 192.168.1.254 ...

Discovered 4 Powerwall Gateway(s)
192.168.1.16 [Powerwall-3] Firmware Cloud and TEDAPI Mode support only - See https://tinyurl.com/pw3support
192.168.1.20 [Powerwall-3] Firmware Cloud and TEDAPI Mode support only - See https://tinyurl.com/pw3support
192.168.1.50 [Powerwall-3] Firmware Cloud and TEDAPI Mode support only - See https://tinyurl.com/pw3support
192.168.1.52 [Powerwall-3] Firmware Cloud and TEDAPI Mode support only - See https://tinyurl.com/pw3support

Turns out, after setting RSA passwords, I can access the v1r tedapi data on the 1.16 network address, nothing cunning about 'vendor net' or whatever. 1.20 is the old GW2 IP address and gets cross if I try to access it. The other two are just WiFi backups of the firs two. Now I just need to figure out how to get the data from tedapi into Home assistant, via MQTT I guess. My Raspi or HAOS server are not keep to have me installing raw pypowerwall python, incase it messes with the various bits of python they are already relying on.

[jasonacox]

@GSV3MiaC Thanks for the update! You might try https://github.com/jasonacox/pypowerwall-server as it uses this library and also publishes to MQTT if configured.

Are both of your PW3 units on WiFi or is that ethernet direct connected?

[GSV3MiaC]

they are both  on the lan, with wifi as backup. Two of the IP addresses are the old GW2, the other two are the lead PW3 I thnk, no sign of the follower PW3 (daisy chained from the lead one) D 9 Jun 2026 07:10:06 Jason Cox ***@***.***>:

…

@GSV3MiaC[https://github.com/GSV3MiaC] Thanks for the update! You might try https://github.com/jasonacox/pypowerwall-server as it uses this library and also publishes to MQTT if configured. Are both of your PW3 units on WiFi or is that ethernet direct connected? — Reply to this email directly, view it on GitHub[#312?email_source=notifications&email_token=ATTYJ7JH75WK2ZUJU3CGFZT466S33A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGMZDANJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17232053], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ATTYJ7LD4GUKQPBXDF5RMAT466S33AVCNFSM6AAAAACZ7QGSD2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMRTGIYDKMY]. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS[https://github.com/notifications/mobile/ios/ATTYJ7IVNYGVA7Y66HVKBLT466S33A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGMZDANJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ] and Android[https://github.com/notifications/mobile/android/ATTYJ7IJEFAM6FF2JFSZI43466S33A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGMZDANJTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ]. Download it today! You are receiving this because you were mentioned. [Tracking image][https://github.com/notifications/beacon/ATTYJ7JY3FOOEAO73SZSRNT466S33BFCNFSM6AAAAACZ7QGSD2WGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQBA3YLLJTSMVQXG33OU5WWK3TUNFXW4.gif]

[jasonacox]

Excellent! Thanks @GSV3MiaC - and let me know if you get a chance to try pypowerwall-server for MQTT data.

@jasonacox-sam we should make note of this, that some people are able to get TEDAPI (WiFi) mode to work directly connecting to the Powerwall 3's LAN address in the 192.168.1.x subnet.

[jasonacox-sam]

Noted! I've documented this finding in PR #314 — added a tip in the TEDAPI Mode section and a troubleshooting entry noting that some PW3 users can reach TEDAPI via the Wi-Fi adapter's 192.168.1.x address even when 192.168.91.1 is rate-limited or blocked after firmware upgrades.

Thanks @GSV3MiaC for the datapoint — this is useful for anyone hitting 429s on the standard Gateway address.

— Sam ⚡

[GSV3MiaC]

Well, not so excellent, my PW3 were on antique 25.x.x firmware, and my second (follower) PW3 aint talking to my leader PW3, so the whole system is sat idle (unable to complete balancing, inverter comms issue with the follower).

After a firmware upgrade on the lead Pw3, I can no longer 'get' v1r data at its LAN address:

v1r login error: HTTPSConnectionPool(host='192.168.1.16', port=443): Read timed out. (read timeout=5)
v1r: Login failed
Failed to connect to Powerwall Gateway
v1r login failed (429): {"code":429,"error":"Api Limit reached for this endpoint","message":"API Limit Reached"}
v1r: Login failed

However the same query pointed at it's secondary (wifi) address (192.168.1.50) works fine:

100.0
{'site': -913, 'solar': 1430, 'battery': 0, 'load': 517.75}
1430
0
-913
517.75
26.10.4 a42baa54
{'VITALS': {'text': 'Device vitals generated from Tesla Powerwall Gateway TEDAPI', 'timestamp': 1781090835.5788915, 'gateway': '192.168.1.50', 'pyPowerwall': '0.15.10'}, 'STSTSM--1707000-30-L--TG1260340000F4': {'STSTSM-Location': 'Gateway', 'alerts': ['BatteryComms', 'IEEE1547Trip', 'SystemConnectedToGrid', 'FWUpdateSucceeded', 'BatteryCalibration'], 'firmwareVersion': None, 'lastCommunicationTime': None, 'manufacturer': 'TESLA', 'partNumber': '1707000-30-L', 'serialNumber': 'TG1260340000F4', 'teslaEnergyEcuAttributes': {'ecuType': 207}}, 'TESLA--None': {'componentParentDin': 'STSTSM--1707000-30-L--TG1260340000F4', 'lastCommunicationTime': None, 'manufacturer': 'TESLA', 'meterAttributes': {'meterLocation': [1]}, 'serialNumber': None}, 'TESYNC--1493315-03-F--JBL20232Y3F01K':

Mind start to boggle, but until those alerts go away is purely decorative system...

D.

p.s. responding directly to your email got me a mailbox full from microsoft!