Replies: 112 comments 539 replies
-
|
Yes! It appears that this was one of the features of this upgrade. I see others reported it on Reddit including someone saying that it used to do this in the past (slow charge after 95%) but that it was dropped about a year ago until this 'foxtrot" version brought it back. I do find the "drops" to be interesting. That seems more like a computational error on % capacity than a reasonable behavior of the battery.
|
Beta Was this translation helpful? Give feedback.
-
|
Another example... It seems like at 95%, it slows the charge significantly, 22% of what it was before. At each percentage point, it seems to drop even more (bends happening at 96% and 97%. But at 98% it jumps to 100%.
I'm not sure if this will help long term battery degradation but at least in my case, the slope has been flattening as new firmware version come out.
|
Beta Was this translation helpful? Give feedback.
-
|
I haven't seen this behaviour yet (or in the past either) - my system is still on firmware 22.18.3 21c0ad81. It does seem odd with the sudden drops and I agree, it seems like a calculation error on the charge level, which likely updates once load is applied to the battery again. Regarding the charge percentage drop to zero during firmware updates as seen in @cwagz's graph - I have been meaning to suggest a proposed change to pypowerwall around this, but haven't gotten around to it. I have observed (and have logged data) that during a firmware update, the local gateway will still respond to certain requests (i.e. soe & aggregates) but it returns a value of zero for all measurements while the firmware updates. Interestingly, requests for other data like freq or battery temperature, do still return valid values (not zero) or simply you do not receive a response. Personally I think it would be better if pypowerwall detected this (could be simple, i.e. if charge percent and all aggregate measurements = zero), and then does NOT return data. Returning zero value data points causes some issues... noted recently in #103 which is when I started some investigating. @jasonacox - thoughts? I could raise this as an issue in pypowerwall perhaps if you agree. |
Beta Was this translation helpful? Give feedback.
-
|
It's a reasonable idea @mcbirse. Thanks for raising it. However, my concern is that the "zero" data is a correct representation of the response from the Powerwall Gateway (which Tesla could someday change themselves). Since the pyPowerwall library is an API for the Powerwall, the expectation is that it delivers accurately what Tesla is saying. While not altering the API itself, I would entertain adding this augmentation logic to the pyPowerwall Proxy that Powerwall-Dashboard uses with a configuration setting that would cause it to produce "None" responses during a detected firmware upgrade event. Of course, if Tesla changes the pattern where all measurements drop to zero during upgrades it would stop working. It could be a moving target. 😜 It may be better to use the authoritative upgrade signal (alert or some vitals setting?) and key off of that. |
Beta Was this translation helpful? Give feedback.
-
|
I think you're right... the "zero" data is a correct representation of the response. And knowing Tesla, they could very well change the behaviour of the responses in the future, so it's probably not worthwhile trying to second guess and filter responses. From checking my data, it appears the "zero" responses are for a short period only during a firmware upgrade (5 minutes). As per #103 it is fairly easy to delete these data periods if they are not wanted. I guess if there was demand for this it could be looked at further. |
Beta Was this translation helpful? Give feedback.
-
Firmware 22.26.2This version seems to have fixed the slow charging issue with the Powerwall. With version 22.26.1, it started trickle charging at around 85-90% and would never get above 95%. With this new version it charges up to 98% and then starts trickle charging at 0.7 kW to the final 100%.
|
Beta Was this translation helpful? Give feedback.
-
|
On a related note, @jasonacox could we add firmware version tracking to the database and dashboard? |
Beta Was this translation helpful? Give feedback.
-
|
I really like that idea @longzheng ! |
Beta Was this translation helpful? Give feedback.
-
|
The latest dashboard nows shows current Firmware version.
It is not getting stored in InfluxDB but we could add a telegraf call for http://powerwall:8675/version |
Beta Was this translation helpful? Give feedback.
-
Firmware 22.26.4
This version seems to have changed the pattern for Powerwall charging from solar. I set the reserve limit to 90% to drive all solar energy to the Powerwalls for charging. I noticed that the Powerwall charging plateaued at 3.6kW and the additional solar power displaced grid usage despite not being at the PW reserve limit. I wonder if the new firmware is limiting charging to 1.8kW per Powerwall to extend life of the battery? Does anyone else see this?
To early to see if this would actually help slow battery degradation. In the past year since I have been recording capacity, the degradation has slowed. I don't know if that is related to these software updates better managing the life of the PWs:
|
Beta Was this translation helpful? Give feedback.
-
Firmware 22.36.4Mine just updated to 22.36.4 71cc31f1 at 4:12pm today. I'm in Melbourne Australia and I'm on Tesla's VPP called the Tesla Energy Plan in Australia. The STSTSM firmware is Has only been a few hours so don't notice anything new. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @longzheng ! Others are reporting the upgrade and have pasted their Alerts here: #158 (comment) Did you see anything new/unusual on your Alerts panel in the dashboard (if you have it installed)? |
Beta Was this translation helpful? Give feedback.
-
|
These are my alerts
Nothing new/unusual compared to the other user. |
Beta Was this translation helpful? Give feedback.
-
Firmware 22.36.6 (and rollback to 22.36.4)
Observations
Upgrade Alerts
|
Beta Was this translation helpful? Give feedback.
-
|
I should also mention: Today was kind of crazy for our solar production, because clouds were in and out. And we were getting high numbers sometimes due to cloud reflections. For example, we peaked at about 6.67 kw, but for this time of year we normally peak around 5 kw. I wonder if that somehow caused a false arc fault.
|
Beta Was this translation helpful? Give feedback.
-
|
The system has been running fine for the last few days until this afternoon. We have had clouds in and out all day - sometimes very high solar output from cloud reflections. We got 5 arc faults and on the fifth one, the solar is locked off on the pw+. Our old solar system still working OK. About 10 months ago when the pw+ system was about one month old, we also had the solar lockout due to arc faults. Then there was no problem after they upgraded firmware. Now we have this new firmware 22.36.4 and seeing the arc lockout again. Not sure yet if this is due to new firmware or not. Later I will reset the arc lockout and see how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
Wow! I do love the visibility the Alert graph gives us. But that still feel a bit like a hardware issue to me. Strange how it happens for all the PVS data points at the same time. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, that Alerts logging and display is awesome! Now I know that it takes 5 arc faults to cause a PV lockout. I reset the lockout at around 3 pm yesterday and it worked fine after that. I am currently thinking that the arc faults are from sudden changes in current due to cloud movement and reflections. When I got the first PV lockout last year due to arc faults, it was also a cloudy/sunny day. Last night there were several other alerts I had not seen before - mainly for checking the system. All is well today. My pw+ solar has two strings of six 400w panels each. The string current for both when the arc faults occurred are in lock step, as usual. String A always has just a bit more power output. Last night I did some tug tests on the wires in the pw solar disconnect and pw inverter and all looked good. Here is the string current for the time when the arc faults occurred yesterday: What I don't know is if the recent firmware update made arc faults more sensitive or not. For about 10 months, I had no PV lockouts and as I mentioned before, the Tesla techs at that time said there was a known firmware problem causing false arc faults and my firmware had been upgraded. Thanks to the Powerwall Dashboard, I can now keep track of a lot more data, especially the alarms. |
Beta Was this translation helpful? Give feedback.
-
|
Today we had dark clouds and rain all morning. There were sudden spikes when it got sunny off and on in the afternoon. One arc fault occurred at 3:30. After 5 minutes, it turned back on at 430 watts, then after 15 more minutes it went back to full power (about 3.5 kw at the time). There were more spikes later but no more arc faults.
Will see if I get 22.36.7 tonight. I live in Rancho Mirage, CA (about 7 miles east of Palm Springs) - the desert - and dark clouds and sun are rare here. This year it had been nice to get some decent rain for a change. |
Beta Was this translation helpful? Give feedback.
-
|
Where can I find a description of the Alerts? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately there isn't anything official from Telsa but the community has gathered a list based on experience: https://github.com/jasonacox/pypowerwall#devices-and-alerts |
Beta Was this translation helpful? Give feedback.
-
|
For that alert page, I think POD_w058_SW_App_Boot alert is used to autostart a generator. I'm offgrid with two powerwalls and a generator and autostart is configured to come on at 25% charge and off at 50% charge. I see this alert fire whenever that happens and it lasts for the entire period of the purple line "SystemConnectedToGrid" (grid for me is generator).
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks @rvry - I added this note to the Alert list on pypowerwall.com. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for pointing out. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not sure which version 22.36.4 or 22.36.6 added this but I noticed there's a new graphic/link on the Powerwall Gateway login screen for the Tesla Pro app
The Android app is here https://play.google.com/store/apps/details?id=com.tesla.teslapros |
Beta Was this translation helpful? Give feedback.
-
|
Good find! Telsla Energy Setup - Upgrade NowThere's a better way to set up Powerwall Step 1: Disconnect from the TEG Wi-Fi network
Step 2: Tap the button below to download Tesla Pros Improvements include:
|
Beta Was this translation helpful? Give feedback.
-
Firmware 22.36.722.36.7 is out now. |
Beta Was this translation helpful? Give feedback.
-
|
Even today, I am pulling down around 18A at peak production on the Tesla system, so if only using one MPPT rated at 13A max, it would seem that it would fry or shutdown. But all is working perfectly. I wonder if one MPPT can actually handle 18A. Just now I measured voltages on the jumper terminals in the inverter. From any negative terminal (1-, 2-, 3-, 4-) to 1+ or 2+, I get the expected voltage of around 210 VDC. So it seems like the negative jumpers are connected together internally. But then why are jumpers needed, as @jasonacox mentioned. Maybe just to carry more current? |
Beta Was this translation helpful? Give feedback.
-
|
Forgot to mention that there was 0 volts between the negative terminals, such as one with a jumper and one without. |
Beta Was this translation helpful? Give feedback.
-
|
Just had a Gateway lockup with 22.36.7...hopefully they push 22.36.8 soon. |
Beta Was this translation helpful? Give feedback.
-
|
The jumpers are to bond the positive terminals, I don’t think necessary for negative as all are common rail. But if paralleling mppt’s you need to tell Inverter that the mppt’s are bonded. Or the mppt’s will hunt individually fighting each other. |
Beta Was this translation helpful? Give feedback.
-
|
@anderep Thanks for the info. Is -2 connected with -3 on the common rail? Or is -1 connected to -2, and -3 connected to -4? See my posts below. I did measure a tiny voltage between -2 and -3 after I fixed the negative jumper. After I connected the negative jumpers according to the installation instructions, I have not seen any arc faults yet. Also, when Tesla came out to check it (after I had fixed the jumper), the lead technician said that the negative jumper did need to be fixed (as I did) - and nothing should be jumpered between 1or 2 to 3 or 4. Hopefully the inverter is configured correctly, as you mentioned. Do you have a schematic for the inverter? We would love to see it! |
Beta Was this translation helpful? Give feedback.
-
Firmware 22.36.8
Firmware updated today - I Only new alert was "Battery Unexpected Power" but that could have been due to the timing (highest production time of day with 100% Powerwalls and pushing to Grid).
|
Beta Was this translation helpful? Give feedback.
-
|
I wonder why they don’t push these at like 2am. |
Beta Was this translation helpful? Give feedback.
-
|
I also see
|
Beta Was this translation helpful? Give feedback.
-
|
Agree @cwagz ! Thanks @longzheng - not sure what it means. |
Beta Was this translation helpful? Give feedback.
-
|
Yes the jumper is in the wrong spot. I have one of my jumpers as well incorrectly setup. You can fix this your self quite easily with a screwdriver and at night. Wait until the sun has fully set and it’s dark use a screw driver to push in the 3 terminal and move to the 1 terminal. |
Beta Was this translation helpful? Give feedback.
-
|
@robot498 I would love to see a schematic of the inverter. It sure appears all the negative terminals are common. If they weren't tied together inside the inverter, then MPPT1 would have never worked since it wasn't a complete circuit. The jumper could be a redundant path and help spread the current. A schematic could answer most of these questions. |
Beta Was this translation helpful? Give feedback.
-
|
@jgleigh: Yes, it would be great to see that schematic! I am still suspicious of firmware changes, too. Last year the Tesla techs knew about a false arc fault problem in firmware. When they came out, they just checked that the firmware was the latest and that the diagnostics passed. At the time, I did not know the PV lockout was after 5 arc faults (I thought it was after one). So I don't know if I had any arc faults but no lockouts after they left. The recent problems started after the 22.36.6 firmware update. A lot of unknowns! |
Beta Was this translation helpful? Give feedback.
-
|
Today I was looking around on the web for more information about the inverter jumpers - I happened to see a picture of someone using a clamp meter in the inverter. I have one and today I put it on the jumper from 1+ to 2+. It measured slightly less than half of the incoming current from the parallel strings, which makes sense - that is the current flowing to MPPT 2. So before I changed that negative jumper, I could have done the same check to see if any current was flowing into MPPT 2. I may put the jumper back and try that, but since all is working well, not sure I want to change anything now. It's not so easy to pop the jumper pin using the screwdriver, and it would be terrible luck to break something. Today I did measure millivolts between some jumper terminals: The system has been flawless since changing the jumper and there were two heavy cloud spike days since then, but time will tell. I may end up telling Tesla after next week not to come out since there is not much they could do, unless I see some arc faults in the coming week. |
Beta Was this translation helpful? Give feedback.
-
|
I agree. I looked at the wring from the connector board where you have plugged in the solar wires and the 7 wires going to the actual inverter board. On my box there are 4 red and 3 black. My guess is that 1 and 2 are separate negatives and 3 and 4 are shared negatives. |
Beta Was this translation helpful? Give feedback.
-
|
Just to follow up: A Tesla crew came out today (I had decided not to cancel the appointment to fix the MPPT jumper). I told them the situation about arc faults and that I already fixed the incorrect MPPT jumper connection. Immediately the lead technician said that was the correct thing to do. The entire crew seemed very knowledgeable. I displayed a couple of screens from Powerwall Dashboard showing the arc faults and PV lockout that occurred on March 20, and also showed some cloud spikes on days after fixing the jumper when there was no problem. They checked the inverter wiring and also went up on the roof to check connections for any evidence of arcing - non was found. I was pleased with the service they did today. Yesterday was another good test: dark clouds and bright sun. At one point I saw 24 amps coming down from my 2 pw+ six panel strings (normally peaks 19 - 20 amps this time of year), and there were no arc faults or any other problems. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like they added the PW versions to the release notes also. Guess we should be seeing 23.4 releasing soon. https://www.tesla.com/support/energy/powerwall/mobile-app/software-updates |
Beta Was this translation helpful? Give feedback.
-
Firmware 22.36.9
Only issue I saw was the power flow animation panel had an "Aw, snap!" error and required a refresh. I don't know if this was was a browser issue or if the recent iframe updates made it more brittle during upgrades. I would love to hear if anyone else experiences an issue. |
Beta Was this translation helpful? Give feedback.
-
|
Just got a MciOpen at noon. This 22.36.x series has had more weird issues. |
Beta Was this translation helpful? Give feedback.
-
|
And again today! 🤬 |
Beta Was this translation helpful? Give feedback.
-
|
Just FYI: I have only been seeing MciOpen on my system in the morning about 7 am, when it looks like it is checking rapid shutdown. Here are today's alarms so far, but I checked previous days and see the same thing.
|
Beta Was this translation helpful? Give feedback.
-
|
Yeah something is off and it's doing its daily checks at noon instead of early in the morning. I'm going to try a full system reboot tonight to see if it clears itself. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like it's reverted to the 7 am health check. Not ideal but better than noon. |
Beta Was this translation helpful? Give feedback.
-
Firmware 25.26.1 2c4bb00eJust got updated (18-8-25) to 25.26.1 2c4bb00e, lost telemetry for approx 5 minutes. Re-connected automagically to PW3 AP without issue. All good so far. UPDATE: Not sure if it's related to the firmware update but there are some errors from the proxy that I have not seen before: 08/19/2025 08:02:55 AM [proxy] [WARNING] Bad payload response in vitals - likely null/malformed data from Powerwall |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I am. Just thought it would be worthwhile mentioning this as since I sorted out PW AP > OpenWrt it has been rock solid, not a single disconnect or proxy degradation apart from when firmware was updated. There were no disconnects when the above occurred. Unfortunately, after many weeks of stable networking, the PW AP is doing the dance of disconnect/reconnect every few hours again. Frustrating. Just wish Tes could get their shit together and stop breaking things. |
Beta Was this translation helpful? Give feedback.
-
|
The bad payload may not be related to WiFi. I saw payload errors (missing keys or even null responses) even on direct hardwired connections before they dropped that support. Not sure why. |
Beta Was this translation helpful? Give feedback.
-
|
I also don't think it's related to WiFi as there are no proxy errors during periods of disconnect/reconnect (~5 seconds). Prior to this fw update not a single disconnect/reconnect for many weeks. Here we go again! |
Beta Was this translation helpful? Give feedback.
-
|
Keep an eye on http://localhost:8675/health to see if pypowerwall is detecting network or other issues. Endpoint stats over time will help: {
"/aggregates": {
"total_calls": 157758,
"successful_calls": 156747,
"failed_calls": 1011,
"success_rate_percent": 99.36,
"last_success_age_seconds": 4.010131120681763,
"last_failure_age_seconds": 36099.546214580536
},
"/soe": {
"total_calls": 157729,
"successful_calls": 157674,
"failed_calls": 55,
"success_rate_percent": 99.97,
"last_success_age_seconds": 4.056822061538696,
"last_failure_age_seconds": 63704.53446507454
},
"/strings": {
"total_calls": 157729,
"successful_calls": 157670,
"failed_calls": 59,
"success_rate_percent": 99.96,
"last_success_age_seconds": 3.5672459602355957,
"last_failure_age_seconds": 63704.45816373825
}
} |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. The below is reflects the accumulated stats since restarting yesterday. The proxy is absorbing the disconnect/reconnect without issue. PS C:\Users\Rick> $health.connection_health PS C:\Users\Rick> $health.endpoint_statistics.'/aggregates' PS C:\Users\Rick> $health.endpoint_statistics.'/soe' PS C:\Users\Rick> $health.endpoint_statistics.'/strings' PS C:\Users\Rick> $health.endpoint_statistics.'/vitals' |
Beta Was this translation helpful? Give feedback.
-
|
Comments on various Powerwall subreddit post indicate Low Energy Lockout is
being triggered by Tesla to prevent a safety issue by remotely draining the
PW then locking the units. Solar for self generation is supposedly not
impacted. Defective PW2 are being replaced with PW3, no word on how long
this will take and how many units impacted.
30 days ago
https://www.reddit.com/r/Powerwall/s/NfOloEHix1
Recent communication from Tesla support to impacted users
https://www.reddit.com/r/Powerwall/s/vm6wz9bbKR
2021-2022 year units likely. I’m on 25.18.5 and still up and running.
Install was 2023. Unfortunately, I haven’t gotten around to getting
dashboard setup again after API change so I’m no help in gathering
additional data.
…On Sun, Sep 14, 2025 at 00:07 Jason Cox ***@***.***> wrote:
I put in the request as soon as this happened 2 weeks ago. I finally got a
response:
Unfortunately your Powerwall 2 has an issue that cannot be fixed. A
replacement for the Powerwall is being issued and you will be able to
schedule a site visit in the Tesla app once the parts are available. We
will be sending an email when that's ready and usually the timeline is 10
to 14 business days.
I keep trying to figure out what could have been in this firmware that
would cause this. Irronically Tesla One apps says there are still no
firmware upgrades for me. I can't help but wonder if it will eventually
take out my Powerall+ as well. 😮
—
Reply to this email directly, view it on GitHub
<#109 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHGXCDMFPSEHMP3USNWARD3SUHZRAVCNFSM6AAAAAARLKZOSSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZZGQ4DMNQ>
.
You are receiving this because you commented.Message ID:
<jasonacox/Powerwall-Dashboard/repo-discussions/109/comments/14394866@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
See also https://www.tesla.com/en_au/support/energy/powerwall/own/powerwall-2-replacement |
Beta Was this translation helpful? Give feedback.
-
|
Notable it appears Tesla has forked their firmware lines (https://www.netzero.energy/firmware_versions): PW3 stands alone, and "not PW3 (or really, PW2/inverters/powerwall+)" is on a separate line. I'm still on 25.18.5 while it looks like the PW3 branch is moving forward faster. |
Beta Was this translation helpful? Give feedback.
-
Firmware 25.34.1 930a7700Updated 9/29 (PW2 and PW+ units). |
Beta Was this translation helpful? Give feedback.
-
|
My system updated to this firmware and then only charged to 89% today while the sun was up. I have never seen that behavior before. Maybe it figured it would sell more or something? Hopefully not a more ominous sign. |
Beta Was this translation helpful? Give feedback.
-
|
My system upgraded as well. My PW2 is fault mode, still waiting on Tesla design team who are looking to replace with PW3. Which would be interesting. Oddly, the battery fault alert disappeared during the firmware update, and became Battery Comms. 
|
Beta Was this translation helpful? Give feedback.
-
|
My solar inverters both updated to this version today. All is well. However, I have not noticed any improvements in wifi stability as were reported earlier. My dodgy inverter is still just as dodgy as it was in the past. The only notable change in behavior is I now have a new persistent alert on both inverters: |
Beta Was this translation helpful? Give feedback.
-
|
I have 2 powerwalls, and a gateway 2, and i am on this firmware. Today, i experienced a grid outage and the system just let me 'be down'. I had ~75% battery, and the system simply did not switch over to it. I had to manually switch to off grid mode in the app to use battery power - in the midle of the day, full sun, with almost 5kw coming off the solar panels. It came to life when i rebooted the individual powerwalls, but when i attempted to reproduce the error by flipping the breaker that connects the system to the grid, i was able to trivially reproduce the problem - when the grid fails, on this firmware, it doesnt switch to battery. |
Beta Was this translation helpful? Give feedback.
-
|
For the sake of data collection, I'll add that I am currently running Firmware 25.34.1 on a 4x Powerwall 2 w/Solar install and I am only receiving my normal set of alerts: |
Beta Was this translation helpful? Give feedback.
-
|
I am also on GW1/PW2 (2) plus solar and have no issues so far with 25.34.1. My alerts, after having a power outage from the grid yesterday, are: |
Beta Was this translation helpful? Give feedback.
-
|
Firmware 25.34.1 update on a PW3 with expansion pack, apart from having to restart Tesla app all seems fine. |
Beta Was this translation helpful? Give feedback.
-
Firmware 25.34.3 82272c3bUpdated October 21st on PW3. No issues to report. |
Beta Was this translation helpful? Give feedback.
-
|
Concerning firmware 25.34.3 82272c3b: I see this issue. PW3 (qty 2) - Grid charging rates dropped from 3.3 kW to 1.9 kW #696 |
Beta Was this translation helpful? Give feedback.
-
|
I'm also on Firmware 25.34.3 82272c3b But have started experiencing random LED flicker across the majority of rooms. It's not consistent and may appear for 2-3 minutes then stops. Only started following the Firmware upgrade. The LEDs are all GU10 style and four separate dimmers have shown the issue (when they were used). Anyone else experiencing this? |
Beta Was this translation helpful? Give feedback.
-
|
Does the dashboard show voltage of frequency changes happening during that time? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Jason, I don't currently have dashboard setup. One for a quiet weekend! |
Beta Was this translation helpful? Give feedback.
-
Firmware 25.42.0 2cd3dcfdAs seen on https://www.netzero.energy/firmware_versions and Reddit. Interesting table of differences in version: |
Beta Was this translation helpful? Give feedback.
-
Firmware 25.42.1 1d1ff4c6My system upgrades yesterday. Nothing to note. 
|
Beta Was this translation helpful? Give feedback.
-
|
Nothing to note on the vanilla PV inverter side either. Upgraded 2 days ago. Your errors are wild. |
Beta Was this translation helpful? Give feedback.
-
Powerwall 2/+ NoteI know someone mentioned this before but I couldn't tie it to the direct fw version, but for PW2 owners, the Powerwall gateway used to have a user accessible portal (see here) with some control (e.g. go off grid) and a powerflow animation. Now, the portal returns a static image and a redirect to a tesla.com site with instruction on how to connect locally: 
https://www.tesla.com/support/energy/powerwall/own/connecting-network The local API's still work (for PW2). Also some are helping to explore the new "local access" path (see jasonacox/pypowerwall#165 (comment)) to see if we can use that to connect via LAN or WLAN vs direct WiFi. |
Beta Was this translation helpful? Give feedback.
-
|
I'm running 25.42.1 and am still getting the battery charging issue that you've mentioned on 25.42.0. Unfortunately I don't know what the temps/fans are doing since I can't get TEDAPI since they blocked local access (I have my PW connected via LAN and I have no wifi card I can get to my dashboard). I am 99% sure that the problem has only shown up today because I check it regularly and noticed it wasn't charging within an hour or so of it sitting at 80%. I've been running the firmware for a little while now (it upgraded at least a week ago, can't tell further back due to Home Assistant being flakey with stats). |
Beta Was this translation helpful? Give feedback.
-
|
This may already be common knowledge, but it turns out that the change in charging behaviour is a new "feature". It should increase battery life (which is obviously good for us all) but it'll have a bunch of flow-on to our ability to keep battery on tap. |
Beta Was this translation helpful? Give feedback.
-
|
Seems to have been a problem with the remote monitor, proper charging came back after an hour. |
Beta Was this translation helpful? Give feedback.
-
|
Firmware: 25.42.1-operational-6 (upgraded on 11/25) My Powerwall 2 upgraded to a unique FW. After the upgrade one of the error seem to have resolved. "fan_speed_mismatch_detected" |
Beta Was this translation helpful? Give feedback.
-
|
Interesting! Do you happen to see a hash number in http://pypowerwall:8675/version ? |
Beta Was this translation helpful? Give feedback.
-
|
This is what I see "25.42.1-operational-6 b5289d33" |
Beta Was this translation helpful? Give feedback.
-
|
I see a small percentage registered in NetZero's report: https://www.netzero.energy/firmware_versions (or maybe that is just you :) |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it was only me.. I also have Netzero app installed |
Beta Was this translation helpful? Give feedback.
-
Firmware 25.42.1 ab1ab81dThis arrived on 2025-12-03 near 3 AM CST (Chicago) for the PW3. My hash number is different. Most all works OK. My only odd issue continues to be #696 (PW3 (qty 2) - Grid charging rates dropped from 3.3 kW to 1.9 kW) though now the charge rate is closer to 1.5 kW. |
Beta Was this translation helpful? Give feedback.
-
Firmware 26.2.1 a7456b0aArrived 2026-02-19 - near 3 AM CST (Chicago) for the PW3s. All seems OK so far! |
Beta Was this translation helpful? Give feedback.
-
|
Same here for PW3's. Dashboard captured some interesting alerts during upgrade transition: 
|
Beta Was this translation helpful? Give feedback.
-
Firmware 26.2.0 87adb89eBoth my non-Powerwall inverters were updated to Tiniest of nits, after a firmware update I always get the "GridCodesWrite" alert until the inverters are restarted again for any reason. |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Tesla Powerwall Firmware Versions
This is an attempt to help navigate the Firmware discussions. Table lists the most recent Firmware versions at the top.
Table added by @jasonacox
Firmware 22.26.1
Just curious if others are seeing the same behavior.
I have noticed, especially since the "foxtrot" firmware version, that my Powewalls are charging much less "smoothly". It seems to be going from 90% to 100% in steps now. I imagine this is better for the batteries. Also, I am seeing a much larger drop in charge level at 4:00PM when my system switches to battery to cover the TOU period.
The system is currently on firmware 22.26.1 1da541cb.
Charge level drops by 5% immediately at 4:00PM. It used to drop by 3%.
Charge behavior and initial drop on older firmware versions: (you can see the foxtrot upgrade here too)
Beta Was this translation helpful? Give feedback.
All reactions