Tesla Wall Connector integration tries to connect to charger with the wring IP about core HOT 7 OPEN

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!

_{^{(message by CodeOwnersMention)}}

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

from core.

Happened again tonight: Integration is trying to reach 192.168.1.110 while the correct IP is .100.

The Tesla Wall connector is .100
See the crazy logs:

024-06-05 22:00:28.629 ERROR (Thread-5) [pychromecast.socket_client] [Tout(192.168.1.111):32186] Failed to connect to service MDNSServiceInfo(name='Google-Cast-Group-51A7B474C0D94695A20E5D3BAD856309._googlecast._tcp.local.'), retrying in 5.0s
2024-06-05 22:04:30.532 INFO (MainThread) [backoff] Backing off async_request(...) for 0.5s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.111)

We see above that at 20:00 the WiFi in the house dies.
Client .111 which is a chroma cast becomes unreachable.
4 minutes later, the TeslaWallConnector integration tries to connect to the Chromecast .111

Next log:
2024-06-06 06:46:36.045 INFO (MainThread) [backoff] Backing off async_request(...) for 0.7s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.100)

At 6:45 Wifi is back, TeslaWallConnector tries to contact the correct IP: .100
Fails one time but then all is good for the rest of the day.

Next log:
2024-06-06 22:04:32.680 INFO (MainThread) [backoff] Backing off async_request(...) for 0.8s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.110)

The next evening, WiFi goes off again. TeslaWallConnector tries to contact .110 (which is the wrong IP, as .100 is the correct.

Next log:
2024-06-07 06:46:34.603 INFO (MainThread) [backoff] Backing off async_request(...) for 0.7s (tesla_wall_connector.exceptions.WallConnectorConnectionError: Error while communicating with Wall Connector at 192.168.1.100: Cannot connect to host 192.168.1.100:80 ssl:default [Connect call failed ('192.168.1.100', 80)]) 2024-06-07 06:46:35.322 INFO (MainThread) [backoff] Backing off async_request(...) for 0.4s (tesla_wall_connector.exceptions.WallConnectorConnectionError: Error while communicating with Wall Connector at 192.168.1.100: Cannot connect to host 192.168.1.100:80 ssl:default [Connect call failed ('192.168.1.100', 80)]) 2024-06-07 06:46:35.830 ERROR (MainThread) [backoff] Giving up async_request(...) after 3 tries (tesla_wall_connector.exceptions.WallConnectorConnectionError: Error while communicating with Wall Connector at 192.168.1.100: Cannot connect to host 192.168.1.100:80 ssl:default [Connect call failed ('192.168.1.100', 80)]) 2024-06-07 06:55:02.403 INFO (MainThread) [backoff] Backing off async_request(...) for 0.5s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.110) 2024-06-07 06:55:03.879 INFO (MainThread) [backoff] Backing off async_request(...) for 0.7s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.110) 2024-06-07 06:55:05.552 ERROR (MainThread) [backoff] Giving up async_request(...) after 3 tries (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.110)

The next morning, Wifi comes back on, TeslaWallConnector tries to contact .100 for a little while then switches to .110 and will keep trying until I reinstalled the integration.

from core.

Another thing:
I disable the TeslaWallConnector integration at 21:55 and re-enable it at 6:55.
So why is it actively trying to contact the connector at 22:04 and at 6:46 exactly ?

Is there a 9 min time difference between the integration and HA Core ?

from core.

Tonight it tried yet another IP:
2024-06-08 22:04:30.328 INFO (MainThread) [backoff] Backing off async_request(...) for 0.9s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.109)

from core.

Happened again today. This time it was a power outage that stopped wifi brutally at 11:51.
When power came back, the integration had switched IP again:
2024-06-14 11:51:44.562 ERROR (MainThread) [backoff] Giving up async_request(...) after 3 tries (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.1.100) 2024-06-14 12:35:29.042 INFO (MainThread) [backoff] Backing off async_request(...) for 0.5s (tesla_wall_connector.exceptions.WallConnectorConnectionTimeoutError: Timeout while connecting to Wall Connector at 192.168.68.105)

from core.

I have "similar" problem with the integration trying to connect to the old IP of the Wall Connector. But in my case I cannot find the new IP either (despite scanning).
Let's say that it "aggressively" tries to talk to the initial IP, or something like that.

from core.

More info:
Today, after the integration started to call yet another IP (.108 this time), I want to the Integration page and clicked "Reload".
An error message was displayed in red reading approx. "cannot connect to 108".
At that point, I did not delete the configured Wall connector.
I tried to add another entity with the correct .100 IP.
I got an error message telling me that the entity is already configured and the existing entity started working again, calling the correct .100 IP.

So reloading the integration does not work, but trying to create a duplicate does reset the existing one to the correct IP.

Also, I do not understand why the integration tries contact the connector every day at 22:04 and 6:46, while the config entry is disabled.

from core.