Summary
P110 plugs running firmware 1.4.6 Build 260309 Rel.093810 fail local communication with the TP-Link Tapo Home Assistant integration (v3.5.0), while P110 plugs running 1.4.0 Build 251020 Rel.161569 work correctly.
The issue is reproducible across multiple devices.
All tested firmware 1.4.0 devices expose their local HTTP service on TCP port 80 and function correctly in Home Assistant.
All tested firmware 1.4.6 devices refuse connections on TCP port 80, cannot be added or controlled through the integration, and generate connection errors, while continuing to function normally in the official Tapo app.
The issue appears to correlate 100% with firmware version 1.4.6 Build 260309 Rel.093810.
Expected Behaviour
P110 plugs running firmware 1.4.6 Build 260309 Rel.093810 should be discoverable and controllable by the TP-Link Tapo Home Assistant integration in the same manner as P110 plugs running firmware 1.4.0 Build 251020 Rel.161569.
The integration should successfully connect to the device and create entities without reporting connection or authentication errors.
Environment
- Home Assistant (fresh installation)
- TP-Link Tapo Integration: 3.5.0
- plugp100: 6.0.0.dev2
- Approximately 48 TP-Link P110 devices
Observed Behaviour
After onboarding and testing approximately 48 P110 devices, I discovered a clear firmware split between devices that function correctly and devices that fail.
Working Devices
Firmware:
1.4.0 Build 251020 Rel.161569
Example device:
Test:
curl http://192.168.1.175
Returns:
HTTP/1.1 200 OK
Server: SHIP 2.0
Port scan:
Returns:
PORT STATE SERVICE
80/tcp open http
These devices are added successfully and operate normally in Home Assistant.
Failing Devices
Firmware:
1.4.6 Build 260309 Rel.093810
Example device:
Test:
curl http://192.168.1.165
Returns:
Port scan:
Returns:
All 1000 scanned ports closed
Not shown: 1000 closed tcp ports (conn-refused)
These devices:
- Continue to work normally in the official Tapo app.
- Remain reachable via ICMP ping.
- Fail to connect through the Home Assistant integration.
- Cannot be added or controlled locally.
Home Assistant Errors
Examples from Home Assistant logs:
Cannot connect to host 192.168.1.165:80
Cannot connect to host 192.168.1.155:80
Cannot connect to host 192.168.1.178:80
Additional log entries observed:
Query failed after successful authentication
and
aiohttp.client_exceptions.ClientConnectorError:
Cannot connect to host 192.168.1.165:80
Reproduction Steps
- Install TP-Link Tapo integration version 3.5.0.
- Add a P110 plug running firmware 1.4.6 Build 260309 Rel.093810.
- Enter valid Tapo account credentials.
- Attempt to add the device.
- Observe that setup fails with:
Cannot connect to host <device-ip>:80
- Verify that the same device remains online and controllable through the official Tapo app.
- From another host on the network, run:
- Observe that the device refuses connections on TCP port 80.
Firmware Correlation
Current testing shows a 100% correlation between firmware version and behaviour.
Working Devices
Firmware:
1.4.0 Build 251020 Rel.161569
Behaviour:
- TCP port 80 open
- Returns SHIP 2.0 page
- Successfully added to Home Assistant
- Fully controllable through the integration
Failing Devices
Firmware:
1.4.6 Build 260309 Rel.093810
Behaviour:
- TCP port 80 connection refused
- Cannot be added to Home Assistant
- Local communication fails
- Continue to work normally in the official Tapo app
Network Validation Performed
The issue does not appear to be network related.
Verified:
- Home Assistant host can reach devices by IP.
- Devices respond to ICMP ping.
- Working devices expose TCP port 80.
- Failing devices refuse TCP port 80 connections.
- VLAN routing is functioning correctly.
- Official Tapo app continues to control affected devices.
Additional Information
I found reports from other users suggesting that firmware 1.4.6 may no longer start the local KLAP/API service immediately at boot and may instead require discovery traffic before local communication becomes available.
This appears consistent with my observations because:
- Firmware 1.4.6 devices remain reachable by ping.
- Firmware 1.4.6 devices continue functioning through the TP-Link cloud and official Tapo app.
- Firmware 1.4.6 devices refuse TCP connections on port 80.
- Home Assistant reports connection failures rather than authentication failures.
Can you confirm whether firmware 1.4.6 Build 260309 Rel.093810 introduced any changes to startup or availability of the local KLAP/API service that would affect communication from the Home Assistant integration?
Thank you.
Summary
P110 plugs running firmware 1.4.6 Build 260309 Rel.093810 fail local communication with the TP-Link Tapo Home Assistant integration (v3.5.0), while P110 plugs running 1.4.0 Build 251020 Rel.161569 work correctly.
The issue is reproducible across multiple devices.
All tested firmware 1.4.0 devices expose their local HTTP service on TCP port 80 and function correctly in Home Assistant.
All tested firmware 1.4.6 devices refuse connections on TCP port 80, cannot be added or controlled through the integration, and generate connection errors, while continuing to function normally in the official Tapo app.
The issue appears to correlate 100% with firmware version 1.4.6 Build 260309 Rel.093810.
Expected Behaviour
P110 plugs running firmware 1.4.6 Build 260309 Rel.093810 should be discoverable and controllable by the TP-Link Tapo Home Assistant integration in the same manner as P110 plugs running firmware 1.4.0 Build 251020 Rel.161569.
The integration should successfully connect to the device and create entities without reporting connection or authentication errors.
Environment
Observed Behaviour
After onboarding and testing approximately 48 P110 devices, I discovered a clear firmware split between devices that function correctly and devices that fail.
Working Devices
Firmware:
Example device:
Test:
Returns:
Port scan:
Returns:
These devices are added successfully and operate normally in Home Assistant.
Failing Devices
Firmware:
Example device:
Test:
Returns:
Port scan:
Returns:
These devices:
Home Assistant Errors
Examples from Home Assistant logs:
Additional log entries observed:
and
Reproduction Steps
Firmware Correlation
Current testing shows a 100% correlation between firmware version and behaviour.
Working Devices
Firmware:
Behaviour:
Failing Devices
Firmware:
Behaviour:
Network Validation Performed
The issue does not appear to be network related.
Verified:
Additional Information
I found reports from other users suggesting that firmware 1.4.6 may no longer start the local KLAP/API service immediately at boot and may instead require discovery traffic before local communication becomes available.
This appears consistent with my observations because:
Can you confirm whether firmware 1.4.6 Build 260309 Rel.093810 introduced any changes to startup or availability of the local KLAP/API service that would affect communication from the Home Assistant integration?
Thank you.