@mgguinne 

I can confirm this information. Update available in my tapo app. Updating via tapo app right now. After update in HA, reread device and voilaaaaa ! 😁

I was waiting for it to pop up in Home Assistant, but no such luck. Installed the Tapo app, added the devices and they updated immediately.

re interview in HASS and the power info is up and running.

it would appear it has always been counting, the counter has started at a random

number, so likely been running and counting just not reporting.

DoinitSideways wrote

so likely been running and counting just not reporting.

@DoinitSideways Yes, the plug stores the total energy (since the last factory reset I guess, haven't looked into that). It reported it via their proprietary protocol for the Tapo app and vendor-specific integrations, now it reports it with standard Matter 1.3 attributes.

By the way, there is a missing feature in the P110M via Matter, the power-on behaviour on start up. Tapo is aware because I told them in reddit, but the Matter attribute named "StartUpOnOff" to configure that behaviour is not implemented.

@Wayne-TP yes indeed. Home Assistant already supported Matter 1.3 (since June 2024) and so once the Tapo P110M firmware was upgraded, I re-paired then with the Home Assistant Matter controller and energy outputs appeared! 

There was a serious limitation was though, I could not update the Tapo P110M firmware OTA with Home Assistant, it said 1.0.0 was the latest. I had to resort to resetting the P110M, pairing using the Tapo app to upgrade the firmware, then re-pairing P110M with the Home Assistant Matter controller. That worked but is sub-optimal, because it means we can't use this Matter product without the proprietary Tapo app. @Wayne-TP is that something that could be improved in the future?

I wanted to say how much I've loving the TP-Link Matter products, apart from the P110M I have a bunch of the bulbs. I avoided TP-Link stuff before because it was proprietary cloud stuff. But with Matter products and ONVIF cameras, I'm buying a lot more Tapo stuff. I hope TP-Link will upgrade more products to Matter, like the power boards. Eventually I hope you'll implement Thread, because I'm not going to add 200 WiFi devices just to have Smart Lighting! A mesh network like Thread or Zigbee is a must!

Before upgrade (1.0.0) and after upgrade (1.3.0) below:

After resetting the Tapo P110M, upgrading the firmware with Tapo app, then re-pairing with Home Assistance Matter controller, the energy info immediately became available.

mocelet wrote

MarkCarline wrote

I have all 45x of my plugs

@MarkCarline I got the update already, I'm really curious about the performance of your SmartThings hub with 45 plugs reporting attributes every 10 seconds which is the rate Tapo went for instead of doing a smart reporting. For power and energy only that would be 540 reports per minute in total (45 x 2 x 6), or 1080 if you use my driver that also displays the voltage and current and updates at the same rate. That's between 9 and 18 reports per second in your case.

 

Edit: Fixed calculations, although that would be the worst case scenario with all plugs on and an active load in each.

  @mocelet 

Sorry, been crazy busy with other stuff so not had the chance yet to switch drivers on Smartthings so they report power but now wondering if that might be somthing to worry about.  Does this 10 second behavior also apply to HA ?  My HA is running on a Pi5 and its only using 1% CPU,

  @MarkCarline 

Does this 10 second behavior also apply to HA ?  My HA is running on a Pi5 and its only using 1% CPU

It's the same in HA, yes, and probably nothing to worry about. I'm just curious because I did a test once with a light that would send lots of reports while doing fades (transitions) and the hub struggled a bit adding some latency to everything, but it was around 200 per second, not 10 or 20, that should be a walk in the park even for the not so powerful (single-core?) ST hubs. Anyway, if you notice anything just let them know since they have room for optimization when it comes to handling power reports.

Edit: typo

I know this might be slightly off topic but since last night none of my TAPO plugs are working in SmartThings.  They are fine in HA.  I did happen to notice that there was a new SmartThings driver released (see red circle).  I wonder if anyone else here has noticed a similar issue?  I have reported it to SmartThings.

@MarkCarline 

MarkCarline wrote

I know this might be slightly off topic but since last night none of my TAPO plugs are working in SmartThings.  They are fine in HA.  I did happen to notice that there was a new SmartThings driver released (see red circle).  I wonder if anyone else here has noticed a similar issue?  I have reported it to SmartThings.

 

Was that after switching back from my driver? If that's the case, you've found a SmartThings firmware bug because I just tried that and the stock driver crashes:

"2025-08-05T09:51:18.933211073Z FATAL Matter Switch  runtime error: [string "cosock.lua"]:252: Unable to serialize datastore value: deserialize error: invalid type: integer `2`, expected a string key"

With my driver works fine though.

I would recommend you to restart the hub though, I have a theory related to the subscriptions that are not handled correctly when the driver is switched. Again, that's assuming the was a driver change.

  @mocelet nope, I haven't touched SmartThings at all (sorry been too busy). I tried restarting the Hub but no luck.

mocelet wrote

@MarkCarline 

MarkCarline wrote

I know this might be slightly off topic but since last night none of my TAPO plugs are working in SmartThings.  They are fine in HA.  I did happen to notice that there was a new SmartThings driver released (see red circle).  I wonder if anyone else here has noticed a similar issue?  I have reported it to SmartThings.

 

 

Was that after switching back from my driver? If that's the case, you've found a SmartThings firmware bug because I just tried that and the stock driver crashes:

 

"2025-08-05T09:51:18.933211073Z FATAL Matter Switch  runtime error: [string "cosock.lua"]:252: Unable to serialize datastore value: deserialize error: invalid type: integer `2`, expected a string key"

 

With my driver works fine though.

 

I would recommend you to restart the hub though, I have a theory related to the subscriptions that are not handled correctly when the driver is switched. Again, that's assuming the was a driver change.