H100 Hub "Unsupported device... encrypt_scheme TPAP" — found a workaround (custom integration)

Share your Projects! Custom Integrations
1

If you’ve got a Tapo H100 hub on recent firmware (1.7.10 Build 260725+) and the built-in tplink integration refuses to set it up with:

Unsupported device ... encrypt_scheme EncryptionScheme(encrypt_type='TPAP', ...)

— you’re not imagining things. The H100 switched to a TPAP encryption scheme that the python-kasa library bundled with HA core (0.10.x) doesn’t implement yet. It’s a protocol-support gap, not something you can fix in config.

There’s an unreleased python-kasa fork (feature/tpap by ZeliardM) that does speak TPAP, so I built a small HACS custom integration on top of it to get the H100 and its paired sensors working again:

jan-tdy/TapoHub-ADV

  • Supports the H100 hub + T310/T315 (temp/humidity) and S200B (button) children
  • Entities generated dynamically from each device’s features — no fixed per-model mapping
  • Local only, no cloud calls from the integration itself (the hub does need your TP-Link account credentials once, to do the local TPAP handshake)
  • Install via HACS as a custom repository (steps in the README)

Please read before installing: this pins an unreleased, third-party python-kasa branch — it’s not upstream, hasn’t had the same review, and could stop being maintained at any point. Full disclaimer and risk details are in the README. Use at your own risk, and if/when TPAP support lands upstream, switch to the official integration (there’s a migration guide for keeping your statistics history).

Posting this in case anyone else has been stuck with a dead H100 integration — happy to hear if it works for your setup, or if you hit issues with other TPAP devices (S200B button events specifically haven’t been tested against real hardware yet).

1 Like