Fix OpenRGB tests failing CI

[thecode]

Proposed change

I noticed the following test failing CI:
https://github.com/home-assistant/core/actions/runs/18771740545/job/53557992992?pr=155073#step:11:249

Looking at the implementation it calls hass.async_block_till_done() multiple time to wait for an update, this doesn't make sense since it is not predictable and reaching a situation like this a good marker for something incorrect in the test.

core/tests/components/openrgb/test_light.py

Lines 377 to 380 in 3c098db

	freezer.tick(SCAN_INTERVAL)
	async_fire_time_changed(hass)
	await hass.async_block_till_done()
	await hass.async_block_till_done()

core/tests/components/openrgb/test_light.py

Lines 802 to 807 in 3c098db

	freezer.tick(SCAN_INTERVAL)
	async_fire_time_changed(hass)
	await hass.async_block_till_done()
	await hass.async_block_till_done()
	await hass.async_block_till_done()

I produced the problem and by waiting for background tasks it fixes the test failure.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @felipecrs, mind taking a look at this pull request as it has been labeled with an integration (openrgb) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of openrgb can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign openrgb Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[Copilot]

Pull Request Overview

This PR fixes flaky OpenRGB test failures in CI by replacing multiple sequential calls to hass.async_block_till_done() with a single call that waits for background tasks to complete. The issue was caused by unpredictable timing when repeatedly calling async_block_till_done() without waiting for background tasks, leading to race conditions in tests that verify state updates after time intervals.

Key Changes

• Replaced repeated async_block_till_done() calls with async_block_till_done(wait_background_tasks=True)
• Applied fix consistently across 7 test functions that were experiencing timing issues

[frenck]

Thanks, @thecode 👍

../Frenck

[felipecrs]

Thanks a lot for fixing it! I didn't realize it was causing trouble.

FYI there are multiple other integrations that do the same, like Tasmota. May be worth refactoring them too, even though they are not causing test failures. Would prevent other people from using them as reference, like I did.