Kasa EP25 is (also) working in Home Assistant including energy monitoring (however...) #803
-
|
I wanted to report similar success as #748. The EP25 plugs I mentioned back in November #548 are now (almost) fully functional (using HA/python-kasa versions noted below). One minor issue is the reporting of Total consumption. Also, I had some trouble getting these provisioned with the Kasa app, to make them available to HA/python-kasa. I've made some notes on that further below in 'Details' Regarding Total Consumption: Here's a screenshot of my plugs. The measurement for Total consumption is being reset and it appears to follow Today's consumption. As you can see here, Today's consumption and Total consumption are the same for each plug. I'm still working on understanding this and will update here on findings. But please let me know if I'm overlooking something here (hopefully it isn't embarrassingly obvious). 
EP25 by TP-Link Home Assistant: 2024.2.2 (HA -> Settings -> About) Details These details are unrelated to the consumption issue described above. This simply describes the trouble I had in setting these up in a restricted network. Ensure the versions of HA/python-kasa are as shown above. Temporarily disable any/all firewall rules, proxies, DNS redirection, etc. in the network where HA and Kasa plugs will be used.
For some reason using the QR code consistently failed. When adding these devices, keep a watch on DHCP and if the plugs are appearing in the chosen SSID. In my experience I'd see the Kasa app fail, the plug light would sustain blue (from orange-blue), yet the plug would become fully functional in HA. When one or more plugs are in the chosen network, run I wish I had something more clear and comprehensive to share. Just making these notes in the event someone is having similar issues. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Just wanted to give you a very quick but short answer related to emeter sensors, that issue is known and will be handled in the next release. The device doesn't report the data similarly than the earlier versions of the device, and there is no "total consumption (since reboot)" available anymore, so this sensor will be removed in the future. There are some new sensors available (consumption in the past 7 and past 30 days), that we might expose to homeassistant instead. This will all be part of the 0.7 release (pinned issue in this repository) and home-assistant/core#111151 which we are hoping to get done by for homeassistant's 2024.4 release, but we'll see :-) |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic. Thanks for the details @rytilahti ! |
Beta Was this translation helpful? Give feedback.
Just wanted to give you a very quick but short answer related to emeter sensors, that issue is known and will be handled in the next release. The device doesn't report the data similarly than the earlier versions of the device, and there is no "total consumption (since reboot)" available anymore, so this sensor will be removed in the future.
There are some new sensors available (consumption in the past 7 and past 30 days), that we might expose to homeassistant instead. This will all be part of the 0.7 release (pinned issue in this repository) and home-assistant/core#111151 which we are hoping to get done by for homeassistant's 2024.4 release, but we'll see :-)