unable to add my **Tapo P110** smart plug to Home Assistant.

Third party integrations
1

Hello,
I am unable to add my Tapo P110 smart plug to Home Assistant.

When I try to add it using the TP-Link / Tapo integration or through the Tapo Controller (HACS) integration, the setup fails immediately and I get the following error message:

Connection error: Unsupported device 192.168.100.110 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)

Additional details:

  • Device model: Tapo P110
  • Firmware version: 1.4.0 (Build 251020 Rel.161559)
  • Hardware version: 1.0
  • The device responds in a browser (HTTP 200 OK)
  • It shows correctly in the Tapo app and works with no issues
  • Another Tapo device (P100) integrates normally with Home Assistant
  • Home Assistant and the P110 are on the same network
  • I am entering the correct local IP address: 192.168.100.110
  • Email and password for Tapo Cloud are correct (lowercase, no spaces)
  • HACS is installed and working normally

It seems like the P110 updated to a newer encryption protocol (TPAP/KLAP) and is no longer recognized by Home Assistant.

Could you please help me figure out how to integrate this device?

Thank you!

2

On the Tapo App on mobile, go to Third Party Services.

Check Third Party Compatibility is on. If it is, turn it off, wait a few seconds and then turn back on.

Then try and add device again in Home Assistant.

20 Likes
3

Hi have you sorted the problem out , its P110 update.
Allsorted !

4

Where is that? I cannot see that in my copy of the App

5

Bottom right corner of screen, little icon that says “Me”
Down screen “Third Party Services”

There it is…

6

@ santiniuk thank you for resolving my issue!

3 Likes
7

Hello

I’ve the same problem, already enabled Third Party Compatibility and also reseted the plug my holding the power button 10 seconds but still fails

Any idea?

8

If you resetted it You have to connect it through your App to you Network again

9

I noticed even with Third Party enabled, adding or re-adding a plug needs disable and reenable Third Party Compatibility set in the mobile app.

1 Like
10

This solved it for me as well. Until I disabled & re-enabled Third Party Compatibility I could not add the plug.
P.S.: After updating from FW 1.4.1 to 1.4.4, all my already paired P110M stopped working with HA. Disabling & re-enabling Third Party Compatibility also fixed that, without me having to re-add them.

2 Likes
11

I seem to be having the same problem with my P110 , Tried all the above with no success update the Tapo app (3.2.2) still no joy

Ok what did work in the end was to Change password in the app which ment I had to delete all my existing plugs in Home Assistant and re-add them and this time the ones that didn’t want to add did, Not sure if there is a way to change the password in Home Assistant Tapo add-on

12

I was able to add back the device doing the same, but still getting an error:

  • Unable to connect to Tapo: Cameras Control controller: PyTapo KLAP Error #3: (‘Device connection error: 192.168.30.200: Server disconnected’, ServerDisconnectedError(‘Server disconnected’))
  • Unable to connect to Tapo: Cameras Control controller: PyTapo KLAP Error #3: ('Unable to query the device: 192.168.30.200: ', TimeoutError())
13

This integration don’t support plugs, it’s only for cameras, and hub-with camera

14

It was not a plug, it was a P100 camera. I managed to get it working after changing my camera password to something all lowercase and no special characters as well, just for reference

15

Go here and search for similar issue as you experience
https://community.home-assistant.io/t/custom-component-tapo-cameras-control/

16

Just had this exact issue with a P110M plug. But only one of them … I have three others and a pile of P110 non matter plugs. Only one of them had this issue.

Disabling Third Party Support in the Tapo app and then re-enabling it fixed this one plug.

Very, very weird.

17

This worked for me, thank you, I disabled the Third Party Services and enabled it again.