I just got my PW3 commissioned and naively thought I would be able to use PVOutput Integration Service to get my data to PVOutput, but after trying to connect to the local API, seems its not supported.
Alls I can get out of it is:
404 page not found
{“code”:403,“error”:“Unable to GET to resource”,“message”:“User does not have adequate access rights”}
I cannot find a login endpoint let alone any data.
Anyone figured this out yet?
For anyone finding this and wanting to know more, PW3 uses tedapi
I was able to get my DIN by first setting up a route via:
route -p add 192.168.91.1 mask 255.255.255.255 192.168.XX.XX
where the second IP is the powerwall on your network, from then on you can access the TEDAPI on the IP 192.168.91.1
You can then run this to get your DIN
curl -k -u Tesla_Energy_Device:GWPWD https://192.168.91.1/tedapi/din
where GWPWD is the password written on the inside of you powerwall near a QR code and SSID
From here all data is available via the URL
https://192.168.91.1/tedapi/V1
the request content and response is binary protocol buffers and alls I could get was 400 Bad Request, I didnt feel like learning protobuf today, so I have stopped here.
Best resource was GitHub - jasonacox/pypowerwall: Python API for Tesla Powerwall and Solar Power Data
I was able to write own service sending data from NetZero API to PVOutput.
Just generation and consumption data for now.
I just had two Tesla 3 batteries fitted to replace my Fronius. I too thought that the PVOutput integration would be a breeze (apparently not), but am I correct that:
A device such as a RPi or NUC is required to query the powerwall gateway every 5 minutes.
The existing system id can be used. New data is added to the existing system data history.
I am using Google Sheets, and have an automatic script running that get’s my data into PVOUTPUT, if there is interest, i might make a guide.
Looking for any assistance in trying to get my new Powerwall 3 systems uploading to PVOutput.org from the Powerwall-Dashboard installation. I created a new system but I have spent the last 4 hours trying to get it recognized by the Dashboard uploader scripts.
Always get a 401 error, invalid System ID
Select Custom Date Range
Sending Solar Data [2026-02-08 to 2026-02-10]
2026-02-08: No Data
2026-02-09: Generated = 56103 - Exported = 942 - Consumed = 108051 - Imported = 61008 - Temp = 42.0 / 65.5Traceback (most recent call last):
File “/home/keith/Powerwall-Dashboard/tools/pvoutput/pvoutput.py”, line 217, in
push_daily(day, generated, exported, consumed, imported, tm, tx)
File “/home/keith/Powerwall-Dashboard/tools/pvoutput/pvoutput.py”, line 112, in push_daily
raise Exception(response.read())
Exception: b’Unauthorized 401: Invalid System ID’
I finally found the right script to edit and change the API key that I changed on the advice of an AI.
Now the py script sends the day of data with the correct response, but the data neve shows up at PVOutput.org after the first tries to upload.
sudo /home/keith/pvoutput-venv/bin/python3 /home/keith/Powerwall-Dashboard/tools/pvoutput/pvoutput.py
[sudo] password for keith:
Select Custom Date Range
Sending Solar Data [2026-02-09 to 2026-02-11]
2026-02-09: Generated = 56103 - Exported = 942 - Consumed = 108051 - Imported = 61008 - Temp = 42.0 / 65.5 - Published
2026-02-10: Generated = 39575 - Exported = 211 - Consumed = 112074 - Imported = 77502 - Temp = 42.9 / 60.9 - Published
Done.
Now I have screwed up my original working system and still haven’t got the new system taking data. Fubared everything up.
Took having to get Rainforest Support to remotely configure my Eagle-200 to clear its locked up state with no ability to configure it in the local portal. Got it reconnected to PVO again finally.
Had to remove and delete the Dashboard-Powerwall software. Found it locked up and not responsive after two days. Turns out the Tesla Cloud API that I configured it to use is rate-limited by Tesla. So not a solution for me unfortunately as I really liked the software’s Dashboard view.