Do not wait for an integration to initialize during startup

[agile imp]

My GoodWe solar inverter can only be reached by the HA integration when the solar panels give enough power. This means Home Assistant hangs during startup, waiting for the integration to initialize to continue the boot sequence. This is especially problematic becase add-ons are only started after the integration has timed out. Is there a way to configure this differently?

Or should the integration not block its initialization on being able to reach the inverter?

[light creek]

an integration failing should not block anything else from starting.

what version of home assistant are you running?
Are you using the core GoodWe integration or a custom one?

[agile imp]

HAOS 17.0, 2026.1.2, core integration

Note that it hasn’t failed yet, the connection attempt just takes a very long time before eventually failing

The “Home Assistant has started” toast takes minutes to appear, and it looks like this is the only thing happening

(This is on a Home Assistant Green)

[light creek]

would you say aprox 10 mins?

[agile imp]

I think closer to 3 minutes

I do see a warning in the logs:

Logger: homeassistant.bootstrap
Source: bootstrap.py:1005
First occurred: 17:12:32 (3 occurrences)
Last logged: 17:14:32

Waiting for integrations to complete setup: {('goodwe', '01KBQ3M3A933P7MRVFBC3XTAT6'): 86.349990605}

[light creek]

so in the integrations code

    try:
        inverter = await connect(
            host=host,
            port=port,
            family=model_family,
            retries=10,
        )

so its waiting for 10 timeouts before it fails which is probably why its slow.

I am not sure what the best solution to this would necessarily be though.
how major of an issue is this? how often are you rebooting your green?

[agile imp]

Makes sense

[agile imp]

Not very often, mostly just when upgrading. But since I run z2m as an addon, nothing requiring Zigbee functions for a few minutes longer than necessary, which is a bit annoying

(I am assuming that this blocks the startup somehow, have not checked that in the code)

[light creek]

I am not 100% sure but it might be the case that the supervisor is waiting to start other containers (addons) until HA is itself fully up. I am not sure on the exact start procedure.

[light creek]

At this point I suggest making a GitHub issue on the Core Repo HERE being sure to tag the integration documentation link correctly it will tag the code owner of the integration. you can add that given how the invertor works reducing the default attempts to something else may help limit the issues it causes. you can link to this thread too.

reducing the retries to something like 3 or 5 is probably sensible. and would speed things up.

[agile imp]

Thanks for your help! I will do that

[light creek]

Great, Happy to help investigate the problem. Hopefully a potential solution comes of it for you. Will see what the code owners come back with.

[agile imp]

Reported here: https://github.com/home-assistant/core/issues/161460

[tulip cape]

Better solution would probably be to put it in a separate task so the integration could finalize its setup without waiting if this is a common thing.

[agile imp]

Yes, that does sound better. Is there documentation about what an integration should and shouldn’t do during its setup?

[tulip cape]

It’s too much “depends on” I believe so would not be feasible to try to document but essentially an integration should be working once setup but for special circumstances one might have to do different things