Tesla Powerwall Integration only supports Tesla Powerwall 1 & 2 as 3 uses a completely different API

[jwftu]

The problem

Hi,
Tesla Integration says it cannot connect with the Gateway and yet I can with a web browser. The error message says:
Failed setup, will retry: Powerwall is unreachable: Cannot connect to host 192.168.X.X:443 ssl:False [Connect call failed ('192.168.X.X, 443)]

What version of Home Assistant Core has the issue?

2025.4.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tesla Powerwall Integration

Link to integration documentation on our website

No response

Diagnostics information

Can't see that in this integration

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @bdraco, @jrester, @daniel-simpson, mind taking a look at this issue as it has been labeled with an integration (powerwall) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of powerwall can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign powerwall Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

powerwall documentation
powerwall source
_{^{(message by IssueLinks)}}

[aaronw2]

What version of Powerwall is it? I have it working with a Powerwall 3. I had to add Tesla fleet services for it to work. I saw the same thing until I set up the fleet services and integrated it with the Tesla OAUTH2 support.

[jwftu]

I'm running 25.2.0.fedab918 on a PW2. However, the problem now appears to have resolved itself, and I have no idea why

[Dave-Jones-1963]

I am using HAOS and trying to install the Tesla Powerwall integration I can't get it to login, Authentication failed with error: Access denied for resource https://10.88.x.x/api/login/Basic: bad credentials: Login Error
This is the IP address of the powerwall 3 battery which is connected via ethernet. Or should I be using another address? Also do I use the password for the battery or for the gateway? Am a little confused as I have various bits of information but not a clear understanding.

[aaronw2]

At least for me, I don't use the IP addresses of the Powerwalls. I followed the directions and got Tesla fleet support, and it uses Tesla's cloud support and OAuth2. It's described at https://www.home-assistant.io/integrations/tesla_fleet/
Once I did this everything got automatically integrated.

[Dave-Jones-1963]

At least for me, I don't use the IP addresses of the Powerwalls. I followed the directions and got Tesla fleet support, and it uses Tesla's cloud support and OAuth2. It's described at https://www.home-assistant.io/integrations/tesla_fleet/ Once I did this everything got automatically integrated.

This has an active alert saying it is now a Tesla paid for service.

[Sklls-Z]

I am now showing the same issue here:
Failed setup, will retry: Powerwall is unreachable: Cannot connect to host 192.168.x.x:443 ssl:False [Connect call failed ('192.168.x.x', 443)]

I can connect to the host from my desktop, so this error does not appear to be accurate and I believe this is an integration issue.

[purcell-lab]

I suspect this is a transient issue and tends to resolve itself over time.

Many issues can cause local connectivity issues, the Powerwall gateway at times seems to rate limit certain end points, or their maybe networking issues, ethernet is a lot more stable for connectivity over WiFi.

Recommend this issue to be closed as a transitory.

[Sklls-Z]

Tesla refused to hard-wire my Powerwall Gateway when I got it installed, so I didn't really have an option, unfortunately... Anyway, I resolved this by just moving to the Tesla Fleet implementation. Still not happy about that, but it's been flawless.

[Dave-Jones-1963]

I suspect this is a transient issue and tends to resolve itself over time.

Many issues can cause local connectivity issues, the Powerwall gateway at times seems to rate limit certain end points, or their maybe networking issues, ethernet is a lot more stable for connectivity over WiFi.

Recommend this issue to be closed as a transitory.

Still the same issues for me, so not very transient!

[LAdrain]

I have this since the powerwall3 was installed at the end of June. No luck trying to sign in with the integration, looks API related as the message returned is "/api/site_info returned error 404".
I can sign into the SSID with the full password with no issue.