Slow async_setup_entry (~90s) for second config entry on multi-device account

[t0mr0zier]

Summary

With two integration entries configured against the same Navien account (one per physical unit), the second config entry consistently takes 70–90 seconds to complete async_setup_entry. The first entry completes in well under that. No exception is raised; HA's bootstrap simply logs "Waiting for integrations to complete setup" until the slow entry finally loads. Once setup completes, all entities populate and update
correctly — this appears to be a startup-time issue only.

Environment

• Home Assistant Core: 2026.4.4
• Install method: Home Assistant OS
• Integration version: 1.0.1
• Navien units on the account: 2 (configured as separate config entries)
• Both units are instantly online in the Navien NaviLink mobile app during the slow HA setup, so the cloud / units themselves appear responsive.

Steps to reproduce

1. Configure two integration entries on the same Navien account, one per physical unit.
2. Restart Home Assistant.
3. Open Settings → Devices & Services → Navien NaviLink.
4. Observe one entry loads quickly; the other shows the dim spinner "Initializing" for 70–90 seconds before completing.

The same ~90-second delay applies to manually reloading the slow entry (3-dot menu → Reload) without restarting HA.

Logs

No exceptions or warnings specific to navien_water_heater appear during the wait. The only relevant log entries are HA's bootstrap "waiting" messages:

2026-05-02 08:39:49.223 WARNING (MainThread) [homeassistant.bootstrap]
Waiting for integrations to complete setup:
{('navien_water_heater', '01KP95P41ZKZJ95WXXZ16W468E'): 670336.117405715,
('reolink', '01KC9ZHVZ2GQ00T0952F4NV052'): 670357.025330631}
2026-05-02 08:40:49.295 WARNING (MainThread) [homeassistant.bootstrap]
Waiting for integrations to complete setup:
{('navien_water_heater', '01KP95P41ZKZJ95WXXZ16W468E'): 670336.117405715}

The second config entry (01KP95P41ZKZJ95WXXZ16W468E) is consistently
the one that hangs. Reolink in the same boot cleared during the gap
between the two messages, while Navien continued waiting.

What I've tried

• Restarted HA multiple times → consistently the same behavior.
• Reload the slow entry from the integrations UI → same ~90s delay.
• Confirmed via the Navien NaviLink mobile app that the unit is online and responsive throughout the wait.
• Increased HA debug logging on homeassistant.components.command_line and other suspects — nothing related to navien surfaced.

Hypothesis

It looks like setup of the second config entry serializes behind the first — possibly due to shared session/auth state being acquired sequentially per entry. Curious whether the device-info and sensor enumeration could be parallelized or the auth handshake reused across
entries on the same account.

Offer

Happy to capture additional logs (debug level on navien_water_heater specifically) or test a candidate fix on this account if it would help.

[t0mr0zier]

Debug log capture

Enabled custom_components.navien_water_heater: debug in configuration.yaml, restarted HA, and captured the first ~5 minutes of logs. Filtered for navien. Posting the relevant excerpt below — happy to attach the full log file if more context is
needed.

navien-tagged log entries (click to expand)

2026-05-02 10:09:37.927 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2026-05-02 10:09:37.929 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration navien_water_heater which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2026-05-02 10:10:50.625 WARNING (MainThread) [homeassistant.bootstrap] Waiting for integrations to complete setup: {('navien_water_heater', '01KP95P41ZKZJ95WXXZ16W468E'): 675914.599055948, ('reolink', '01KC9ZHVZ2GQ00T0952F4NV052'): 675943.131748412} 2026-05-02 10:11:50.686 WARNING (MainThread) [homeassistant.bootstrap] Waiting for integrations to complete setup: {('navien_water_heater', '01KP95P41ZKZJ95WXXZ16W468E'): 675914.599055948, ('reolink', '01KC9ZHVZ2GQ00T0952F4NV052'): 675943.131748412} 2026-05-02 10:12:50.760 WARNING (MainThread) [homeassistant.bootstrap] Waiting for integrations to complete setup: {('navien_water_heater', '01KP95P41ZKZJ95WXXZ16W468E'): 675914.599055948, ('reolink', '01KC9ZHVZ2GQ00T0952F4NV052'): 675943.131748412} 2026-05-02 10:13:50.823 WARNING (MainThread) [homeassistant.bootstrap] Waiting for integrations to complete setup: {('navien_water_heater', '01KP95P41ZKZJ95WXXZ16W468E'): 675914.599055948}

The slow config entry is 01KP95P41ZKZJ95WXXZ16W468E. The bootstrap "waiting for integrations to complete setup" messages span roughly the same 70–90s window during which the lines above were emitted.

Let me know if you'd like a different log filter (e.g., aiohttp, asyncio) or a longer capture window.

[t0mr0zier]

Root cause found. The NaviLink cloud echoes the request sessionID truncated from epoch-milliseconds to epoch-seconds (request 1780760417880 → echo 1780760417), so the response_events lookup in the response handlers never matches — and every waited request times out at the full polling_interval. The response data itself arrives and is processed fine, which is why entities work and nothing shows in the logs (the relevant exception paths log at debug).

Setup cost is therefore 2 × polling_interval per config entry, for every installation. My "second entry slow" was simply the entry with the longer polling interval crossing HA's 60-second bootstrap warning threshold — both entries were affected all along.

With sessionID matching fixed at seconds precision and the response-wait timeout decoupled from polling_interval (10 s), my two entries now set up in ~15 s and ~11 s instead of 43.8 s and 246.8 s, with zero bootstrap warnings.

Fix in #54.