Load initial data in the background so BLE setup doesn't block startup - #21
Merged
Conversation
async_setup_entry awaited async_config_entry_first_refresh(), so the initial BLE connect + reads (up to the 120 s connect timeout) blocked config-entry setup — HA logged "Waiting for integrations to complete setup" for a minute or more. Forward the platforms and run the first refresh in a background task instead. Entities already report unavailable until the coordinator has data, and it retries on its interval and on BLE rediscovery. Device resolution still runs in setup, so a missing device still raises ConfigEntryNotReady. test_async_setup_entry_success updated; the three setup-time refresh-error tests removed (dead path).
This was referenced Sep 4, 2026
Nailik
pushed a commit
that referenced
this pull request
Sep 4, 2026
The platform setups read coordinator.data.device_type to decide which entities exist. Since #21 the first refresh runs in a background task, so the data is still None when the platforms are forwarded and binary_sensor, select and sensor abort with AttributeError. Forward the platforms from that background task once the first refresh has produced data, retrying while the device is unreachable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
async_setup_entry awaited async_config_entry_first_refresh(), so the initial BLE connect + reads (up to the 120 s connect timeout) blocked config-entry setup — HA logged "Waiting for integrations to complete setup" for a minute or more.
Forward the platforms and run the first refresh in a background task instead. Entities already report
unavailableuntil the coordinator has data, and it retries on its interval and on BLE rediscovery. Device resolution still runs in setup, so a missing device still raisesConfigEntryNotReady.Tests:
test_async_setup_entry_successupdated; the three setup-time refresh-error tests removed (dead path).