Bad nomenclature on my part … was trying to convey the nature of the on ramping, i.e. the “ON cycle ends” meaning after 7 seconds of ramping the unit is at a 223W plateau and operating.
There are more dramatic examples but that was the very first activation of the unit and if by some miracle Sense was able to do native detection at that point you would assume, based upon what I understand of the realtime on/off chunks (“on” only in the case) that Sense ingests for the DSP, that it would be looking at at least 7 seconds of data.
This all speaks to the difficulty of realtime detection. As a thought experiment, it’s easy enough with the dedicated Sense to say, from the waveform, “my AC is on” but I was just playing around with the fan speeds and moving the vanes (tiny DC motors!) to see whether Sense would tag any of the wattage changes or, more importantly from a human vs Sense perspective, whether I could see those changes in the waveform and say something like “I turned up the fan”. Sense is definitely beating me on those little changes.
[Interesting: It’s as though some of the small motor loads are being absorbed by some capacitor charging. It’s very hard to see any load change in the waveform as I’m moving the vanes or changing fan speed. “Components” in modern devices, that one needs to detect, really starts to mean “components at the solid-state electronics level”, not just motors and such]