One other challenge I’m seeing with Sense for IDing AC units is premature off-detection when the AC is running for long periods. Here’s a timeline that blends data from my Sense and from my Ecobee from yesterday. We’re in the middle of a NorCal heat wave - 90 degree temps. My upstairs HVAC (using smaller units than I included in the last post) was running all of yesterday from about 9:30AM onward thanks to the Ecobee commands for continuous cooling (Up_Cool column - 3600 secs / hour of cooling in red). AC2 is the Sense reported hourly energy consumption for my upstairs unit (in blue) and FurnaceUp is the Sense/HS110 reported energy consumption for the upstairs furnace fan (in green). By the looks of the power usage it looks like the furnace controller might have inserted some brief fan, and possibly compressor, breaks around 6 or 7 PM. And either Sense got bored (timed-out) or got confused by a brief break at that time and treated it as an off-signature with no subsequent on (the Sense detected power drops to zero, even though the Ecobee is still calling for cooling)
The good news is that I can see exactly what happened with the furnace fan, since it is on an HS110. It looks like the power reduction was more of a dip, than even a brief off.
So I’m guessing that Sense eventually timed out thinking my compressor couldn’t have been on that long. Of course, that’s speculation since I only have Sense’s view to go by.
I might be able to investigate this a little more by looking for extra “Other” showing up after about 6:15 PM.