Logbook entries repeatedly reporting entities as unavailable

[billraff]

I installed this integration yesterday and have observed that every few minutes (not correlated to the polling setting in seconds as best I can tell) the entire collection of entities becomes unavailable and then returns. I can watch this happen -

What could be causing this behavior? I assume it's on my side since I didn't see any issues describing this. My goal was to create an automation or two but if the automation were to try to run when the entities are unavailable it would fail.

[purcell-lab]

It would be really helpful if you could add the debug log to this issue, so we can see what the logs are reporting.

You can enable debugging from the integration tile.

[billraff]

I enabled the debug in the integration while the sensors were showing as available. Waited for them to become unavailable and then return to normal. Only took a few minutes. Is the debug log its own file somewhere or is it written to the home-assistant.log?

[purcell-lab]

Is the debug log its own file somewhere or is it written to the home-assistant.log?

When you switch off debug, it should download the debug file to your browser.

The details are also available in your home-assistant.log

[billraff]

Attaching log file.
home-assistant_tesla_custom_2023-10-10T10-50-59.083Z.log

Re-attached log file without address and other personal information.

[alandtse]

The logs are saying there's a connection error.
httpcore.ConnectError: All connection attempts failed
That typically indicate an error outside of the component. It could be the hardware, network connection, or your ISP. You will note that homeassistant.components.openweathermap.weather_update_coordinator also had trouble with the connection.

That said, at the end it appears to have resolved itself. But at this point, the logs don't show anything we can resolve.

[billraff]

Thank you for looking at the log. I'll do some digging on my end.