Upgrade huawei-lte-api to 1.6.11

[scop]

Proposed change

We need to deal with the issues solved in
e690db9 , #81751 (which this one brings back) some different way. They're less grave than the others it introduced.

Split up from #85572 in case we want to see this through separately first. Will rework that one if we do.

• https://github.com/Salamek/huawei-lte-api/releases/tag/1.6.8
• https://github.com/Salamek/huawei-lte-api/releases/tag/1.6.9
• https://github.com/Salamek/huawei-lte-api/releases/tag/1.6.10
• https://github.com/Salamek/huawei-lte-api/releases/tag/1.6.11
• Salamek/huawei-lte-api@1.6.7...1.6.11

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 An unknown error has occurred on the device #83226, component huawei-lte : Entities only available with authenticated mode #83994, Configure Routers with password but no user #85256, Huawei LTE failled add device #85311
• This PR is related to issue: Improve Huawei LTE SSDP inclusion #85572, Upgrade huawei-lte-api to 1.6.7, fixes empty username issues #81751
• 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 @fphammerle, mind taking a look at this pull request as it has been labeled with an integration (huawei_lte) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of huawei_lte 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 huawei_lte Removes the current integration label and assignees on the issue, add the integration domain after the command.

[rytilahti]

LGTM, thanks @scop! 👍

[rytilahti]

About the issue you described, should this be fixed in the huawei-lte-api or inside the integration itself? In any case, I think we can merge this now.

[scop]

Thanks! I think the mentioned issue should be fixed with us. I've a WIP branch towards that, will submit a MR soonish once I get some more things ironed out.

[rytilahti]

Ohh, should this go to the point release or rather wait for the next one (alongside the one this was spun out off)?

[scop]

Based on the number of issue reports we've received, I'd say at least this would be good to have in a point release.

The other I'll rework later this evening, no objections if that goes in in one as well. I think it's a less severe one though.