I understand that. If I would understand how binding works in OH, I would tried to help you on that matter. I tried reading the doc but my head just keep spinning to understand how stuff work. I have over 80 devices at home so I could help expand the binding
The 9009 error is generated by a firewall blocking a port. Currently investigating this.
Have tou tried to allow third party compatibility in tapo app? And also setting “things” to klap protocol on port 80?
1 Like
Yes it is activated and the problem appeared once I started to set FW rules on the Proxmox datacenter, nodes and VM. This is related to the way JVM ‘emulates’ pings. The solution for me was to give JVM needed (see comment here : Single Tapo P100 not working, another works fine, both work with app - #4 by glhopital )
The device I have that I must go though HA isn’t supported since it’s a special device with child device. It require a special setting because it control both a fan with 3 speeds and a light with 0-100% brightness level. I have a lot of kasa devices and some tapo devices that I would love to unifi under one binding (specially since the tp-link binding doesn’t get any dev anymore and new device need tapo authentication that aren’t supported by tp link binding).
It seems that a lot of this thread is about Tapo but I only use regular Kasa. I’m using a Kasa KP200 and it would not connect until I turned on Third Party Compatibility switch. The strange thing to me is that I have other KP200 that I installed in the past and they work fine. Thanks for this!
well, it was already mentionned 4 reply just above yours… It’s not new though, I’ve had that tick at least the last 2 years.
Guess I don’t know the difference between “Kasa” and “Tapo Kasa”. Don’t see any post that doesn’t mention Tapo. But thanks for the help.
The post does say “in tapo app” not kasa. There’s is no Tapo Kasa.
TP-Link does 2 line of device, Kasa and Tapo.
Tapo is the new line that use a different communication protocol. This binding (tapocontrol) use that.
For older Kasa device, we use TP-Link Binding. Problem is that binding is not supported anymore (no dev) and it got to a point where new version of current Kasa device and new Kasa device now use the same communication protocol then Tapo. That’s why we started asking if we could merge both of them into a single one.
On android and iphone, it’s also 2 different apps, Tapo and Kasa.
I have another set devices under tapo branding, tapo cameras. Will this be supported? I am currently using home assistant for it.
I can agree, the switch to enable third party in the TAPO app is set to enable, my TAPO P110 device with firmware 1.4.0 is switching between Online and offline (HTTP 9001). some minutes online, then offline and after while back to online.
Another P110 with firmware 1.3.1 works without any problem.
Looks like that firmware 1.4.0 brings some communication problems.
I had working Kasa KP200 outlets with the TP-Link binding, until I updated their firmware to 1.1.0. All the Kasa devices stopped working after the firmware updated. That is when I discovered TAPO. The TAPO app supports both Kasa and TAPO devices. Upgraded to OpenHAB 5.0.3, but still no luck with either the TP-Link or TapoControl binding. Saw the post from @sn49750, and turned on the Third Party Compatibility switch and the Kasa KP200 outlets were once again available and function from the TP-Link binding. To enable Third Party Compatibility, I did it in the Kasa app. It has a switch for Third Party Compatibility in general, which speak specifically about third party integrations like HomeAssistant.
Hi, @glhopital.
Have you discovered how to fix this issue? I updated the firmware of my Tapo devices and OH can no longer connect to them, even though the Tapo Cloud is online.
No @nelson.aponte , issue is not fixed. For me also Tapo Cloud is online and 2 of my 3 P300 online, the third offline.
I’m seeing this with some P110M smart plugs and firmware 1.4.1 - I’ll try look into it when I get some time.
I fixed my P110M by turning 3rd party compatibility off, then back on again.
Same for me. I don’t know what I did differently this morning. Now back online.
I wasn’t aware of this new feature on the Tapo app. I enabled it, and my devices are back online on OH! Thanks a million, @Paul_Smedley and @glhopital!
1 Like
I’ll raise a PR to update the README.md
Yesterday I found one of my P105 not connected to openhab all of a sudden. I figured out that, for some unknown reason, automatic update was turned on (not sure if triggered by someone in the family) and firmware was updated to
1.4.0 Build 250901 Rel175625
Turning third party compatibility on in the tapo app made the p105 reachable again.