Missing support for TP-Link TPAP encryption (RV30, P100, ..)

[unze]

TPAP encryption type unsupported

This is a known problem that is being tracked in python-kasa/python-kasa#1590 .
Please read the description of that issue, and feel free to add a comment if you have another device/firmware version, but refrain from adding "doesn't work for me either" comments to keep the signal-to-noise high.

Note: some user reports indicate that toggling the "third party compatibility off and on again mitigates the issue.

---

Original report

The problem

After firmware upgrade of my two RV30-Max to Version 1.3.0 Build 250909 Rel.135514 the connection no longer works:

Verbindungsfehler: Unsupported device 192.168.0.84 of type SMART.TAPOROBOVAC with encrypt_scheme EncryptionScheme(is_support_https=True, encrypt_type='TPAP', http_port=4433, lv=2)

What version of Home Assistant Core has the issue?

core-2025.10.2

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://www.home-assistant.io/integrations/tplink/

Diagnostics information

home-assistant_tplink_2025-10-12T14-34-12.648Z.log

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[home-assistant]

Hey there @rytilahti, @bdraco, @sdb9696, mind taking a look at this issue as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tplink can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tplink Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

tplink documentation
tplink source
_{^{(message by IssueLinks)}}

[rytilahti]

This is the first time I have seen this encryption type (TPAP), so I guess they changed the encryption again & someone needs to figure out how it works and implement it in python-kasa. So feel free to open an upstream issue for a reference, and include the discovery output (kasa discover raw) for that device after masking the device_id, owner, and mac fields.

You could also try kasa --host <ip address> --username <email> --password <password> discover config to see if any combination of currently known connection parameters works.

[Redha-Idrus]

I have only recently been trying for the pass week to integrate my RV30 max plus, when auto discover, it is not found, when try to do manual, always gets Connection error: try_connect_all failed.

[victorhugoam18]

Same issue here !!!

[Imaginos]

Hi!
Same issue here.

[unze]

This is the first time I have seen this encryption type (TPAP), so I guess they changed the encryption again & someone needs to figure out how it works and implement it in python-kasa. So feel free to open an upstream issue for a reference, and include the discovery output (kasa discover raw) for that device after masking the device_id, owner, and mac fields.

You could also try kasa --host <ip address> --username <email> --password <password> discover config to see if any combination of currently known connection parameters works.

i tried both, here are the results:

kasa --host 192.168.0.84 discover raw
Discovering device 192.168.0.84 for 10 seconds
{
"discovery_response":{
"result":{
"device_id":"xxx",
"owner":"xxx",
"device_type":"SMART.TAPOROBOVAC",
"device_model":"RV30 Max(UN)",
"ip":"192.168.0.84",
"mac":"xxx",
"is_support_iot_cloud":true,
"tpap":{
"tls":2,
"dac":1,
"noc":1,
"pake":[
2
],
"port":4433
},
"obd_src":"tplink",
"protocol_version":1,
"factory_default":false,
"mgt_encrypt_schm":{
"is_support_https":true,
"http_port":4433,
"encrypt_type":"TPAP",
"lv":2
}
},
"error_code":0
},
"meta":{
"ip":"192.168.0.84",
"port":20002
}
}
Raised error: Unsupported device 192.168.0.84 of type SMART.TAPOROBOVAC with encrypt_scheme EncryptionScheme(is_support_https=True, encrypt_type='TPAP', http_port=4433, lv=2)

kasa --host 192.168.0.84 --username xxx --password xxx discover config
Attempt to connect to 192.168.0.84 with SmartProtocol + KlapTransportV2 + SmartDevice + https failed
Attempt to connect to 192.168.0.84 with IotProtocol + KlapTransport + IotPlug + http failed
Attempt to connect to 192.168.0.84 with SmartProtocol + KlapTransportV2 + SmartDevice + http failed
Attempt to connect to 192.168.0.84 with SmartProtocol + SslTransport + SmartDevice + https failed
Attempt to connect to 192.168.0.84 with SmartCamProtocol + SslAesTransport + SmartCamDevice + https failed
Attempt to connect to 192.168.0.84 with SmartProtocol + AesTransport + SmartDevice + http failed
Attempt to connect to 192.168.0.84 with IotProtocol + XorTransport + IotPlug + http failed
Unable to connect to 192.168.0.84

[tarasmurzenkovv]

Having the similar issue as well Unsupported device 192.168.1.135 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)

[geon106]

Same issue here

[schwarzbier01]

same issue with smart plug: Unsupported device 10.21.222.2 of type SMART.TAPOPLUG with encrypt_scheme EncryptionScheme(is_support_https=False, encrypt_type='TPAP', http_port=80, lv=2)

[r1ms4ab0r4ht5]

same here with P100 plugs, but not with a P300, but also present with the aforementioned RV30 max plus.
Managed to bring the P100's back online with steps:

• updated android Tapo app
• ticked "Tapo App -> Me -> Allow third Party access: Enable"

While that fortunately did work for the P100's, it unfortunately does not for the RV30 max plus.

Anyway - as I own quite a few P100's, that's at least "half of the success"

Then made a test:

Set up a stunnel as client to the RV30max, port 4433, and tried to access it via that stunnel (cleartext) socket.
That quite of worked from within HA, it does not trigger the nefarious error message ("TPAP" encryption message),
but yeah, as it then does request username / password afterwards, "there goes nothing" anymore after that (duh)...

Next try: socat TCP listener and client to RV30max plus, port 4433, that is, "stay encrypted all the way, but simply use
another way of communicating". But no luck, no error regarding that "TPAP" encryption scheme, but error after
requesting username and password. Error message then states something like "required_all_way" or sthg. like that.

So long story short; no, it did not fully work with that tried workarounds of mine (stunnel / socat), either.

But maybe that info can help with bugfixing ... ?

I mean, at least that "TPAP" scheme is TP-Link internal, so to speak, as the OP already mentioned
(after the said Firmware upgrade) - and yes, the error(s) did appear on the RV30max plus here, too, after that.

HTH anyone.

[Ham60elu]

Same here with smart plug P100:

still working in the tapo app ....