Custom Home Assistant integration for TP-Link Tapo P110 smart plug using the TPAP protocol (TP-Link Adaptive Protocol).

Firmware 1.4.0+ replaced the KLAP protocol with TPAP (SPAKE2+ P-256 key exchange + AES-128-CCM encrypted data channel). Existing integrations (official tplink via python-kasa, HACS tapo via plugp100) do not support TPAP yet.

I was frustrated after I bought a new Tapo P110 (IN/1.20) and couldn't get any existing integration to work, so I built my own dedicated to the Tapo P110.

• Hub model — one config entry per TP-Link account, multiple plugs as device subentries
• Local polling — no cloud dependency after setup
• TPAP protocol — SPAKE2+ handshake with cloud credentials
• 27 entities per device across 6 platforms:

• Plug Power (outlet on/off)
• Auto-Off Timer
• Auto Firmware Update (config)
• Power Protection

• LED Mode (Always On / Auto / Off)
• Default State (Last 'On' State / On / Off)

• Power (W), Today/Month/Total Energy (kWh)
• Today/Month Runtime (Xh Ym format), On Time
• Voltage (V), Current (A)
• WiFi Signal (dBm), WiFi Signal Level, WiFi SSID
• On Since (timestamp), Device ID

• Overheat, Power Overload, Overcurrent, Charging Protection

• Reload Device — Refresh device session with a new handshake. Use this when the plug's entities show stale or unavailable data but the plug itself is responsive (e.g. after a network change or DHCP renewal).

• Auto-Off After (box input, 0–1439 min)
• Power Protection Threshold (box input, 0–3580W)

• Full raw device state dump with redacted sensitive fields

The Tapo P110 computes some statistics on the device side and only updates them when it has internet access (cloud sync). Without internet access, these entities show Unavailable until connectivity is restored — this is a device firmware limitation, not an integration bug:

All other sensors (Power, Total Energy, Voltage, Current, On Time, WiFi, Device ID) and every command (power, LED, auto-off, power protection) work fully offline over the local network — subject to the plug being reachable on LAN (see the [!IMPORTANT] note under Discovery).

1. Ensure HACS is installed in your Home Assistant
2. Go to HACS → Custom Repositories
3. Add this repository URL: https://github.com/rabilrbl/tapo-p110-ha
4. Select category: Integration
5. Search for "Tapo P110" in HACS and click Install
6. Restart Home Assistant

1. Copy the custom_components/tapo_p110/ directory to your HA custom_components/ directory
2. Restart Home Assistant

The integration uses a hub model: one config entry per TP-Link account (the "hub"), with one or more device subentries (one per plug) under it. Credentials are stored once on the hub; each device only stores its host address.

1. Go to Settings → Devices & Services → Add Integration
2. Search for "Tapo P110"
3. Enter:
   • IP Address or Hostname — your Tapo P110's local address (e.g. 192.168.1.100)
   • TP-Link Account Email — your TP-Link cloud account email
   • TP-Link Account Password — your TP-Link cloud account password
4. Click Submit — the integration will perform the TPAP handshake, create the hub, and add the first device

1. Open the existing Tapo P110 hub entry in Settings → Devices & Services
2. Click Add Device
3. Enter the IP Address or Hostname of the next plug
4. Click Submit — the device is validated against the hub's credentials and added as a subentry

Add the integration again with a different email + password to create a second hub. Each hub is independent.

Tapo P110 plugs are discovered via zeroconf (tplink*). If a hub already exists, discovered plugs are offered for addition to an existing hub; if no hub exists, the full setup form is shown.

• Home Assistant 2026.7+
• cryptography package (bundled with Home Assistant)
• ecdsa package — declared in manifest.json requirements, installed automatically by HACS on first setup

• TPAP protocol reverse-engineered from Tapo P110 fw 1.4.3
• SPAKE2+ implementation based on python-kasa PR #1592
• Tapo brand icon from home-assistant/brands