The problem
Over the last week or two, one of my two P110 smart plugs has stopped appearing in Home Assistant. It was showing an SSL type error when trying to reload it.
I have tried setting third party services to on (it was off). Tried toggling it on and off too. Tried re-loading the device in HA. Checked the tapo app was up to date. Tried upgrading Home Assistant OS. Tried updating the firmware on the plug. Tried factory resetting the plug and re-adding it to Tapo app.
Tried deleting the device from home assistant, now when trying to re add the device in Home Assistant I get:
Connection error: Unsupported device 192.168.1.114 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)
What version of Home Assistant Core has the issue?
2025.11.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
TP-Link Smart Home
Link to integration documentation on our website
https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+tplink%22
Diagnostics information
Connection error: Unsupported device 192.168.1.114 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)
Example YAML snippet
Anything in the logs that might be useful for us?
2025-11-22 07:57:48.967 DEBUG (MainThread) [kasa.discover] [DISCOVERY] 192.168.1.114 >> {'system': {'get_sysinfo': {}}}
2025-11-22 07:57:48.969 DEBUG (MainThread) [kasa.discover] Waiting a total of 5 seconds for responses...
2025-11-22 07:57:48.977 DEBUG (MainThread) [kasa.discover] Unsupported device found at 192.168.1.114 << Unsupported device 192.168.1.114 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)
Additional information
Home Assistant OS 16.3
supervisor-2025.11.4
Operating System 16.3
Although it wasn't working on earlier versions too - upgraded all in an attempt to see if a fix was already available.
The problem
Over the last week or two, one of my two P110 smart plugs has stopped appearing in Home Assistant. It was showing an SSL type error when trying to reload it.
I have tried setting third party services to on (it was off). Tried toggling it on and off too. Tried re-loading the device in HA. Checked the tapo app was up to date. Tried upgrading Home Assistant OS. Tried updating the firmware on the plug. Tried factory resetting the plug and re-adding it to Tapo app.
Tried deleting the device from home assistant, now when trying to re add the device in Home Assistant I get:
Connection error: Unsupported device 192.168.1.114 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)
What version of Home Assistant Core has the issue?
2025.11.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
TP-Link Smart Home
Link to integration documentation on our website
https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+tplink%22
Diagnostics information
Connection error: Unsupported device 192.168.1.114 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)
Example YAML snippet
Anything in the logs that might be useful for us?
2025-11-22 07:57:48.967 DEBUG (MainThread) [kasa.discover] [DISCOVERY] 192.168.1.114 >> {'system': {'get_sysinfo': {}}} 2025-11-22 07:57:48.969 DEBUG (MainThread) [kasa.discover] Waiting a total of 5 seconds for responses... 2025-11-22 07:57:48.977 DEBUG (MainThread) [kasa.discover] Unsupported device found at 192.168.1.114 << Unsupported device 192.168.1.114 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)Additional information
Home Assistant OS 16.3
supervisor-2025.11.4
Operating System 16.3
Although it wasn't working on earlier versions too - upgraded all in an attempt to see if a fix was already available.