Modernize Huawei LTE

[scop]

Breaking Change:

Configuration has been consolidated below huawei_lte.

Device tracker no longer uses known_devices.yaml but entity registry.

Description:

Modernize Huawei LTE quite a bit, config entry support, unauthenticated access.

Related issue (if applicable): fixes #23819

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#10380

Example entry for configuration.yaml (if applicable):

huawei_lte:
  - url: http://192.168.100.1/
    username: admin
    password: something

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist

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

• Documentation added/updated in home-assistant.io

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

• The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[scop]

So, here's a work in progress rework of the whole shebang, using entities disabled on discover, and entity enablement. Appears to work in principle, but I'm seeing some issues (see the "Work in progress" section).

[scop]

Also, the passing of system_options to disable new entities when creating the config entry requires #27044 to be applied first.

[balloob]

If I go to entity registry and enable some disabled entities, after a while I receive these errors in the logs (and the whole component stops working). Dunno why this happens, or how to prevent it.

That happens when Home Assistant does the reload. Apparently your integration does not deal with reloads well. You need to make sure that when an entry is unloaded, you unload and detach all things that you set up. You should not return from that method until it is all set up. So don't create task but await the forward unload calls.

[balloob]

So when you re-enable an entity, Home Assistant doesn't know where that entity is, nor can it instantiate it. So what happens is that we wait up to 30 seconds after the last change and then reload the integration.

https://github.com/home-assistant/home-assistant/blob/5c01dd483fc6bf2d15848b7f4ebcc99fb45bb705/homeassistant/config_entries.py#L823-L831

[MartinHjelmare]

Generally looks good I think. Beware of async vs sync context.

[scop]

Thanks a lot for the assistance, I'll address rest of the comments a bit later.

[scop]

Ok, with this batch of commits, stuff appears to work fine. Reload woes were because I was inadvertently using a mutable default defaultdict for all router instances (filed a couple of related pylint RFE's right after that), and there were some other less significant ones here and there.

I believe this is pretty much in a shape for inclusion now, still pending #27044 or similar, and the _better_snakecase should probably be turned to a general utility functions so other things can take advantage of it.

[scop]

Way to set system_options tweaked, and new hopefully less intrusive PR for it filed as #27612.

[scop]

Tweaked to enable a small known subset of sensors by default, no longer requires #27612.

[scop]

Should be good to go now.

[scop]

Re better snakecase: okunishinishi/python-stringcase#18

[MartinHjelmare]

Nice work!