Based on some other threads about Always On power now that we have Smart Plug integrations…
My question is:
What does everyone expect from Always On now that we can identify some of that Always On power.
Always On historically is “the low water mark”. Now that we have a way to identify Always On devices, do we need a new way to view Always On? Is it the lower water mark? Or only the low water mark of unidentified power, which means it isn’t actually all of the Always on power.
If we can identify Always On power, does that mean that Always On should go down? It is still Always on, but it is just identified. If we leave it as it is now, where the always on Bubble contains the always on number, but the smart plug which is catching some of the Always On power, we get bubbles that don’t add up to actual consumption because things are effectively counted twice. Do we now need more bubbles? Always On (Unidentified) and then an Always On Bubble per smart plug if Sense is able to calculate a lower water mark per plug. Then an additional bubble for the variable power from that smart plug above and beyond what it has detected as the lower water mark per plug?
Obviously its personal preference, but I sort of feel that no matter what, I always want “Always On” to represent the lower water mark for the entire house. Regardless of if I know what some of that always on power is. Otherwise I don’t have a quick way to look at that low water mark. The “two bubbles” idea above will just get clunky and I don’t actually like it, but was just tossing it out there as an idea.
I’m now more thinking that we need an Always on “bubble” for the bubble display. But then under Usage, we have two “Always On”'s lines. One for identified and one for Unidentified usage. For visual representation, we can see both. But for data export, and calculation purposes, it only adds the “Unidentified” always on when summing usage.
I know that it means that on the bubble display screen that you can’t add up the power on all the bubbles and expect it to match the live usage, but that sort of happens already because Always On is not live updating.
I think i’m talking in circles, but wanted to get a conversation going about it as I think its much more complicated from a UI/UX and data analysis perspective than it seems.