kevin1
July 16, 2019, 11:49pm
2
I did a long thought experiment on how to automatically classify smartplug device power usage in this history of postings.
Numerous visitors to this forum question “why it is so hard for Sense to see" an on or off pattern for a device in the Power Meter that is clearly visible to them. Or why does Sense have trouble figuring out when a smartplug device is in and “Off” state, vs. an “Idle” state vs. an “On/Active”. The gist of issue is that detecting patterns in the midst of noise and other patterns is a hard problem and the human brain and vision system are a very sophisticated piece of biologic hardware built for…
Just a caveat before I start “Installment 2” on this topic. I don’t profess to know how Sense actually does “Idle” vs. “On” detection nor do I have access to the fine-grained data they have to work with. But I want to share how one might do an assessment with the export data available.
Installment 2 - Data Science of “On”, “Off” and "Idle"
As I mentioned in the previous installment, the next important step is to figure out a density level for the second biggest maximum, or secondary mode if o…
Installment 3 - On and Off History for Furnaces
When I started looking at the energy histograms for my furnaces, especially my upstairs furnace, I noticed something a little funky. There seemed to be a few spikes on the low end of the graph, indicating multiple energy modes that all deserved attention.
[FurnaceUp]
But before I took the histogram at face value, I realized I would have to reckon with another challenge in defining energy modes - resolution mismatch. I remembered that my furnac…
Installment 4 - Revisiting ON/OFF with another month’s worth of smartplug data
I wanted to do one more round of analysis with:
Another month of data - my smartplugs first entered service at the start of November
Removal of most of my data dropout hours during the smart plug period - 382 partial hours removed.
Always On vs. power consumed by smartplug devices. Maybe not the smartest thing to look hour-by-hour since Always On adjusts over a far longer period, but I though this was interesting.…
I think I would rather have Sense do some kind of statistical clustering and allow us to assign names/states to the various clusters, where one user-assignable state would be Always On. The whole thresholding thing presumes just one breakpoint between two states. I would rather have Sense look for the real states.
Would appreciate your thoughts…
1 Like