home-assistant-tapo-p100
A Home Assistant custom integration for controlling TP-Link Tapo smart devices (plugs, light bulbs, switches, sensors) over local LAN. Supports device discovery, energy monitoring, and async operations native to Home Assistant.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | petretiandrea/home-assistant-tapo-p100 |
| Owner | petretiandrea |
| Primary language | Python |
| License | MIT — OSI-approved |
| Stars | 962 |
| Forks | 127 |
| Open issues | 22 |
| Latest release | 3.5.0 (2026-03-28) |
| Last updated | 2026-03-28 |
| Source | https://github.com/petretiandrea/home-assistant-tapo-p100 |
What home-assistant-tapo-p100 is
Python-based Home Assistant integration wrapping the plugp100 library, communicating with Tapo devices via LAN using both legacy and KLAP protocol. Provides async device control, diagnostics, firmware updates, and dynamic device-type detection through UI config flow.
Get the home-assistant-tapo-p100 source
Clone the repository and explore it locally.
git clone https://github.com/petretiandrea/home-assistant-tapo-p100.gitcd home-assistant-tapo-p100# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Email address for Tapo app authentication must be lowercase; uppercase letters cause 'Invalid authentication' errors—validate before deployment.
- Devices require internet access for periodic Tapo cloud sync even when using LAN control; network isolation may trigger credential sync failures.
- TP-Link is phasing in KLAP protocol via firmware updates; older firmware uses legacy protocol. Keep integration updated via HACS and monitor device firmware versions.
- Static IP assignment mandatory for device reliability; DHCP-based discovery is supported but tracking occurs via Home Assistant's native MAC address resolution.
- Discovery is not universal—not all Tapo models support native discovery. Manual IP+credentials configuration fallback required.
When to avoid it — and what to weigh
- Cloud-Only or Proprietary Control Required — This integration requires local LAN access and does not support cloud-only Tapo modes or devices locked to the official Tapo app. If your deployment mandates proprietary cloud integration, this is not suitable.
- Non-TP-Link Tapo Devices — Compatibility is limited to TP-Link Tapo brand devices. If you control other smart home brands, you will need separate integrations; this is not a multi-vendor solution.
- Zero Configuration or Minimal Networking Knowledge — Requires manual IP configuration, static IPs for devices, email lowercase constraints, and troubleshooting of KLAP vs. legacy protocol issues. Not plug-and-play for non-technical users.
- Production Critical 24/7 Uptime Guarantees — Maintained by a single individual with no SLA. 22 open issues and protocol-breaking firmware updates from TP-Link introduce risk for mission-critical deployments.
License & commercial use
Licensed under MIT (permissive OSI-approved license). Allows free use, modification, and distribution for commercial and private purposes, provided original license and copyright notice are included.
MIT license permits commercial use without royalty or special permission. However, this is a community-maintained project with no warranty or SLA. Commercial deployments should: (1) review the 22 open issues and single-maintainer status, (2) establish internal fork/maintenance contingency, (3) conduct security review of protocol implementation before production deployment.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Local LAN communication (no clear TLS enforcement documented for LAN traffic). Credentials stored in Home Assistant secrets management (standard HA pattern). No explicit audit or penetration test data provided. Protocol relies on TP-Link's KLAP and legacy encryption; upstream plugp100 library security posture unknown. Recommend: review plugp100 library security advisories, validate against TP-Link firmware release notes for protocol vulnerabilities, and isolate Tapo devices on separate VLAN if handling sensitive automations.
Alternatives to consider
Official TP-Link Kasa App + Home Assistant Cloud Integration
TP-Link's official Kasa integration exists for Home Assistant but requires cloud routing and Kasa account; trade-off of cloud dependency for official support and stability. No local-only control.
Generic MQTT + Tapo Device Firmware
Some users bridge Tapo devices via MQTT using alternative firmware or custom scripts (e.g., Tasmota derivatives). Requires flashing and offers more granular control but higher technical barrier and device warranty risk.
Lutron Caseta / Philips Hue / Native Matter Switches
If device ecosystem is not yet locked into Tapo, consider Matter-native or established proprietary solutions with larger vendor support, better documentation, and production-grade SLAs for home automation.
Build on home-assistant-tapo-p100 with DEV.co software developers
Install via HACS, configure device credentials, and start controlling your Tapo devices locally. For production deployments, review the maintenance status and security considerations.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
home-assistant-tapo-p100 FAQ
Do I need internet if I only control devices locally?
What is the difference between KLAP and legacy protocol?
Can I add Tapo devices not listed in the README?
Why do I get 'Invalid authentication' errors?
Software developers & web developers for hire
From first prototype to production, DEV.co delivers software development services around tools like home-assistant-tapo-p100. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source observability and beyond.
Ready to automate Tapo devices in Home Assistant?
Install via HACS, configure device credentials, and start controlling your Tapo devices locally. For production deployments, review the maintenance status and security considerations.