Skip to content

[Bug]: Failed to connect Tapo H200 Hub (KLAP) - HTTP 403 on multipleRequest initialization #989

Description

@Tannyia

Written with Gemini, because i don't understand pretty much anything :))

Describe the bug

When attempting to manually add a Tapo H200 Hub via the integration, the setup fails with a Failed to connect error.

The logs show that the initial KLAP authentication succeeds, but the subsequent multipleRequest query fails with an HTTP 403 Forbidden response. The integration appears to query plug/bulb-specific methods (get_auto_off_config, get_device_usage, get_energy_usage) which the H200 hub rejects.

Device Information

  • Model: Tapo H200 Hub
  • Connected Sub-devices: Tapo S200B Buttons, T110 Contact Sensors
  • Protocol: KLAP

Steps to reproduce

  1. Go to Settings -> Devices & Services -> Add Integration.
  2. Select Tapo: Devices Control.
  3. Enter the local IP of the H200 Hub, along with the valid Tapo account credentials (all lowercase email).
  4. Click Submit.
  5. Integration immediately errors with Failed to connect.

Logs

Logger: kasa.transports.klaptransport
Source: components/tplink/coordinator.py:78
Query failed after successful authentication: Host is 192.168.0.138, Sequence is -359223672, Response status is 403, Request was {"method":"multipleRequest","request_time_milis":1786890208569,"terminal_uuid":"tij5OMiIUiYxEjmUVHZh+w==","params":{"requests":[{"method":"get_device_time"},{"method":"get_auto_off_config","params":{"start_index":0}},{"method":"get_device_info"},{"method":"get_device_usage"},{"method":"get_energy_usage"}]}}

Expected behavior
The integration should recognize the H200 as a hub/gateway and avoid requesting plug-specific metrics (get_energy_usage, get_device_usage, get_auto_off_config), allowing the hub and its connected sub-devices (like S200B) to be imported properly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions