Add Bridge module to AsusWRT

[ollo69]

Proposed change

I'm trying to split PR #71899 in multiple smaller parts.
This first PR just introduces the bridge module, that implement an abstract AsusWrtBridge class that than is derived to use a specific library (like SamsungTV integration bridge module).
With this PR there are no changes in integration functionality.

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
• The code has been formatted using Black (black --fast 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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[home-assistant]

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

Code owner commands

Code owners of asuswrt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign asuswrt Removes the current integration label and assignees on the issue, add the integration domain after the command.

[PeteRager]

What help can I provide to get your updated code acceptable to merge?

[ollo69]

The point is have a ha team member that review the PR. This is up to them.

[ollo69]

I caught two unhandled exception as I tested the change.

There are no change in the coordinator function here. This would happen here as in the version without bridge and exception is managed by coordinator. Do you mean that I should catch this exception and raise and UpdateError?

[bieniu]

Do you mean that I should catch this exception and raise and UpdateError?

Yes, those exceptions should end with UpdateError but we don't have to fix this in this PR. This was a side note.

[bieniu]

Please add IndexError to these two methods. This will fix the two exceptions I got a few days ago.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[ollo69]

Please add IndexError to these two methods. This will fix the two exceptions I got a few days ago.

Added also to _get_bytes that could have same issue

[bieniu]

Looks good 👍 Tested with RT-AX53U and works as intended.

[bieniu]

@ollo69 Please tag me in the next PRs you open to implement http communication and I'll try to help with the review.

[ollo69]

@ollo69 Please tag me in the next PRs you open to implement http communication and I'll try to help with the review.

Ok, thanks. I'll start working on this shortly.