Technically, there is no “Kasa Binding”. There’s the “TP-Link Smarthome Binding” (created before TP-Link bought the Tapo product line), the “TapoControl Binding” (created after the purchase), and also a “TapoCamera Binding”.
So…it’s already confusing for new openHAB users (I’ve had to explain this to a few people). When I posted that link earlier, it was just to note that TP-Link’s recent changes are going to add to this confusion. If a new OH user buys a Kasa device and then sets it up with the Tapo app, which binding should they choose?
As a result, the question we probably need to start with now is, “how did you set up the device?” I can think of 5-6 answers, because TP-Link also sells Matter devices in the Kasa and Tapo product lines (none of which will work in OH at this time, as far as I’m aware).
This brings me back to:
OH is eventually going to have to make changes to reflect the reality that TP-Link prefers. It might be sensible to mark the “TP-Link Smarthome Binding” as a legacy binding, while expanding/renaming the “TapoControl Binding” to manage both Kasa and Tapo devices. Basically, have the bindings reflect the apps used to control the devices, not the branding on the boxes. But this is just speculation, since I’m not a developer.
Anyway, since you have a device that appears to use the Tapo protocol, it seemed like it might be a good way to add support for your KS240 working natively in openHAB. Even more so, now that I know you’ve already set it up in the Tapo app.
If “this guy” refers to me, note that there was a correction in the linked article from The Verge.
I didn’t re-read the article when I made my previous comment, so I was under the wrong impression when I wrote:
I’ll edit my comment to correct this.