If “Currently Learning” is the list of mystery / motor / heat / named devices that I haven’t acknowledged yet, I would describe it as possessing excessive enthusiasm and a good imagination, a few weeks in.
I wonder if step one in sorting it out would be to put some checks in place that would reject new devices that fail some obvious tests. My experience in offering users software functionality is that, if found to be flaky on introduction to real users, remove it rather than leave it offering misleading information while being worked. Often that is not easy, but in this case I think use cases for certain devices could be written that eliminates some of the “noise”.
example I’ve just had my water heater identified. Consumption is 10W, which isn’t a water heater of course and we have a gas water heater. I do have a pseudo water heater as part of my humdifier (discussing lack of detection with Support off-line) but it has a very distinct sawtooth resistive trend which would not fit the pattern of a typical water heater.
I’ve just had a 10W Motor 2 identified this evening, which has been running for approx 25 mins. Feels like it’s in the noise. Even if there was a credible 10W motor detection, could loads below ??? be suppressed for some significant time or until a user had flagged that a primary list of loads had been detected.
Sense is a fabulous tool, isn’t it?