I’ve noticed that all my long-running natively detected devices have a flat “tail.” A sample detection is included below for the motor in my dehumidifier, which ran three times last night. I believe that the AI engine in the Sense mainframe, when it detects a new device, assigns it a wave-form pattern (probably based on the average of the instances it analyzed). From that point onward, each time the local Sense monitor notices a certain device come on, it displays that waveform as the device consumption.
Notice how the waveform pattern at the beginning of each ON instance are exactly the same shape. I believe the waveform pattern definition has a maximum file size, so for long-running devices, when the time frame included in the defined waveform has elapsed, the Sense app displays a constant value. This does not
mean that the device now has a constant electrical demand. It is merely the limits of the interface technology.
Do I believe that my dehumidifier wattage actually stabilizes at a constant value after running for 20 minutes? No. In fact, in a few of my devices that have native detection behind an HS300, I have seen the integration continue to report zig-zags after the native definition has leveled off. I can’t put my finger on an example at this moment, but I have seen it multiple times.
Conclusion: Motor 2 probably does not have a constant usage of 280 Watts throughout the day.