Fix flaky tests in advantage_air

[epenet]

Breaking change

Proposed change

#129735 reduced the occurrences, but it is still flaky

There must be a better way to resolve this - but I couldn't work one out...
I believe it is now resolved.

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:

Checklist

• 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.

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 @Bre77, mind taking a look at this pull request as it has been labeled with an integration (advantage_air) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of advantage_air 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 advantage_air 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.

[Bre77]

I'll take a look for the root cause soon. There must be some sort of race condition.

[epenet]

I'll take a look for the root cause soon. There must be some sort of race condition.

Yes - I think I have resolved the issue now: patching the reload timeout means that it reloads more quickly, before the next update triggers.

I think this is the correct way of resolving the race condition.

[bdraco]

Patching RELOAD_AFTER_UPDATE_DELAY isn't great, but its an existing issue

[Bre77]

I am reworking the tests because this whole reload business is redundant given we can test with @pytest.mark.usefixtures("entity_registry_enabled_by_default"), however since you have fixed the tests we might as well get this merged to fix the issue immediately.