They just have outdated information, both Home Assistant and SmartThings fully support smart plugs with Matter 1.3 energy reporting since early October. I guess they were not aware.
2 Likes
The good news in the Tapo forum thread is this part:
“Since the CSA Alliance released the Matter 1.3 standard in May 2024, TP-Link has been actively developing and certifying multiple Tapo models for Matter 1.3 functionality. As this is a new standard framework, adaptation will take some time. If all goes smoothly, we anticipate releasing firmware that supports Matter 1.3 by the end of 2024.”
1 Like
That’s indeed not Matter but a custom integration that periodically polls the plug using the proprietary TP-Link API.
The advantage of Matter, besides being a standard and not requiring TP-Link accounts, is that the plug can push meaningful changes in readings. If the vendor implements it correctly that means less latency in automations.
1 Like
Works for me on the 4 x power strip. Matter setup with home assistant only. Matter is on off only but tplink integration shows power consumption. Pain to be in 2 different spots but is showing
I am using both, the matter and the TP-Link integration but I don’t have a TP-Link Cloud Account. So the account fortunately seems to be optional for TP-Link integration as well but for sure I would prefer the Matter-only way.
It was optional for old devices / firmwares. According to the integration page not anymore:
If your device is a newer Kasa or Tapo device it will require your TP-Link cloud username and password to authenticate for local access. If you have an older device that does not currently require authentication, you may consider disabling automatic firmware updates to keep it that way.
You only need an account if you want to set up the device through the Tapo app.
If you set up WiFi via Matter or the Tapo API, you don’t need an account and still get updates, the integration works, etc…
See my post above: Tapo P110M Energy Monitoring - #27 by MrEbbinghaus
1 Like
Thats exactly what I did. I basically added the device using matter (the installation automatically poped up on my android phone with bluetooth enabled) and then used the IP I got from the matter device info to add it to the Tapo integration.
No account needed, but the integration says it has connection to the cloud so I am not sure if it works fully local or not.
The device contacts the tp-link servers to check for updates.
I just blocked its access to the internet.
Ya, TP def needs to update its Tapo, Kasa, and anything else they support Matter with in order for these options to function. As others have said, you can only get energy monitoring if integrated through their API and not matter. Even then, you can’t include this data within the energy tab or anything. It only shows daily or monthly available and won’t let you add those values. It needs raw data straight from the plug I guess.
So for now, if you want true energy monitoring with all of the perks of HA, then you should stick with Z-Wave or Zigbee. Zooz plugs are nice for this. Fibaro as well.
I am actually using it for the energy tab without problems, using the daily consumption entity. Home Assistant automatically adds them up so that you have a total consumption as well.
However, I would still prefer energy consumption with matter as you never know what TP-Link decides to do with it’s API.
Well that’s no fair. I have a total of four, and when I try to add either “Today’s consumption” value or monthly, it results in an error. Maybe I need to update HA as it could be a bug in the version I am using. I do know there is a x.2 update jump or something waiting for me in there. Just need to get back home to do it.
I’ve set them up in december and I didn’t notice any issue until now bit I ususlly skip the .0 releases
It’s coming:
Don’t mind the smart power strip title, the Product ID 0x0108 is the one of the P110M.
Cool!
Is anyone able to interpret the linked compliance document and understand whether the new version really includes energy monitoring?
Yes, I checked that before linking the certificate, it includes both energy and power measurement clusters.
What I’m curious about is the reporting rate and if they are being smart to notify meaninful changes like Matter spec recommends or just do periodic reporting (which translates in either automations having latency if the period is long or the network being flooded if it is very short).
How long does it typically take from certification to get pushed up? This is my first Matter device that supports DCL.
Tapo expects to release it within a month. Updates in Matter have been so scarce across vendors that I don’t think there’s even a typical time span.
I would not trust the firmware available in DCL though, assuming it’s even provided by Tapo, and instead would update with the Tapo app.
My understanding is that vendors like Tapo, WiZ or Meross, with cloud products that happen to be Matter compatible, certify “the Matter part” of the firmware (which has its own version), but the whole firmware of the device is another story and may includes fixes not present in what was certified.