I have a problem with TAPO P100 after firmware upgrade and operate for many devices on OH3.4.5, The 4.0 SNAPHOT is not working with older OH. Is it possible to compile the *.jar file for OH3.4.5?
Uploaded a new 4.1 Snapshot (and only 4.1 at the moment).
Binding is now supporting Device-Discovery in loacal network via udp.
Online discovered devices will set and ip-address protocol themself.
@Tomasz_W
Sorry i have no time to support older versions at the moment.
@Bigdesaster Chris, no problem. I solved the problem using P110 instead of P100. The newest firmware version of P110 - 1.2.3 Build 230425 Rel.142542 - does not create the connection problem.
Uploaded jar with UDP-Discovery for OH-4.0-Version.
@Tomasz_W
Nice if this is fine for you. But maybe it’s better to switch off auto-firmware-update for your P110. Tapo was updating a lot of different devices in the last weeks becaus old protocol may have a security bug.
@Bigdesaster Chris - yes, indeed, i did so for my 4x P110 Plugs.
Thank you!
Hello, would it be possible to add the L31 bulb among the compatible devices, which I understand is almost identical to the L610 which is already working? In case, if I can be helpful, I can provide the logs for both the L31 and (possibly) the T100 smart motion sensor .
Thank you very much for your valuable contribution
L31 should be possible, need a tracelog. should be possible to choose a different thing-type and set ip of L31 to get needed data.
T100 may be difficult. Hub is polled every x seconds and motion event may be not at this moment.
Hi,
I’m facing issue with my L900. It’s thing shows a COMMUNICATION_ERROR with error message unknown api error (-1)
Via Tapo App the lightstrip is usable. I already removed the thing and re-registered it without changed behavior. I’m using openHAB 4.1.0.M3, but faced the issue already with major release.
Can someone help or at least confirm the issue?
Did you use the jar from my oh-compiled-addons?
Maybe protocol for L900 was changed by Tapo already. The new protocol fix isn’t already merged today
Grazie mille per l’aiuto.
Thank you so much for your help.
I tried to set the TL31 device as if it were an L610 (i.e. with the IP of the TL31). When saving the configuration, I get the error message “COMMUNICATION_ERROR login failed (1111)”.
After activating the TRACE mode for tapocontrol, I simply get as a tracelog:
"19:19:03.014 [DEBUG] [trol.internal.api.TapoDeviceConnector] - (tapocontrol:L610:2798b176c7:a77e9cdc01 / DeviceConnector) exception while login '@text/error-api-login-failed [ "1111" ]'
19:19:03.015 [DEBUG] [trol.internal.api.TapoDeviceConnector] - (tapocontrol:L610:2798b176c7:a77e9cdc01 / DeviceConnector) handle error '@text/error-api-login-failed [ "1111" ]'
19:19:03.017 [DEBUG] [al.devices.wifi.TapoBaseDeviceHandler] - (tapocontrol:L610:2798b176c7:a77e9cdc01) startScheduler: create job with interval : 30 SECONDS
19:19:03.018 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'tapocontrol:L610:2798b176c7:a77e9cdc01' changed from UNKNOWN to UNKNOWN: login failed (1111)
19:19:03.020 [INFO ] [hab.event.ThingStatusInfoChangedEvent] - Thing 'tapocontrol:L610:2798b176c7:a77e9cdc01' changed from UNKNOWN: login failed (1111) to OFFLINE (COMMUNICATION_ERROR): login failed (1111)
"
What can I do to generate a more useful tracelog?
Thank you very much
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.
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
Any idea, when this will be merged?
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
1 Like
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!
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).
https://github.com/mihai-dinculescu/tapo
No integration ist only available for OH4.
OH3 is not implemented.
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
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! 
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.
2 Likes