Seems like a sensible approach. I have my two entertainment clusters and my home gateway cluster (modem, router, main switch, plus a couple of bridge devices) on HS300s that have 6 separate plugs, but haven’t really gotten much marginal value from separating all of them. The gateway cluster HS300 is fed by a UPS. The downstairs entertainment cluster was occasionally sucking enough power through the HS300, that I had to put the Yamaha receiver on a separate HS110.(KP115 / KP125 equivalent). I also have a laptop / monitor / hard drives cluster that is connected to a UPS plugged into an HS110.
If I had to do it over, I would have avoided the HS300s, and just measured combined usage for each cluster.
I definitely do recommend you do that, NOT an HS300. When I researched that, the extra detail of knowing what some 20-30 watt devices were drawing provided no value in my home energy management (wasn’t going to be shutting off things like my modem regardless) and the extra cost for little value simply made no “sense”.
Your plan is a good one, and that’s almost exactly what I do.
I like combining the single smart plug with a “master switched” power strip. These power strips automatically turn off accessories like computer monitors and speakers when the computer turns off. This helps cut down your “always on” usage.
I’m assuming you mean that you have configured the plugs via the Kasa app to be attached to your network and visible in the Kasa app ?
You’ll next need to make sure the TP Link integration is turned on under Settings > My Home > Connected Devices
Once that happens the plugs should show up as devices in a few minutes.
A few more pointers:
The Sense monitor typically has to be on the same subnet as the plugs. They talk via broadcasts on the subnet.
Various folks with various types of networks have noticed that the Kasa devices can sometimes experience dropout, when the Kasa plug stops talking to the Sense monitor for some period of time. We haven’t resolved what’s happening, but it seems more related to networking/plug interactions vs Sense.
Thanks, that is what I was looking for.
When I enabled that in sense, it stated it should start to see the plugs in 5-10 mins.
Note: 6 of the 8 are active (2 are configured but not plugged in yet)
Pointer #3 - the Other bubble should drop in size by the amount the new plugs are detecting since it’s a simple subtraction.:
Other = Total Usage - sum(all detected usage)
Always On is a very different bird since it is a statistical calculation using data collected over the past 48 hours. After your plugs have been going for 24 hours or so, Sense will give you Always On values for each plug so you can reduce the size of the unknown component of you house-level Always On.