Arie Catsman

> I just realized the timer is marked `cancel_on_shutdown` so it seems like we have a bug in the test tooling where its not being cancelled Tested with a cleanup...

Implemented envoy coordinator.async_cleanup called from async_uncload_entry to cancel token check timer and reverted the envoy_mock change.

To get a bit more info in the logfile you can extend the logging entry in configuration.yaml to: ```yaml logger: default: warn logs: homeassistant.components.enphase_envoy: debug httpx: debug httpcore: debug ```...

Getting the xml code in a tree without style info is the expected outcome. So the Envoy is responding to this request which is also used during the connection attempts....

What platform is your HA running on? (Docker, linux, HA-OS,....) Sounds as if the HA doesn't known where to find the Envoy, wrong interface, route, whatever. Does `traceroute envoy-ip-address` result...

It 'should' work as well on WiFi, but reality is often stubborn. Are the other devices also pulled or are they pushing to the HA? It seems that HA requesting...

The name envoy.local is not actually used, just a convience, ah well if it works..... The ip it finds comes from autodiscovery, the Envoy tells it's ip and HA reacts...

Hi @ShooterQ, the log file shows you are running the `Enphase Envoy (DEV)` custom integration. Issues for that integration should be reported at https://github.com/briancmpbll/home_assistant_custom_envoy/issues. If you intended to use the...

Any luck with this @bruisehilda?

Sorry to hear the trouble is still there, must be frustrating. In the mean time we've changed logic around timeout. I'm not saying this will solve the issue and trigger...