core icon indicating copy to clipboard operation
core copied to clipboard

Telsa Wall Connector now has error "Failed to connect"

Open emptorium opened this issue 9 months ago • 39 comments

The problem

Not sure if it's since upgrading to 2025.2.0, had issues with my Tesla Wall Connector integration. All the entities failed to connect around 16 hours ago.

I tried removing the integration, power cycling the actual wall connector, restarting Home Assistant.

Since I removed the integration, the entities are gone. Manually adding the integration with the IP address of the wall connector results in "Failed to connect"

What version of Home Assistant Core has the issue?

core-2025.2.0

What was the last working version of Home Assistant Core?

core.2025.1.4

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Tesla Wall Connector

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tesla_wall_connector/

Diagnostics information

No response

Example YAML snippet


Anything in the logs that might be useful for us?


Additional information

No response

emptorium avatar Feb 07 '25 23:02 emptorium

Hey there @einarhauks, mind taking a look at this issue as it has been labeled with an integration (tesla_wall_connector) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tesla_wall_connector 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 tesla_wall_connector 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)


tesla_wall_connector documentation tesla_wall_connector source (message by IssueLinks)

home-assistant[bot] avatar Feb 07 '25 23:02 home-assistant[bot]

Are you able to provide more detailed logs, or nmap the device itself to check the device is actually responsive / the problem is clearly homeassistant?

Right now its not really possible to investigate

CloCkWeRX avatar Feb 09 '25 03:02 CloCkWeRX

Hi there, I was looking for logs but couldn't see anything as the device is no longer successfully integrated? If you have some steps for me to follow, more than happy to fillow them.

The tesla wall connector is working via the tesla app.

emptorium avatar Feb 09 '25 06:02 emptorium

I'm having the same issue for around the same amount of time. Getting the following logs: 2025-02-09 09:48:10.789 INFO (MainThread) [backoff] Backing off async_request(...) for 0.1s (tesla_wall_connector.exceptions.WallConnectorConnectionError: Error while communicating with Wall Connector at [redactedIP]: Server disconnected) 2025-02-09 09:48:11.061 INFO (MainThread) [backoff] Backing off async_request(...) for 0.5s (tesla_wall_connector.exceptions.WallConnectorConnectionError: Error while communicating with Wall Connector at [redactedIP]: Server disconnected) 2025-02-09 09:48:11.616 ERROR (MainThread) [backoff] Giving up async_request(...) after 3 tries (tesla_wall_connector.exceptions.WallConnectorConnectionError: Error while communicating with Wall Connector at [redactedIP]: Server disconnected)

KE55ARD avatar Feb 10 '25 15:02 KE55ARD

I'm experiencing the same issue with identical logs as @KE55ARD. Does this have to do with the tesla change over to the fleet api?

smurmann avatar Feb 10 '25 17:02 smurmann

I assumed mine had just dropped off wifi, so rebooted it and connected to it's AP and got a new message saying to download some "Tesla One" app to administer it, which I did and then saw it appeared to be for Tesla staff/partners so didn't seem to be much use. But made me question whether they've changed it's API or something?

KE55ARD avatar Feb 11 '25 07:02 KE55ARD

Same issue here, same period

ChucklesR avatar Feb 14 '25 04:02 ChucklesR

I also am having the same issue, started happening some time last week. I can confirm the device is accessible on the local network and via the Tesla app.

Giving up async_request(...) after 3 tries (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.xx.xx)

teejmiller avatar Feb 15 '25 04:02 teejmiller

same here - 7.02 HA have data from wallbox, next charging 10.02 integration cant connect to WC.

WallConnector itself have access to internet, I can ping it, working fine with tesla app

psujek-dev avatar Feb 15 '25 16:02 psujek-dev

I have nothing useful or additional to add, just adding to the "me too"s.

discgolfer74 avatar Feb 18 '25 23:02 discgolfer74

Having same issue. HA can't connect to the Wall connector. I try deleting it and re adding it back into HA. I just get an error that it Failed to connect.

Gearbot17354 avatar Feb 20 '25 04:02 Gearbot17354

I'm experiencing the same issue with identical logs as @KE55ARD. Does this have to do with the tesla change over to the fleet api?

Wondering the same thing since I also lost the ability for HA to do anything with the TWC....the timing seems about right.

Thunder7ga avatar Mar 02 '25 15:03 Thunder7ga

Always appreciative of the work done related to home assistant, not sure if this integration was created as volunteer work.

It's taken a while to get a response, I'm just glad my integration was more info than depended on for triggering. @einarhauks @CloCkWeRX , can you help?

emptorium avatar Mar 02 '25 20:03 emptorium

I get similar issue: Tesla Wall Connector always receives new IP from DHCP server after router restart. IP can not be static as Orbi does not allow to set static IP's for the guest network. On the other hand Tesla Wall Connector also does not allow to setup static IP address. Would be nice if it would be some automatic scan of network (e.g.: old_ip/24) in case of connection failure to detect the new IP.

slidertom avatar Mar 15 '25 00:03 slidertom

Adding myself as "me to" for this issue. Been trying to troubleshoot for the past month or so, no luck.

Confirmed the wall connector is accessible via HTTP, but the integration does not seem to connect anymore.

meppss avatar Mar 16 '25 15:03 meppss

Same issue here :(

sirloinofbeef avatar Mar 25 '25 07:03 sirloinofbeef

Same problem for me

Arturfrain avatar Mar 31 '25 18:03 Arturfrain

@einarhauks @purcell-lab , can you assist pls? Thx.

emptorium avatar Apr 03 '25 13:04 emptorium

@einarhauks @purcell-lab , can you assist pls? Thx.

It has been working rock solid for me, I haven't done anything special with the setup.

Image

purcell-lab avatar Apr 03 '25 21:04 purcell-lab

It failed for me after its IP address changed. There doesn't appear to be a way to manually change that so I deleted and re-added the integration and everything came back.

dougat3acres avatar Apr 05 '25 18:04 dougat3acres

@einarhauks @purcell-lab , can you assist pls? Thx.

It has been working rock solid for me, I haven't done anything special with the setup.

Image

Thanks. I wonder what is going on with mine and other's setup? I just upgraded to 2025.4.1 and turned the wall connector on and off. When trying to add the integration, still the same 'Failed to connect' message like everyone else

emptorium avatar Apr 06 '25 07:04 emptorium

It failed for me after its IP address changed. There doesn't appear to be a way to manually change that so I deleted and re-added the integration and everything came back.

tried adding back new integration and still getting 'Failed to connect'

emptorium avatar Apr 06 '25 07:04 emptorium

mine was working fine, didn't change anything in HA and integration suddenly stop working.

Maybe its relateded to Tesla API - I'm using teslafi.com and they need to change Tesla API on my account to get car telemetry

psujek-dev avatar Apr 06 '25 09:04 psujek-dev

I upgraded Home Assistant and just started getting this error. IP definitely didn’t change as it’s fixed in my DHCP server.

KE55ARD avatar Apr 06 '25 11:04 KE55ARD

I believe with Tesla Wall Connector firmware 24.44.0, the local webserver no longer is supported, which breaks this interface I believe.

I have a wall connector with this error and the 24.44.0 firmware.

I also have a wall connector with 24.43.3 which works fine and doesn’t ask me about Tesla One.

gautamvasudevan avatar Apr 14 '25 04:04 gautamvasudevan

I believe with Tesla Wall Connector firmware 24.44.0, the local webserver no longer is supported, which breaks this interface I believe.

I have a wall connector with this error and the 24.44.0 firmware.

I also have a wall connector with 24.43.3 which works fine and doesn’t ask me about Tesla One.

I have 24.44.3 firmware so you may be onto something.

emptorium avatar Apr 14 '25 04:04 emptorium

I'm failing to connect as well - firmware is 24.44.3

alexeiw123 avatar Apr 15 '25 01:04 alexeiw123

I'm on the same firmware and having this issue.

And suspiciously when I look in the app at the release notes for the wall connector, the latest firmware I can see is from October for 24.36. Almost seems like they didn't want to put up release notes for this version saying "we disabled the local web API, screw you HA users"

KE55ARD avatar Apr 15 '25 11:04 KE55ARD

Does anyone tried to downgrade firmware ?

psujek-dev avatar Apr 15 '25 16:04 psujek-dev

Does anyone tried to downgrade firmware ?

I've tried downgrading the fireware. Sadly I was not successful.

smurmann avatar May 03 '25 04:05 smurmann