Thanks, Kevin! However, this sounds to me like it’s absolutely about UX. Measuring what’s “Always On” could just be a simple min over time, but like you said, this could potentially be misleading for temporary drops depending on the user.
For me personally, I would want it to drop immediately if I flipped a breaker and then gradually rise again over some “short” period of time. That is reasonable to me. I wouldn’t want it to drop though if Sense missed a measurement. It should be able to differentiate between the absence of a value and a value of 0.
I guess I wouldn’t even have this confusion if it was called “Usually On” instead of “Always On”…not that I actually want that. Just trying to understand the rationale behind the current behavior.
For the screenshot above, I suppose my ideal behavior would be to drop to 73W and then follow the current wattage until it climbs back up to 86W (or whatever the calculated Always On was at that time) and then display that instead.