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!
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
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) :
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.
I have this response in log: ==> /var/log/openhab/openhab.log <==
2023-12-14 22:36:24.920 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model ‘Tapo.things’
2023-12-14 22:36:24.926 [WARN ] [el.core.internal.ModelRepositoryImpl] - Configuration model ‘Tapo.things’ has errors, therefore ignoring it: [5,159]: no viable alternative at input ‘“’
Please can I check if the Smart Contact Sensor (T110) is supported by this binding?
I have one of these T110 sensors but I cannot get it to work (it has no IP address on my network and seems to communicate through the hub so is it expected to work with this binding?)
If I try to add a Thing manually it doesn’t seem to pick up the bridge…
Note I have a number of Tapo bulbs which are working well with this binding
@hayta78
Maybe the path on ubuntu is another. check how to install bindings manually for your system and use the correct version of the binding.
@SteveBuckell
T110 should be discovered by the hub automaticly…
So if the hub is working and it should come into inbox. If you ad it manually you need to configure the hub as bridge.
@Wyskens
Fix will be applied if the PR will be merged.
Just updated from OH 4.1.0M4 to final OH 4.1.0.
I removed the 4.1.0 SNAPSHOT.jar from add-on folder which fix the Secured KLAP HTTP Protocol issue in 4.1.0M4.
I assumed in final 4.1.0 this fix is included but after upgrade and reinstalled the original 4.1.0 binding, this feature disappeared again
Did I miss anything ?
I have the same issue after upgrade to OH4.1 and add this binding (copy it into the add-on folder like described on github).
Problem is that the add-on from the add-on package is registered in OH. Do following steps :
sudo openhab-cli console
… enter the password of the openhab account - mostly habopen
list -s
… search for the tado add-on and the id-number in front of the entry
bundle:uninstall xxx
… xxx is the id number
logout