Have both Tapo P110M and Kasa KP125M on the latest firmware connected to Hubitat via Matter. The P110M firmware definitely supports Matter 1.3 and energy monitoring, I think the KP125M does too.
I can see energy info in the Tapo mobile app.
This post from Feb 21 says that Hubitat supports Matter 1.3.
I'm using the Generic Matter Outlet, which allows me turn power on and off, but I don't see any energy information.
The Generic Matter Outlet will parse this data if available. Do you know that your device actually sends this data over Matter? (Just because the device can do it doesn't mean the manufacturer chose to expose it over Matter.) If you don't see "0B04" under "inClusters" in the "Device Data" table (on the "Device Info" tab of the device detail page for the device), it doesn't.
If you've had the device paired for a while and did a firmware upgrade or something on the device that may have changed things since then, a re-pair might help. But it's ultimately dependent on the above, whether the manufacturer actually does this.
Home Assistant forums show they are able to get the energy monitoring data via Matter with the latest firmware, so I'm assuming the devices actually can send it.
I do not see "0B04" under inClusters. However, I'm not seeing this listed on any of my other plugs that do provide that info --though those are all zwave and not Matter.
Did you remove and re-pair the device or just re-pair? I'm not sure the latter will be enough for it to "see" the new cluster.
Do you see "0B04" listed under "inClusters" in the "Device Data" table on the "Device Info" tab of the device detail page? Does debug logging show anything if you have it enabled when you think a power (not energy -- I don't see that anywhere) reading should come in, especially anything with "0B04" in it?
Just done this exercise now on a separate but identical socket -> the result is the same, no power reading using the Matter Generic Outlet" driver
Steps followed: Removed the socket from the Matter commissioning hub, re-paired again, then used the Matter code to add to Hubitat and selected "Matter Generic Outlet".
After waiting several minutes and observing the exact like behaviour, I then deleted all states using "device" driver, then switched to the community driver.. the power readings are present again.
Yes, power is being reported on cluster 0x0090 in your Advanced Matter Bridge driver, but not your "Matter Advanced Outlet" and "Generic Matter Outlet" system driver.
Hopefully, this will be fixed soon in the HE system driver.
I do not plan to further develop my Matter drivers, as Matter is a well-defined standard protocol, and it makes no sense to duplicate existing work.
Thank you! Mike is going to look into this tomorrow. I think 0B04 (I read the driver and rolled with this...) got carried over from Zigbee, so it should be a simple fix.
It's still odd that this cluster still doesn't appear in the clusters list, but that could depend on when the device was paired, so I guess whether it works is the real question...
Ok so my newly acquired Tapo P110M matter plug should show energy soon then without me having to use a community driver? It doesn't at the moment with the latest firmware (matter 1.3).
Edit: I see a power state. How did I miss that before.