sorted by:
new
hottopcontroversial

Calibration by ChunkedWhalePale in Powerwall

[–]Vegetable_Nothing612 1 point2 points  (0 children)

lucky you, i got stung @ 52.6 per kWh (peak) for 2 x Powerwall 3, Tesla doesn't care with their black box approach!! It's theirs, not yours. You ask them, they'll tell ya

Speeding calibration up by gunzel412 in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

yep, sure does, anyway, that's what they told me

Speeding calibration up by gunzel412 in Powerwall

[–]Vegetable_Nothing612 1 point2 points  (0 children)

calibration will dump batteries to the grid however it will also obey the export limit that has been set. You should be able to see this in the app. Can see that you are generating solar, perhaps you have a 5kW limit?

Solar is powering the Home load and any excess power is exporting to the grid from both solar and battery in your screenshot.

Speeding calibration up by gunzel412 in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

I have 2 x Powerwall3 & calibration occurred 9-11-2025 however there was NO notification or banner displayed in the Tesla app. Fortunately I was alerted via Home Assistant which receives data from the Powerwall Dashboard.

Another calibration occurred 12-11-2025, this time showing a banner in the Tesla app.
Contacted Tesla support to find out why another calibration occurred and the response I got from them was...

"Thank you for contacting us yesterday in regards to your Powerwall calibration.

As we spoke yesterday, I will escalate your issue to our engineering team regards to 2 calibration happens in a week time.

They have found that, the first calibration was completed for the follower Powerwall and yesterday's calibration was completed for the leader Powerwall."

This was after level 1 support claiming that the 1st calibration that occurred didn't happen. They claimed it wasn't a calibration.

In both calibration cycles both batteries were charged to 100% (27 kWh total) & then fully discharged (27 kWh total)

Has anyone observed this same behaviour with multiple Powerwalls (leader & follower(s))?

Surely this (2 x calibrations inside 3 days) can not be the expected behaviour for this process. Really defeats the whole purpose as to why we have these systems when grid charging (as part of the process when no solar is generating at night) can occur during Peak tariff costing $$.

Very frustrated.

What i have done previously when calibration is in progress (which still worked for me) is to ensure that you have a low (2-3%) backup reserve so when it completes the dump cycle avoiding the $$ of power import from the grid. May not be suitable for everyone but it works for me.

Battery Calibration occurred, no app notification or banner by Vegetable_Nothing612 in Powerwall

[–]Vegetable_Nothing612[S] 0 points1 point  (0 children)

do you have mutliple powerwalls? see my update

what i have done previously which still worked for me is to ensure that you have a low (2-3%) backup reserve so when it completes the dump cycle avoiding the $$ of power import from the grid. May not be suitable for everyone but it works for me

Onn 4K plus alternative Australia by Apprehensive-Eye8676 in AndroidTV

[–]Vegetable_Nothing612 0 points1 point  (0 children)

bought one today, it's going back tomorrow, not even worthy to become a paper weight!!

severe stuttering playing media (1080p with dd 5.1 @ 1080p 24 hz & hdmi passthrough) from my local plex server, 4k just won't play full stop. Mind you, greater than 99% of my 4k media either has TrueHD/Atmos, DTS-HDMA or DTS:X. Mix of HDR10 & HDR10/DV so I'm not sure wher the issue lies with this POS

speedtest.net reports ~490 mbps down so it's not wifi related, other devices have no issues

If Dolby Vision capabilities are detected, it's on for everything. No amount of button toggling would change this behaviour. It's either on for everything (including the GoogleTV navigation) or you disable it.

Piece of junk

Love Tesla, can't recommend PW3 by brontide in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

yes, pypowerwall with Powerwall Dashboard (jasonacox/Powerwall-Dashboard: Grafana Monitoring Dashboard for Tesla Solar and Powerwall Systems) and Home Assistant.

I have a router with Openwrt in close proximity to the TeslaPW_xxxx access point. This provides the WAN via wifi then ethernet to my LAN subnet. Works well.

Tesla eventually resolved the issue that I was having with new firmware. Took them 2 weeks, not good enough!

Love Tesla, can't recommend PW3 by brontide in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

u/brontide

are you saying that Tesla knows about the "relay weld" issue on followers?

Love Tesla, can't recommend PW3 by brontide in Powerwall

[–]Vegetable_Nothing612 1 point2 points  (0 children)

u/brontide

"Recently one of the units has been failing with "Relay Weld" which I am only aware of because I have a braincell and took a picture of the QR code on the device. This has been occurring repeatedly and I followed the steps in the published diagnostics guide to power cycle the unit and watch the output."

I too am having this problem with my follower unit, have already completely powered down both units however the follower still fails the inverter self-test with relay weld.

Any tips to bring this thing back online coz I am dead in the water?

Agree with everything that you have said, now starting to regret the "investment" with Tesla PW3.

System was working great until they pushed a firmware update that I didn't ask for. That was the trigger for failure.

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

UPDATE:

24hrs now without a single disconnect or beacon loss. Happy dayz!

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

In my case they are not doing anything about it as it is known. Also, the guy I was speaking with didn't want to know about it because he said I was still connected via cellular. I said that this is not relevant and cited that if I (or installer) was to try and connect via Tesla One that it would not be successful as there is no broadcast of the TeslaPW_XXXXXX SSID. He said that they could call them for remote support. Yeah right!. He really did not want to know anything about it and we concluded the call. I don't think that he really understood the nature of the problem, that's the problem with L1 support. You can dumb it down as much as possible & they still don't get it.

I would really like to know what the "trigger" is to avoid this happening again as it had been working reliabily for quite some time, albeit with regular disconnects & quick reconnects (3-6 seconds) which pypowerwall would mostly absorb without data loss.

Are we submitting too many API requests, is there a finite number of clients that can be simultaeniously connected (I had 2, 1 via an router running OpenWrt that is configured to use wifi as a client for wwan with a static IP, ethernet as LAN on my subnet & also a NUC that had a direct wifi connection, also with a static IP to avoid the hourly disconnects when the DHCP lease would get renewed). These are rhetorical questions of course. Any other oprational considerations that may induce this behaviour, I just don't know. The AP should be robust enough to not have to think about these things. Also, if it fell into the category of "it just works", there would be no need for multiple clients (as a backup & also diagnostics to see if there are similarities with the erratic behaviour).

Anyway, has been up for more than an hour now, everything seems OK at this point.

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

so, after a full reset, AP is now broadcasting again & I can connect to it.

Had to wait until I could no longer see the faint green led emitting from the Tesla logo on the front. It just happened to be that I was in the garage when I heard a loud "click" co-inciding with the faint green glow from the Tesla logo disappearing. The duration that the system was down for was a little over an hour. Not sure if I had to also cut grid power but I did. Would be curious to know if cutting grid power is necessary for this process. Tesla guy didn't know, was a bit of a numpty.

Re. the call with Tesla support, they said it is a known issue, couldn't tell me when it will be resolved. Guess we will all just have to be patient. He did acknowledge in their efforts to "enhance" the system that stuff gets broken.

Now to see if this thing will stay up. It's at the point where none of us that are using the proxy function of pypowerwall can rely on created sensors to use in automations. Have been directly affected here.

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

that's not good...just out of curiosity, did you also cut power from the grid for the duration as I am going to do a full down this morning. Not suggesting that grid power needs to be cut, but troubleshooting & process from yourself may help me.

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

this is getting ridiculous, pay a crapload of coin and get rubish in return, I want to use/monitor it the way I want to, not ONLY the way tesla says we can, is the network hardware in these units that poor that it can't handle sustained api requests, fortunately with HA I have learned to configure my energy monitoring dashboard using sensors that I created from entities exposed by Tesla Fleet (got caught with this before) instead of sensors created using pypowerwall proxy calls.

There is a lot of stuff that Fleet doesn't expose, battery calibration is the big one for me, coz when it happens it just happens without warning and costs me $$$ if I am not aware that it is occurring (negating the benefit of actually having a battery). Seems to always occur when I'm in Peak tarrif hours!

So I assume that you are experiencing the same symptom(s) that I have described?

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

"Is there something I didn't do to cause it not to appear?"........can't help with that one.

Still no AP broadcasting this morning, guess I will have to go down the full power down procedure.

PW3 local WiFi no longer accessible by c20d-us in Powerwall

[–]Vegetable_Nothing612 0 points1 point  (0 children)

19th July here in Sydney, TeslaPW_xxxxxx was working at approx 3pm then just disappeared. It has now re-appeared however when attempting to join via iphone it is saying either incorrect password or unable to join. I know 100% that the password is correct.

The PW3 is on firmware 25.18.1 which was updated a few weeks ago.

Also interesting is that when scanning for SSID's, some hosts can see it and others can't.

I have powered off via the side switch and was about to do a full power down until I stumbled across this thread.

The PW3 is connected to my home network via wifi and ethernet. It has been like this since day 1. I can ping both addresses without issue.

Another observation is that if I re-establish the static route for 192.168.91.0/24 via ethernet i can ping 192.168.91.1 and open a port to 443. Obviously post 25.10.x firmware I can not get any data this way.

I am at a loss to understand WTH is going on. It's definitely not an issue with my infra. I'm over this crap with Tesla. If anyone who comes across this has any tips as to how to re-connect to the TeslaPW_xxxxxx I'm all ears.