[TapoControl] - Control Tapo Smart WiFi-Devices with Openhab - Official Support Thread

Bize · November 15, 2023, 4:38pm

Hi!
Unfortunately I upgraded 4 of my P100 plugs after each other and now running into the same issue (connection error: 1003), on a OH3.3.
Is there any updated TAPO binding for OH3.x available which solves that issue?
Thanks!

Bize · November 15, 2023, 8:52pm

Also for me, this TAPO API client for python is working with a P100 plug with latest FW (FW: 1.5.5 Build 20230927 Rel. 40646, HW: 1.20.0).

Bigdesaster · November 16, 2023, 11:18am

No integration ist only available for OH4.
OH3 is not implemented.

MarkP1972 · November 24, 2023, 2:48pm

Thank you much for this information!
What do you think in the meantime: Will it be in 4.1? And if not, it is possible to install the new version of Tapo-Control-Plugin manually in OpenHAB 4.1 so I don’t have to wait until 4.2?

Kind regards,
Mark

magicofit · November 25, 2023, 12:00pm

After i updated my tapo-firmware (1.3.0 230905 Rel. 152200) i got API-errors for my tapo-(P110)-devices so i tried the newest org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT (commitsha 9698fff) from today, but even with the KLAP-Protocol i got “login failed (1111)” so saxxings solution is not working for me.

2023-11-25 12:50:31.323 [DEBUG] [l.devices.wifi.TapoBaseDeviceHandler] - (tapocontrol:P110:123456:987654321) check if logged in but is not
2023-11-25 12:50:31.334 [DEBUG] [rol.internal.api.TapoDeviceConnector] - (tapocontrol:P110:123456:987654321 / DeviceConnector) exception while login '@text/error-api-login-failed [ "1111" ]'
2023-11-25 12:50:31.334 [DEBUG] [rol.internal.api.TapoDeviceConnector] - (tapocontrol:P110:123456:987654321 / DeviceConnector) handle error '@text/error-api-login-failed [ "1111" ]'
2023-11-25 12:51:01.347 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'tapocontrol:P110:123456:987654321' changed from OFFLINE (COMMUNICATION_ERROR): login failed (1111) to UNKNOWN: login failed (1111)
2023-11-25 12:51:01.348 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'tapocontrol:P110:123456:987654321' changed from UNKNOWN: login failed (1111) to OFFLINE (COMMUNICATION_ERROR): login failed (1111)

Update:
After complete recreations auf things is got with KLAP:

2023-11-25 16:10:42.764 [DEBUG] [l.devices.wifi.TapoBaseDeviceHandler] - (tapocontrol:P110:123456:9876543) check if logged in but is not
2023-11-25 16:10:42.794 [DEBUG] [rol.internal.api.TapoDeviceConnector] - (tapocontrol:P110:123456:9876543 / DeviceConnector) exception while login '@text/error-api-hand-shake-failed [ "1100" ]'
2023-11-25 16:10:42.794 [DEBUG] [rol.internal.api.TapoDeviceConnector] - (tapocontrol:P110:123456:9876543 / DeviceConnector) handle error '@text/error-api-hand-shake-failed [ "1100" ]'

is there a solution out there? Thanks!

dheneghan · November 26, 2023, 9:30am

Running OpenHab 4-0-4

Last night 5 of my Tapo P110 plugs all started with the “unknown api error (-1)” error however 2 were still ok.

Discovered that the 5 had auto updated the firmware to 1.3.0 Build 230905 Rel 15220, the 2 which were still working had not.

After reading this thread

Updated the firmware of the 2 remaining working ones, which then (obviously) failed to connect to OpenHAB.
Downloaded the tapocontrol-4.0.4-SNAPSHOT.jar and put into the AddOns folder.
Removed the Market place binding.
Rebooted OpenHAB.
Went to each and changed the Protocol to "Secured KLAP HTTP Protocol| under the Advanced section

and all 7 devices have come back online without any issues.

Have now been into the Tapo App and turned off Auto Firmware updates for all the devices!!

Thank You so much for your continued work on this binding.

MarkP1972 · November 26, 2023, 9:52am

I did it one hour before your post and I wanted to post the solution here too.
I did it like you and all devices are running now!

magicofit · November 26, 2023, 2:51pm

Ok, now its also working for me.

I’ve done some additional stuff:
-Delete tmp&cache
-Update Openhab from 4.0.0 → 4.0.4
-Recreate tapo-cloud bridge without cloud discovery (only UDP) again

I was not sure, what exactly helped …but dave your post helps me, that this exactly issue is somehow fixable with this snapshot.

stefan13 · November 26, 2023, 9:30pm

Where can I download the fixed version org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT?

Can I use it for OH 4.1.0M3 as well?

Many thanks
Stefan

stefan13 · November 27, 2023, 5:16pm

I managed to download org.openhab.binding.tapocontrol-4.1.0-20231127.032506-101.jar
from jfrog.

Unfortunately I still see the same behavior. Doesn’t this version contain the new Secured KLAP HTTP Protocol?
I don’t get the new “Advanced Options” provided in the UI - still see only the “Refresh Interval”.

I removed the previous Add-on 4.1.0M3 and copied the new .jar in the /addon folder.
I seems to be recognized well, as per bundle:list output.

Anything else I need to consider?

324 │ Active │  80 │ 4.1.0.202311270409     │ openHAB Add-ons :: Bundles :: TapoControl Binding
openhab>  
324 │ Active │  80 │ 4.1.0.202311270409     │ file:/openhab/addons/org.openhab.binding.tapocontrol-4.1.0-20231127.032506-101.jar
openhab>

Many thanks for any hints

Bigdesaster · November 27, 2023, 5:37pm

Just download the right jar from my “OH-Compiled-Addons” repository linked in the first entry of this thread.
I think the jfrog is the unmerged version.

stefan13 · November 27, 2023, 6:43pm

thanks a lot Chris - I missed this linked
Its working now

ChristianHupfer · December 2, 2023, 6:47am

Thanks a lot also from me to you, Chris

This issue with the new firmware and protocol style for Tapo bulbs troubled me for about three months by now.

The suggested solution works out of the box, but I had to remove the original Tapo binding first, then save the org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT in the addons folder, restart the openhab service.
(I installed it on a Raspberry Pi 4, current version is 4.1.0.M3)

After reloading the bulbs can be controlled again from within OpenHab.

Dadobam · December 5, 2023, 2:47pm

Saving org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT` in the addons folder and clearing cache and removing binding and restarting etc etc didn’t work for me. Still got errors 1111 and handshake error.
After removing the Tapo device (L510) in the official app Tapo and adding the same device again it worked.

tebraxin · December 5, 2023, 8:48pm

Also for me still have the error :


2023-12-05 21:46:59.230 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'tapocontrol:P105:accountTapoCLoud:PresaTapo1' changed from OFFLINE (COMMUNICATION_ERROR): login failed (1111) to UNKNOWN: login failed (1111)

thanks

nelson.aponte · December 6, 2023, 10:37am

My Tapo P115 smart plugs finally reported yesterday that there was a firmware update available. I updated them and then changed the connection to use the KLAP protocol (using the latest snapshot binding for OH 4.0.4). They worked right away!

Dadobam · December 6, 2023, 5:09pm

So maybe you can try to remove the Tapo device in the app Tapo. And then add it again. Worked for me.

tebraxin · December 7, 2023, 6:22pm

I always get the same situation :

Dadobam · December 9, 2023, 11:20am

This error (api error -1) I got when I still had the market place addon installed. So could it be something went wrong installing the third party addon? I made mistake to save org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT-sources.jar in the addon folder instead of org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT.jar. After installing third party addon correctly I got error 1001 or handshake error. Then I removed the Tapo device in the Tapo app and added it again. Then in Openhab click disable and then enable the Tapo thing

hyzteric · December 13, 2023, 9:44am

So I ran into the same issues of course but I wanted to clarify what did work exactly for me, hoping it will help others.
I am using file base configuration and running OH 4.0.4.

1 - Remove the TapoControl Binding from the Binding interface
2 - Download the latest snapshot “org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT.jar” from here oh3_compiled-addons/ at tapocontrol · wildcs/oh3_compiled-addons · GitHub
3 - Put that file /usr/share/openhab/addons/
4 - Set file permission : sudo chown openhab:openhab /usr/share/openhab/addons/org.openhab.binding.tapocontrol-4.0.4-SNAPSHOT.jar
5 - Stop openhab : sudo service openhab stop
6 - Clean cache (just in case) : sudo openhab-cli clean-cache
7 - Start openhab : sudo service openhab start
8 - Add the KLAP protocol in my configuration file (which is under advanced settings if not using files)
My configuration looks like this :
tapo.things (note that KLAP is all uppercase and it did not want to work with lowercase as seen in previous posts) :

Bridge tapocontrol:bridge:myTapoBridge “Cloud-Login” [ username=“xxxx”, password=“xxxx” ] {
Thing P110 p110SV06 “Sovol SV06” [ ipAddress=“192.168.0.9”, pollingInterval=30, protocol=“KLAP” ]
}

I had to update my tapo.items too as the channel changed (I had to add “myTapoBridge”) :

Switch TAPO_SV06 “Sovol SV06” {channel=“tapocontrol:P110:myTapoBridge:p110SV06:actuator#output”}
Number TAPO_SV06_Power “[%.2f W]” {channel=“tapocontrol:P110:myTapoBridge:p110SV06:energy#actualPower”}

I did get some error upon restarting but it did clear up automatically.
If your devices are not using the latest firmware you may have some issues too. Before doing this, I only had one device still working (the one not automatically updated). After that, it was the only one that failed. It did work immediately after a manual firmware update.

Hope it helps.