Hello everyone,
after enabling “Third-Party Compatibility” my TAPO P100 thing is online, but there is something wrong with the communication. I am getting the following errors: invalid http-response (9001) and encrypting failed (9500).
The thing is generally not working properly.
My installation: openHAB 4.3.2, TapoControl Binding Version 4.3.2 on win10
Which update interval have you configured in the Thing settings for the Tapo device.
Refresh Interval - 30
I switched on the debug logs and have the same entries sporadically 2 or 3 times a day. The whole sequence starts with a timeout followed by other messages of that device. But in my case allways more then one device is showing up in a timespan of 20 sec. It looks like a network problem during that timeframe, I do not know whether this logs where there from the very beginning, or this is a new problem, because everything works fine, and I have not switched on debug logs over longer periods. I will check if this correlats with the magic switch in the tapo app. Will take some time.
Maybe I have more problems because of the older version? (TapoControl Binding Version 4.3.2)
I have solved my problem so far by using P110 instead of P100 which works perfectly without magic switch (of course I have disabled automatic FW updates).
I have got the same messages today, even if I switch off the magic switch with all my old devices as well. That means it is independent of the magic switch. It is independent from the Openhab version (I have 5.1 snapshot) and it is independent from the devices (I have timeouts with H100,P115,Lxx, S112, …). I had as well a look into the code, and cannot find anything wrong. The http request returns a timeout that is set to 5000ms. I will further investigate, ecspecially in my network.
I think the “timeout” error can occur here and there in WiFi intensive areas. For me it happened when I moved P110 from one socket to another. The main thing is that the functionality is not disturbed. My P100 (after FW update) from OH environment does not work at all. It only works from the mobi APP.
I will be away until Monday.
Best regards and thanks for your effort!
I’m also facing issues with P100 and P110 plugs, using openHAB 4.1 (and a patched org.openhab.binding.tapocontrol-4.1.0-SNAPSHOT.jar with KLAP support).
Until 2025-10-10 everything worked just fine. Now, all plugs are dysfunctional.
I can still control them through the Tapo app, but in openHAB logs I just see “(COMMUNICATION_ERROR): @text/no-error.
In the Tapo App I enabled the “3rd Party Compatibility” and restarted the plugs.
But I’m still seeing the same behavior.
From what I read here in the thread, the issue is not bound to the old openHAB 4.1 (with the patched binding for KLAP support), but also for newer openHAB versions, right?
Hi,
have you disabled automatic firmware update of the tapo plugs?
I have some P110M plugs arriving today, be interesting to see if they work with OH, if not, I’ll investigate.
All of my tapo p105, p110 and p115 plugs are working with openhab 5.0.1 and the corresponding tapo binding. The firmware versions are the following.
P105: 1.2.1 build 230804 rel 190922 (offering update to 1.2.5 build 240411 rel 143808)
P105: 1.2.5 build 240411 rel 143808
P110: 1.3.1 build 240621 rel 162048 (offering update to 1.3.4 build 250403 rel 150504)
P115: 1.3.1 build 240621 rel 162048 (offering update to 1.3.4 build 250403 rel 150504)
I have disabled automatic firmware update.
Actually I haven’t turned off automatic firmware updates. But there’s no way to flash an older firmware, right?
As there are reports about working OH5 bindings, is there a chance for a downmerge of the protocol change adjustments?
My plugs are using 1.3.4 Build 250403 Rel. 150504
Of course, I’m available for testing any updated plugin or support developing a fix by running some debug versions.
I just received some P110M switches. I updated to 1.3.2 uild 250526 Rel 171305
The switch is working fine for at least power on/off. In advanced settings, I have the Protocol set to Secured KLAP HTTP Protocol. I also enabled Third Party Compatibility in the Account Settings.
@Paul_Smedley Which openHAB version are you using?
I’m running 5.1M2
Sounds like the Binding has been updated in newer releases. Can the maintainer say something about this? Is there a chance of a “backport” for OH 4.1?
I’ve updated to 5.0.2. The plugs work now!
Unfortunately, there’s an issue with the Amazon Skill.
Let’s see when that will be fixed 
Hello, I have a Kasa KS240 that use the tapo protocol. Currently, I installed it in HomeAssistant that I linked in nodered and I update things in OpenHab with it, not the best implementation. I was wondering if it was possible to integrate it with Tapo Control?
Thank you
Hi, the implemtation is not as easy because in Tapo each device is different in its protocoll. Without having the device physically it is nearly impossible because you have to debug the protocoll and test it against the physical device. I don`t have the device and it seems to be not very popluar as it is for very special fans
hello, with OH 5.0.2 and Tapo P110 with FW 1.4.0 i’m not able to make them work.
any idea? tried all comunication protocol with no luck 
all of my Plugs were working before, with 1.3.4 FW