Does this work with the new plugs such as P110?

[andylamp]

I am not sure if this has been tested but since Kasa plugs are mostly discontinued, do you know if this is compatible with P110 plugs which are the new "replacements"? This is not available in all regions and I used one that I could find that has the full specs.

[candlerb]

Don't know about the P110, but I found a project here which says the fffonion/tplink-plug-exporter works with HS110 plugs.

[andylamp]

@candlerb, well... obviously... that is my project... It does work with any Kasa based Plugs (which both KP115 and HS110 are). P110 plugs are based on Tapo not Kasa, hence my question.

All evidence points that they are not compatible, unfortunately, but have not personally tested them.

[candlerb]

that is my project...

Oops, sorry about that, didn't check the username! :-)

I had ordered a Kasa Slim but have just cancelled it, after reading on #12 (comment) about the Kasa plugs auto-updating their firmwares to become effectively Tapos. I'm in the UK, and the suggestion is that the UK models are affected by this.

[fffonion]

Hi @andylamp , thanks for the update. I haven't been using this project since the pandemic, as I don't have access to those hardwares anymore. But I will be happy to add support to Tapo if you could point me to any existing work (more preferably if it's proved working on your P110 hardware).

[andylamp]

@fffonion thanks for the reply! Unfortunately, I do not yet own P110 but there have been projects trying to reverse the protocol used (see here and here). It seems to be quite different than the one Kasa uses (see here and here for a more lengthy discussion).

I am going to buy a bunch of P110 in due course to replace (and expand) my HS110's as I would love monitoring over my whole house and, while awesome, the HS110's are not being made anymore. Thus, any replacements or additions will be not possible. To port this exporter to P110 (or more concisely, to the Tapo API) I would expect to require some work on the exporter. I was planning (before committing to the plugs) to do that myself, but have not (yet) gotten around to do so...

[brazune]

I have a Tapo P110 and, because I needed to learn kubernetes, prometheus and grafana, though it would be a good way to try it in a "real world" scenario. All the deployment (and learning) went fine just to discover that the exporter was unable to talk to the P110.
A full UDP/TCP port scan reveals that only tcp/80 is opened.
I've tried to simply recompile kasa.go to use port 80, but, as expected, doesn't work.

[Jakob-Eichberger]

Since im currently in the same situation as @andylamp I decided to read into this a bit more. Turns out this exporter does not support any tapo products since their API is completely different then the API for KASA products. Tapo uses AES encrypted payloads whereas the Kasa products do (as far as I'm aware) not.

You can read more about it on the home-assistant forum.

@ fishbigger thankfully created a phyton library for Tapo Devices. From what I've read this python plugin should be able to query states and energy consumption (as well as control them) from different TAPO devices (I've seen confirmations for P115, and P110 devices)

@fffonion I'm sadly not familiar enough with golang to create a pull request with support for tapo devices. Any chance you could add support for tapo devices? I would highly appreciate it!

[RedFirebreak]

Update: Been using this project for quite some time using my HS110 devices. Just got my hands on the P110 and P115 and I can confirm that they are NOT compatible as of now.

[Night1]

as @RedFirebreak said they do not work with Tado plugs , does not look like a trival task to do since they changed must of the backend of these plugs if i would have known this i would not have bought these plugs.

I got it working by combing this and https://github.com/FergusInLondon/Tapo-P110-Prometheus-Exporter and doing some magic with grafana not all tags are the same but still easiest way to do get data.