Environment:
Home Assistant Core version: 2026.3.4
Installation type: Home Assistant OS on Raspberry Pi 4 (SSD)
Remote Home-Assistant version: 4.6
Remote connection type: VPN / Tailscale / ZeroTier (IP: 100.81.42.42)
Describe the bug:
When the remote Home Assistant instance is offline or unreachable due to network connectivity (e.g., a camper van parked without coverage), the remote_homeassistant integration blocks the Home Assistant startup process.
Instead of gracefully failing and retrying in the background, it hangs the setup loop until the Core Bootstrap watchdog intervenes after 60 seconds and forces the system to move forward.
Expected behavior:
The integration should catch the connection timeout early during async_setup_entry and raise a ConfigEntryNotReady exception. This would allow Home Assistant to finish booting the rest of the system instantly and let the integration silently retry the connection in the background when the network becomes available.
Logs:
Setup timed out for bootstrap waiting on {<Task pending name='debouncer cooldown=10, immediate=True' coro=<DataUpdateCoordinator._async_refresh() running at /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:426> wait_for=<Future pending cb=[_chain_future.._call_check_cancel() at /usr/local/lib/python3.14/asyncio/futures.py:390, <1 more>, Task.task_wakeup()]> cb=[set.remove(), Task.task_wakeup()]>, <Task pending name='Task-273' coro=<async_setup_entry..setup_components_and_platforms() running at /config/custom_components/remote_homeassistant/init.py:265> wait_for=<Future pending cb=[BaseSelectorEventLoop._sock_write_done()(), Task.task_wakeup()]> cb=[set.remove()]>} - moving forward
Steps to reproduce:
Configure a remote instance.
Disconnect the remote instance from the network.
Restart the main Home Assistant host.
Observe the 60-second delay and the bootstrap timeout warning in the logs.
Environment:
Home Assistant Core version: 2026.3.4
Installation type: Home Assistant OS on Raspberry Pi 4 (SSD)
Remote Home-Assistant version: 4.6
Remote connection type: VPN / Tailscale / ZeroTier (IP: 100.81.42.42)
Describe the bug:
When the remote Home Assistant instance is offline or unreachable due to network connectivity (e.g., a camper van parked without coverage), the remote_homeassistant integration blocks the Home Assistant startup process.
Instead of gracefully failing and retrying in the background, it hangs the setup loop until the Core Bootstrap watchdog intervenes after 60 seconds and forces the system to move forward.
Expected behavior:
The integration should catch the connection timeout early during async_setup_entry and raise a ConfigEntryNotReady exception. This would allow Home Assistant to finish booting the rest of the system instantly and let the integration silently retry the connection in the background when the network becomes available.
Logs:
Setup timed out for bootstrap waiting on {<Task pending name='debouncer cooldown=10, immediate=True' coro=<DataUpdateCoordinator._async_refresh() running at /usr/src/homeassistant/homeassistant/helpers/update_coordinator.py:426> wait_for=<Future pending cb=[_chain_future.._call_check_cancel() at /usr/local/lib/python3.14/asyncio/futures.py:390, <1 more>, Task.task_wakeup()]> cb=[set.remove(), Task.task_wakeup()]>, <Task pending name='Task-273' coro=<async_setup_entry..setup_components_and_platforms() running at /config/custom_components/remote_homeassistant/init.py:265> wait_for=<Future pending cb=[BaseSelectorEventLoop._sock_write_done()(), Task.task_wakeup()]> cb=[set.remove()]>} - moving forward
Steps to reproduce:
Configure a remote instance.
Disconnect the remote instance from the network.
Restart the main Home Assistant host.
Observe the 60-second delay and the bootstrap timeout warning in the logs.