PW3 on 25.18.1 now blocking WIFI access

[jasonacox]

Pposted by @wyx087 in #109 (comment):

Is there any possibility that the PW3 is now also blocking WIFI access?

Single PW3 at 25.18.1
UK based
I got WIFI access working about 3 weeks ago. #109 (comment)
I've then set up local connection in the Tesla app (by setting the Ethernet wired PW3 WIFI to connect to same WIFI as my phone)
Everything was working well...... until...

Both powerwall-dashboard and powerwall3mqtt Home Assistant addon stopped working around similar time 2 days ago (24th).

Checking through the connection, from Linux container to WIFI travel router. I've found I can no longer ping 192.168.91.1. Not even from the DD-WRT travel router that connects to PW3 via WIFI.

According to Home Assistant fleetAPI integration, I'm already on 25.18.1 before 23rd. So I'm at a complete loss what has changed causing PW3 to not respond to pings via WIFI.

Anything else I can try?

Originally posted by @wyx087 in #109 (comment)

[jasonacox]

Are you able to connect to the PW3 WiFi access point (e.g. TeslaPW-xxx) using your laptop?

[Nexarian]

I was just updated to 25.18.2 a few hours ago and wifi still works (but I'm on regular Tesla Solar Inverters)

[wyx087]

Thanks for opening an issue with this. From lack of responses in the discussion thread, I guess I'm the only one seeing this.

Connect PW3 wifi access point get same, ping times out.

I can't seem to remove WIFI connection in the Tesla app, other than renaming my home WIFI SSID (which I don't want to do).
Is there anything else I can try?

[Nexarian]

Can you connect with Tesla One? One possibility is that your wifi card itself is now dead.

Also, try a full reset/power cycle of your PW3?

[heynorm]

fyi - I have two full PW3's which were updated to 25.18.1 about a week ago. I run the dashboard on a RPi using the Panda Wireless PAU0D AC1200 Wireless AC USB Adapter to connect to the PW3. I have not seen any issues with this firmware update.

…

________________________________ From: wyx087 ***@***.***> Sent: Friday, June 27, 2025 6:40 AM To: jasonacox/Powerwall-Dashboard ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [jasonacox/Powerwall-Dashboard] PW3 on 25.18.1 now blocking WIFI access (Issue #648) [https://avatars.githubusercontent.com/u/17969066?s=20&v=4]wyx087 left a comment (jasonacox/Powerwall-Dashboard#648)<#648 (comment)> Thanks for opening an issue with this. From lack of responses in the discussion thread, I guess I'm the only one seeing this. Connect PW3 wifi access point get same, ping times out. image.png (view on web)<https://github.com/user-attachments/assets/7dc29ca1-8559-4c50-a7e8-b4baee8b62d3> I can't seem to remove WIFI connection in the Tesla app, other than renaming my home WIFI SSID (which I don't want to do). Is there anything else I can try? — Reply to this email directly, view it on GitHub<#648 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APUXY3DXYDIIYFUROIMPXWT3FVCTXAVCNFSM6AAAAACAH2EXUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMJTGEZDQMJWG4>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[wyx087]

Restarted the device by doing the following:

1. Turn off both switch on the PW3 itself
2. Turn off battery isolator in the gateway
3. Waited a minute
4. Turn battery isolator back on
5. Turn battery back on
   Still can’t ping from travel router, after confirming it is connected to PW wifi.

Tesla One also can’t connect. It connects via WiFi successfully (got IP) but the app gets stuck on “Retrieving device info...” and after a long wait comes back “Failed to connect to device”.

I think now is probably worthy of a support ticket.

edit:- contacted my installer.

[jasonacox]

Are you seeing any data on the Tesla App itself (cloud not local)?

If so, you can at least switch P-D to cloud mode (run setup.sh switch to cloud).

[wyx087]

Yes. I can see data in the Tesla app (the regular customer app). So (unfortunately) from regular customer perspective nothing is wrong.

I disconnected the Ethernet cable. It still says connected to my wifi. But as usual it’s hard to tell where data is actually flowing with its built in SIM.
(Curiously when Ethernet cable is disconnected. The “local connection” wording doesn’t show up in Settings page)

I would much prefer get the local method working. Both for more data in dashboard and for faster data refresh in Home Assistant via Powerwall 3 MQTT addon.

Is there more step by step guide for how to use the cloud method? I gave up on it when it says I need to run a python script that I can’t find.

[jasonacox]

Hi @wyx087 - I wouldn't give up ont he local access, but I'm running out of things to suggest for you. However, at least you could get metrics flowing while you are troubleshooting that. Here is the step by step for the cloud:

Cloud Mode Setup

Run Setup from the Powerwal-Dashboard directory:

./setup.sh

The setup script wills tart and you will pick Tesla Cloud:

Powerwall Dashboard (v4.8.1) - SETUP
-----------------------------------------
Select configuration mode:

Current: Local Access

 1 - Local Access     (Powerwall 1, 2, or + using the Tesla Gateway on LAN) - Default
 2 - Tesla Cloud      (Solar-only systems or Powerwalls without LAN access)
 3 - FleetAPI Cloud   (Powerwall systems using Official Telsa API)
 4 - Extended Metrics (Powerwall 2, +, or 3 using TEDAPI and local WiFi access)

Select mode: [1] 2

If you have already set it up for local, you will be asked to change that config. For the email address, you will use the one you set up on the Tesla consumer app (or website account). Since you have a Powerwall system, do not select the Solar-only dashboard.

You are already using the Local Access configuration, are you sure you wish to change? [y/N] y

Timezone (leave blank for America/Los_Angeles)
Enter Timezone: America/Los_Angeles

Enter email address for Tesla Account...
Email: your@emailaddres.com
If you have a Solar-only system, you can customize the dashboard for Solar and
hide the Powerwall metrics.

Set dashboard to Solar-only system? [y/N] n

Using America/Los_Angeles timezone...
-----------------------------------------

Found existing location coordinates for sun cycle.
   Your current location appears to be Latitude: 34.3000, Longitude: -118.000

Enter Latitude (default: 34.3000): 
Enter Longitude (default -118.000): 

Weather setup is optional.

Weather Data Setup
-----------------------------------------
Weather data from OpenWeatherMap can be added to your Powerwall Dashboard
graphs.  This requires that you set up a free account with OpenWeatherMap
and enter the API Key during this setup process.

Do you wish to setup Weather Data? [y/N] 
No problem. If you change your mind, run weather.sh to setup later.

Running Docker Compose...
[+] Running 5/5
 ✔ Container influxdb     Running                                                                                                                                                                    0.0s 
 ✔ Container pypowerwall  Started                                                                                                                                                                    3.2s 
 ✔ Container weather411   Running                                                                                                                                                                    0.0s 
 ✔ Container grafana      Running                                                                                                                                                                    0.0s 
 ✔ Container telegraf     Started                                                                                                                                                                    2.3s 
-----------------------------------------

After the containers are running, setup will kick off the Cloud mode setup phase. It will provide you with a long and weird looking URL. Copy this and open it up in a browser.:

pyPowerwall [0.13.1] - Cloud Mode Setup

Tesla Account Setup
------------------------------------------------------------

  Email address: your@emailaddres.com

Open the below address in your browser to login.

https://auth.tesla.com/oauth2/v3/authorize?response_type=code&client_id=ownerapi&redirect_uri=https%3A%2F%2Fauth.tesla.com%2Fvoid%2Fcallback&scope=openid+email+offline_access&state=&code_challenge=&code_challenge_method=S6&login_hint=your@emailaddres.com

This URL will take you to the Tesla login page. Use your customer account to log in to Tesla. When you do, you will get a very concerning response, a 404 Page Not Found error.

This is exactly what you want (yes, I know, it seems wrong). Copy the URL that is in the address bar of your browser and paste it into your terminal at the prompt:

After login, paste the URL of the 'Page Not Found' webpage below.

Enter URL after login: https://auth.tesla.com/void/callback?code=xxxxxxxxxxxxxxxxxxxxxxxx&state=xxxxxxxxxxxxxxxxxxxxxxxx&issuer=https%3A%2F%2Fauth.tesla.com%2Foauth2%2Fv3
------------------------------------------------------------

The Setup script will use that to access your Tesla account and find your sites. Pick your site (usually only 1 option):

1 Sites Found (* = default)
------------------------------------------------------------
 *1 - Tesla Energy Gateway (xxxxxxxxxxxx) - Type: battery

  Select a site [1]: 

Selected site 1 - Tesla Energy Gateway (xxxxxxxxxxxx)
Setup Complete. Auth file .auth/.pypowerwall.auth ready to use.
Restarting...
pypowerwall
-----------------------------------------
Waiting for InfluxDB to start...
 up!
Setup InfluxDB Data... ('already exist' errors harmless)
2025/06/28 14:17:12 error: retention policy already exists
2025/06/28 14:17:12 error: retention policy already exists
2025/06/28 14:17:12 error: retention policy already exists
2025/06/28 14:17:13 error: continuous query already exists
2025/06/28 14:17:13 error: continuous query already exists
2025/06/28 14:17:13 error: continuous query already exists
Fetching local weather...
weather411
------------------[ Final Setup Instructions ]-----------------

Open Grafana at http://localhost:9000/ ... use admin/admin for login.

To complete *Grafana Setup*:

* From 'Dashboard\Browse', select 'New/Import', browse to /home/pi/Powerwall-Dashboard/dashboards
  and upload 'dashboard.json' or 'dashboard-solar-only.json'.

NOTE: The datasources for InfluxDB and SunAndMoon are already configured.
If you need to modify them via Configuration\Data Sources:

* InfluxDB
  - URL: 'http://influxdb:8086'
  - Database: 'powerwall'
  - Min time interval: '5s'
  - Click "Save & test" button

* Sun and Moon
  - Enter your latitude and longitude (tool here: https://bit.ly/3wYNaI1 )
  - Click "Save & test" button

That's it! Now you can check your docker logs to see how things are working. You will see that pypowerwall is using cloud mode:

docker logs pypowerwall

06/28/2025 07:17:12 AM [proxy] [INFO] pyPowerwall [0.13.1] Proxy Server [t76] - HTTP Port 8675
06/28/2025 07:17:12 AM [proxy] [INFO] pyPowerwall Proxy Started
06/28/2025 07:17:13 AM [proxy] [INFO] pyPowerwall Proxy Server - Cloud Mode
06/28/2025 07:17:13 AM [proxy] [INFO] Connected to Site ID XXXXXXXXXX (Tesla Energy Gateway)
06/28/2025 07:17:33 AM [pypowerwall.cloud.pypowerwall_cloud] [WARNING] This API [get_api_sitemaster] is using mock data in cloud mode. This message will be printed only once at the warning level.
06/28/2025 07:17:33 AM [pypowerwall.cloud.pypowerwall_cloud] [WARNING] This API [get_api_powerwalls] is using mock data in cloud mode. This message will be printed only once at the warning level.
06/28/2025 07:17:33 AM [pypowerwall.cloud.pypowerwall_cloud] [WARNING] This API [get_api_auth_toggle_supported] is using mock data in cloud mode. This message will be printed only once at the warning level.
06/28/2025 07:24:26 AM [pypowerwall.cloud.pypowerwall_cloud] [WARNING] This API [get_api_system_status_grid_faults] is using mock data in cloud mode. This message will be printed only once at the warning level.
06/28/2025 07:24:26 AM [pypowerwall.cloud.pypowerwall_cloud] [WARNING] This API [get_api_unimplemented_timeout] is using mock data in cloud mode. This message will be printed only once at the warning level.

[Nexarian]

Yes. I can see data in the Tesla app (the regular customer app)

Nuance here matters. Can you see data in Tesla One app (Which is completely distinct from the regular Tesla customer app, the naming is very confusing).

Tesla One connects to the wifi of the PW3 after you scan the QR code. You sign in as an "external partner" and use your normal Tesla login. Ignore any admonitions by your installer or Tesla that you're not supposed to use it.

If THAT is not working, you have a warranty case as the wifi is dead. If that works but PyPowerwall's TEDAPI does not, then we have a very interesting debugging mystery.

[wyx087]

Thanks very much for cloud instructions, I’ll give it a try later tonight.

@Nexarian Yes, I understand Tesla One app is different to the customer facing Tesla app. As previously reported, the One app isn’t able to connect and I have contacted my installer. #648 (comment)

However, I believe wifi on this PW3 still works because when I disconnected the Ethernet cable, I see PW3 stays connected to my router. But it’s difficult to tell where the data is coming from through the customer app.

edit: another idea hit me. I disconnected Ethernet cable. Router then says PW3 wifi is connected. Curiously I am able to get ping response to the LAN IP to which PW3 WIFI is connected. So it seems this PW3's WIFI isn't completely broken.

[wyx087]

Hum, the Tesla One app now works. I sent the Email late Friday afternoon so I don't believe installer had a chance to look into this yet. Really really strange.

This is what I did:

1. As mentioned in the above post edit, I unplugged Ethernet cable.
2. I got ping response from the PW3 WIFI IP address found in my router
3. I decided to check Tesla One app before I start configuring cloud access for PW-dashboard. It was not able to find PW3 WIFI SSID.
4. After waiting a few minutes, the WIFI SSID reappeared. Then Tesla One app connected and all worked.

With that, I was able to restore connection as before using the DD-WRT travel router.

I get the feeling this whole episode is result of me using keep alive feature of travel router, doing too many pings? Because I noticed the travel router up time is very low every time I checked on it while it was all working.

Or may be two pyPowerwall instances constantly query the device made it stop responding on its own WIFI for a while?

[Nexarian]

First, I apologize for asking about the Tesla One thing twice. I was scanning the threads and reacted too quickly.

Second, I think an important takeaway from your experience is related to mine: The wifi on these Tesla boxes can be fragile, and cut out if hammered with too many requests. One of my inverters has a dodgy card that appears to fail if subjected to too many simultaneous requests, or really too many TOTAL requests over time, with the only remedy being a power-cycle.

Many report that the wifi cards on their tesla systems are rock-solid and don't seem to have this problem, but Tesla is known to use prototype hardware in their cars sometimes, they're likely doing it here as well for at least some devices.

[jasonacox]

That's great news @wyx087 ! The Powerwall will rate limit and even full deny all requests for 10m or so if it thinks it is being attacked. You will get 429 Too Many Requests or 503 Service Unavailable errors, but even during that, you will still be able to ping the device. That is why your case is so odd and probably more what @Nexarian is saying.

[wyx087]

Thanks both. I guess the PW3 WIFI (the AP) had cut out as result of too many re-connections and/or requests over time.

I did a quick power cycle, it was off for about 1 minute. Reading further into this, seems like I need to wait for over 1 hour.
https://energylibrary.tesla.com/docs/Public/EnergyStorage/Powerwall/3/OwnerManual/en-us/GUID-D239D3CE-AED7-41EA-88C0-13566FDF966C.html

Or wait ~5 days for it to reset itself.

I don't believe this is phPowerwall or dashboard related. So please close. Thank you very much for all your help.