TP-Link Tapo P110

Hello @nayelyz
I bought a Tapo P110 outlet with energy metering.

In the “Explore” tab, in the “Easily Save Energy” sector, this model appears as being compatible…

But inside the device does not show the energy consumption is it anyway?
Can I only see consumption in the Energy app?

Thanks


Hi, @Helder_Rodrigues
I checked the profile used by this device and indeed, the only capability that will appear in the Detail View is “Switch”.
The one that saves the information on the power consumption is “powerConsumptionReport” but it doesn’t have a presentation, which indicates how it should be shown in the app (Detail, Routine, and Dashboard view).

You could check in the Advanced Users’ app > Devices if the value of its attribute is shown there. I see the attribute (“powerConsumption”) is a compound of several properties, so, I don’t know if it will be presented correctly there.
However, you should be able to see the current value in JSON format if you use the SmartThings CLI with the command below:

smartthings devices:status deviceID -j

Please, let me know if you have any questions.

Hello again

This is what appears!

the full text
{“start”:“2023-08-30T00:11:00.645Z”,“end”:“2023-08-30T00:26:00.645Z”,“energy”:1311,“deltaEnergy”:490}

Do you think it’s possible for you to make it appear like it does on other devices?

What do you mean by “like it does on other devices”?
For example:

  1. Are you referring to the other capabilities that are called “powerMeter” or “energyMeter” where you can see the current measurement?
  2. You want to see that value shown in the detail view as other capabilities appear like “switch”

In both cases, it would be difficult to do so:

  1. If you’re referring to adding another capability to the integration, the task would correspond to the partner (TP-Link). Do you see if this device is controlled by a driver or if it has a type of “VIPER” in the Advanced Users’ app?
  2. In this second case, it depends on the engineering team because they have to develop the presentation and decide how to display that data in the app (detail view of the device). But, it depends on the purpose they have given to this capability (internal data/display data)

Hello.
I’m talking about something like that!

What appears in the device settings is this!

Do you think it’s possible?

Thanks for the screen capture of the details. As it is typed “VIPER”, it corresponds to a Cloud-Connected integration.
This means only TP-Link can make the change, if it was a Zigbee or Z-Wave device, you could have made your own integration (assuming the device supported those measurements).
As that’s not the case, for you to get more information about whether it’s possible to add those capabilities to this device, you need to contact the support team of TP-Link and ask for that feature.

Thanks me for the help :grinning:

Yes, I’ll try… I don’t miss anything either! :grinning:

@Helder_Rodrigues, were you able to get this working, to display energy information within SmartThings for the Tapo P110 plug, maybe through Edge drivers?

I have it working with a Kasa KP115 plug, but seems the Tapo P110 is easier (and cheaper) to get hold of, however, there doesn’t seem to be any edge drivers (for Tapo P110) that display the energy information inside of SmartThings, which is what I need for a routine.

Both Tapo and Kasa are owned by TP-Link.

Hello.
I also have P110 plugs and yes, that are integrated on ST Energy, but we can’t see the Power Consumption as a capability.
I would like to access it so that I can make automations based on the real time power consumption. I understand what you explained, that TP-Link should add this capability to the device (so far they haven’t).

But my question is: Why is the power consumption available on the Home Assistant integration??? I don’t use it, but I read about it, and they can access it :face_with_raised_eyebrow:

How ?!?!?

Let’s hope TP-Link will resolve this…

TP-Link does not offer any integration for Home Assistant so some users reverse-engineered the proprietary local protocol it uses to communicate with the Tapo app and get the measurements like if HA was the Tapo app.

While that could be doable as a custom driver in SmartThings I don’t think anyone is willing to waste effort there, especially since the P110M is going to get Matter 1.3 support soon and will report both power and energy to SmartThings in a standardized way.

As for why TP-Link does not offer that option in the cloud integration, it would be a waste of their cloud resources constantly sending messages to all smart home platforms integrated. SmartThings Energy only requires one report every 15 minutes.

1 Like

So if I buy 1 P110M now, with no support for Matter 1.3, later when TP-Link adds the support, my plug will get that support, right?
Maybe it will need a firmware update, but will get that support?
Or they will launch a new plug to the market, and only that new plugs will get that Matter 1.3 support?

It’s a firmware update, it’s already certified by the CSA and should be arriving this month according to the official community thread discussing the issue. But, as always, I would wait till the firmware is released, you never know!

Mind the Matter integration is local and requires a SmartThings hub, unlike the P110.

Should you get it before, when the update arrives you’ll have to remove it from SmartThings and add it again since the stock Matter drivers are not designed to detect those changes and would still believe it has no power monitoring (I consider that a bug and the engineering team is aware).

2 Likes

Slightly off-topic: Just in this moment, my Eve Energy plugs are updating to firmware 3.5.0 (Matter 1.3).

I hope that they will still show up in SmartThings Energy.

1 Like

That is great!

But I was searching for Matter 1.3 and if I understood correctly, the V2 hub is not compatible with Matter 1.3 :pensive_face:

It supports Matter, but not the 1.3 version.

Am I correct?

Even if it’s not, it’s not important in this case since the driver for Matter smart plugs already includes the cluster definitions and handling code needed.

In fact, v2 is already updated to Matter 1.4, but again, doesn’t really matter since the drivers have backwards compatibility for older firmwares for hubs that don’t get frequent updates.

2 Likes

So you are saying I can use a P110M plug, even after the plug is updated to Matter 1.3, and will then have access to automations on Smartthings with options for real time power consumption??
And of course, still have it on the Energy panel…

If so, Great!! :grin:

Yes, just checked that my hub has the 1.4 Matter SDK.

A hub reboot should be enough, right?

No, the do_configure lifecycle only runs once when installing the device and that’s where they pick the profile with or without power and energy capabilities. If it’s already picked, it’s not going to change unless you remove it and add it again.

1 Like