@bdraco suggested having separate timeouts in HA-land for the connection phase vs the full-loading phase of all the leap requests/zones/etc. I'm finding that approach challenging as the _connect() logic is so intertwined in the Smartbridge state machine. Instead, a more simple approach may be to define a helper function that tests connectivity to the bridge, which HA can call to verify connectivity and report any issues back to the user, before the full load which will be given a longer timeout (BRIDGE_TIMEOUT) for large QSX deployments.
Hi there! I'm trying to resolve https://github.com/home-assistant/core/issues/110067
@bdraco suggested having separate timeouts in HA-land for the connection phase vs the full-loading phase of all the leap requests/zones/etc. I'm finding that approach challenging as the _connect() logic is so intertwined in the Smartbridge state machine. Instead, a more simple approach may be to define a helper function that tests connectivity to the bridge, which HA can call to verify connectivity and report any issues back to the user, before the full load which will be given a longer timeout (BRIDGE_TIMEOUT) for large QSX deployments.