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:
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
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!
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?
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" ]'
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.
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.
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.
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.