need to do regression testing with Home Assistant and make sure everything is still covered

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.96%. Comparing base (bbe7197) to head (0de2c10).
Report is 820 commits behind head on master.

@@            Coverage Diff             @@
##           master    #8680      +/-   ##
==========================================
- Coverage   97.98%   97.96%   -0.03%     
==========================================
  Files         107      107              
  Lines       33825    33860      +35     
  Branches     3969     3970       +1     
==========================================
+ Hits        33143    33170      +27     
- Misses        505      513       +8     
  Partials      177      177              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

manual testing looks good

Backport to 3.10: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 4f41d05 on top of patchback/backports/3.10/4f41d05e1a1340303a92e77a166646af370291e8/pr-8680

Backporting merged PR #8680 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.10/4f41d05e1a1340303a92e77a166646af370291e8/pr-8680 upstream/3.10

4. Now, cherry-pick PR Fix close race that prevented the close code from reaching the client #8680 contents into that branch:

   $ git cherry-pick -x 4f41d05e1a1340303a92e77a166646af370291e8

   If it'll yell at you with something like fatal: Commit 4f41d05e1a1340303a92e77a166646af370291e8 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 4f41d05e1a1340303a92e77a166646af370291e8

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix close race that prevented the close code from reaching the client #8680 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/4f41d05e1a1340303a92e77a166646af370291e8/pr-8680

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Backport to 3.11: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 4f41d05 on top of patchback/backports/3.11/4f41d05e1a1340303a92e77a166646af370291e8/pr-8680

Backporting merged PR #8680 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.11/4f41d05e1a1340303a92e77a166646af370291e8/pr-8680 upstream/3.11

4. Now, cherry-pick PR Fix close race that prevented the close code from reaching the client #8680 contents into that branch:

   $ git cherry-pick -x 4f41d05e1a1340303a92e77a166646af370291e8

   If it'll yell at you with something like fatal: Commit 4f41d05e1a1340303a92e77a166646af370291e8 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 4f41d05e1a1340303a92e77a166646af370291e8

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix close race that prevented the close code from reaching the client #8680 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/4f41d05e1a1340303a92e77a166646af370291e8/pr-8680

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.