Well, that’s interesting at a purely academic level, but no matter what the math is behind it, the “Now” screen is still off by thousands of watts. And not to be argumentative, but I had the whole thing shut down for half an hour one day, and that did nothing to the Always On number, so maybe that’s how it’s supposed to work, but that’s not how it’s actually working.
Sense is a cool idea, but in my experience over the past few years, the reality isn’t nearly as cool as the idea. There are too many system outages. The Sense device has awful Wi-Fi sensitivity on 2.4 GHz, and it can’t do 5 GHz at all. I had to install a dedicated access point just to keep the Sense device from locking up every time it lost the WiFi connection. In a place where any other device can manage 50 Mbps on 2.4 Sense also can’t do WPA3. There are gaps in the data, potentially related to the system outages. In my particular case, there are dozens of devices, amounting to thousands of watts, that are not being tracked anywhere in the app. The interface on a real computer is inferior to the mobile app, and the mobile app isn’t that great. It just seems like a crowd-funded project that never was quite finished.
Putting aside most of the problems above, if anyone were to ask me, I would tell them that the Now screen should be dedicated to things happening in the present tense. I would tell them to put “Always On” somewhere else (anywhere else!), and then make the rest of the bubbles add up to the current power consumption. Pretty simple concept, really: Now is now. I don’t object to the idea of an Always On calculation, as long as it’s not on the Now screen.
When I first got the Sense device, I had the feeling that Sense was a work in progress. I was really looking forward to all the great things to come. Two years later, I’m pretty well convinced that the work is no longer in progress, and my confidence in those great things to come is very low. I fear that what you see is all you’ll ever get. If Sense had developers actively working on the software, glitches would be fixed in hours or days. I mean, bad math is a simple fix. I can’t see that anything has ever been fixed. I used to do software development for CAD, and I quite often added multiple new features in a single day. Bugs were fixed in minutes, not days, weeks, months or years. That’s what active software development looks like.
Does this seen negative? I’m sorry, but I feel negative about it. We can go back and forth in this forum, and at some level I would enjoy the conversation with you, but I honestly don’t believe that anything that I say here is going to result in changes for the better. I’m just venting on you (which I don’t want to do) because there is no way to communicate with the development team, if indeed there actually is such a team. I noticed that the firmware version changed, but I can’t see that it made any difference. And there is no published changelog or release notes, so who knows?