OH5: TAPO P110 Error 9001 (unstable behaviour). Overview of possible solutions

My setup:

  • OH 5.0.2 stable
  • Official TAPO Binding (Version 5.0.2)

Goal:

I have 3 TAPO P110 Plugs.

  • Firmware:1.4.0 Build 251020 Rel. 161559
  • Firmware: 1.3.4 Build 250403 Rel. 150504
  • Firmware: 1.4.0 Build 251020 Rel 161559

Steps to reproduce:

  • Installed official TAPO binding on OH 5.0.2
  • Added Cloud-Login with TAPOControl Binding, successfully logged in with my TAPO credentials (Shows stable: Status Online)
  • Added Thing P110 using Cloud-Bridget. Advanced Settings → selected Secured KLAP HTTP Protocol. Set the correct IP Adress (triple checked from TAPO App), received invalid http-response (9001). Found hint on this form telling me to “switch on support for third party solutions” in the TAPO App. You find this in the app from the homescreen → Me → “Third Party Services” → “Compatibility with Third Parties” → Switch On.

Expected Behaviour

  • The thing will show stable “online” and remains in that state

Actual Behanviour:

  • The thing shows online (for several seconds) and then switches back and forth
  • Here is the log:
  • 2025-11-21 13:45:27.636 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘tapocontrol:P110:012b617b73:788CB5F160CE’ changed from OFFLINE (COMMUNICATION_ERROR): invalid http-response (9001) to OFFLINE (COMMUNICATION_ERROR): encrypting failed (9500)
    2025-11-21 13:45:34.377 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘tapocontrol:P110:012b617b73:788CB5F160CE’ changed from OFFLINE (COMMUNICATION_ERROR): encrypting failed (9500) to UNKNOWN
    2025-11-21 13:45:35.259 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘tapocontrol:P110:012b617b73:54AF977CBAB8’ changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): invalid http-response (9001)
    2025-11-21 13:45:36.391 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘tapocontrol:P110:012b617b73:788CB5F160CE’ changed from UNKNOWN to OFFLINE (COMMUNICATION_ERROR): invalid http-response (9001)

ANy ideas`? Should I just sell all TAPO Plugs? Which ones would you recommend?

What I already tried:

  • set Secured KLAP HTTP Protocol
  • set “enable third party apps” in TAPO App. That in part “helped”. Now adding a thing does not fail altogether. Now things are switching back and forth between online and offline (see log files above). So that is NOT really a solution
  • upgraded from 4.x to 5.0.2.
  • tried UDP Discovery on the cloud bridge, also tried cloud only discovery, also tried both.
  • prayed to the TAPO god to have mercy

Run Tapo App, go to Me → Services of other companies, and enable option “Compatibility with third-party products”. That might solve the problem

1 Like

Hi Nils,

thanks for your help,
as I already wrote in my posting “[…] ound hint on this form telling me to “switch on support for third party solutions” in the TAPO App. You find this in the app from the homescreen → Me → “Third Party Services” → “Compatibility with Third Parties” → Switch On. […] I already tried this. but it does not work stable. I think I’ll sell my TAPOs. I have trouble using TAPOs for over 1 year now. Thats enough. :frowning:

Hi Hannes,

I have exactly the same problem. The Tapo binding initial broke, and then I re-enabled “Compatibility with Third Parties” in the Tapo app. The Tapo binding then becomes unstable, often reporting the errors “encrypting failed (9500)” or “invalid http-response (9001)”.

I also tried upgrading to Openhab 5.0.2 and re-installing the Tapo binding and deleting and recreating the Tapo Thing and control Item.

One comment - the unstable behaviour is particularly linked to having the Tapo application open on my phone. Opening the Tapo app seems to trigger the problem.

Any advice would be very welcome. This is a strange and disruptive error.

I think that is all very disappointing. The TAPO App never has a problem to switch the TAPO devices while openhab seems to be very instable. Furthermore I also bought shelly plugs, which work rock solid with openhab (until now). So I give up using TAPO and sell them and buy shelly (it just takes to much time). If you find any solutions please let me know.

If you want to LOL here is the official answer of the TAPO support, asking them to help with the problem:

Thank you for sharing your suggestion with us! Your feedback is incredibly valuable as we strive to enhance our services for you. We’ve noted your input and will consider it as we move forward. Your engagement shapes our decisions, and we’re grateful for your contribution.

The above answer was provided by AI-powered search assistant designed to reply your question based on our pre-pared knowledge base. If you have further feedback or any concerns regarding product usage, please kindly respond to this email. Our agents will get back to you after analyzing the information you provide.

Depending on your region, Tapo plugs are pretty cheap. I got a 3 pack of P125M for around USD$20. Updated firmware to support Matter and they are solid with the Matter Binding (no energy monitoring however).

I found part of the solution. Unfortunately I tried to upgrade from oh 4.1 to 5.0.2. For this i created a separate docker container for running 5.0.2 and switched off 4.1 . At least I thought I switched it off. Only to find out that my nightly reboot of my synology restarted the 4.1 container without my knowing because the container was set to automatically start when power on. So in the end I had two oh containers running and interfering with one another.
So need to take back some of my critisism on TAPO devices. I already bough shellys instead. They are smoothly recognized during openhab thing scan (which the tapo devices cannot do) But apart from that they are running smoothly.

Sorry for my error and this unnecessary post. But I thought i would share my thoughts and error here, in case other people also try to safely upgrade oh and run into the same problem with double oh instances / containers.

Best regards

Hannes