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

Bigdesaster · November 7, 2023, 6:34am

Did you try both protocols in advanced settings?
Orherwise i have to Upload a Special jar with universal device thing. But this week i’m away.

saxxing · November 7, 2023, 2:49pm

Hi, I tried using the KLAP protocol and the login error disappeared. In addition, the LT31 bulb used with the L610 configuration already works correctly (both on/off, and the dimmer). Only the consumption reading functionality would be missing, but honestly it is secondary. However, I suggest adding the LT31 to the operating devices with the binding. They are available in case for testing or other. Thank you very much

NoOpenHab · November 14, 2023, 5:54am

Any idea, when this will be merged?

Bigdesaster · November 14, 2023, 7:16am

PR#15725 was already created. One more reviewer must confirm this and merge it into main.
I hope it will be merged until release of OH4.1

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!