TP-Link Tapo integration error message

[vagelisdermos]

Describe the issue
After update to the latest version 3.5.3 the home Assistant integration stuck in an "Initializing" loop and fails to load properly.
The integration encounters an unsupported child device with the model name AC and throws an error instead of skipping it or handling it safely, which blocks all other Tapo devices from loading.

To Reproduce
Connect a Tapo Hub to Home Assistant using this integration.
Open the official Tapo Android app and add an AC remote control to the IR hub.
Reload the integration or restart Home Assistant.
The integration gets stuck in "Initializing".

Error Log
This error originated from a custom integration.

Logger: HubChildrenComponent
Source: custom_components/tapo/hass_tapo.py:45
Integration: TP-Link Tapo (documentation, issues)
First occurred: 1:07:36 PM (616 occurrences)
Last logged: 1:13:36 PM

Found child device not supported, model AC
Please request support by opening an issue to https://github.com/petretiandrea/plugp100/issues/new

Environment
Home Assistant Core: 2026.7.0
Home Assistant Supervisor: 2026.06.2
Home Assistant OS: 18.1
Frontend Version: 20260624.3
Integration Version: v3.5.0
Tapo Device/Hub Model: T110
Installation Method: Home Assistant OS

[vagelisdermos]

I did some additional debugging on this.

The problem seems to be that the unsupported AC child device causes the Hub initialization to fail, instead of being safely skipped.

I tested the H110 directly with plugp100 and confirmed that the AC remote is correctly returned by the hub:

• child device type: SMART.TAPOREMOTE
• model: AC
• category: ir.remote
• device_id: 802DB0CDD8BA97DA7525E81F66EF10E9250EB5AD030B0007

The hub itself works correctly and the AC child can be queried successfully.

The important part is that an unsupported child device should not make the whole Hub initialization fail.

Could the integration handle unsupported child models by skipping them and continuing with the remaining supported children?

For example:

if child_model is unsupported:
    log.warning("Skipping unsupported Tapo child device: %s", child_model)
    continue

This would prevent Home Assistant from repeatedly retrying the initialization and getting stuck in an "Initializing" loop.

I think this should be handled independently from adding actual AC support. AC support can be implemented later, but an unsupported child should not block the entire Hub/integration.

I can also provide the raw H110/AC response if useful.

One additional finding from my testing:

I initially tried to access the H110 through TapoClient directly and found that TapoClient was instantiated with the TapoProtocol class rather than a protocol instance.

This resulted in:

TypeError: TapoProtocol.send_request() missing 1 required positional argument: 'request'

and during cleanup:

TypeError: TapoProtocol.close() missing 1 required positional argument: 'self'

Using the factory/connect path correctly creates a concrete protocol instance (KlapProtocol/PassthroughProtocol/etc.) and the H110 works.

So the main integration issue appears to be the unsupported AC child handling, rather than the H110 communication itself.