Hey Jon, I’ve seen a few different places where you’ve said something similar to “if the runs are very short it’s possible they get filtered out to ensure only quality data is used for the profile”.
Can you explain that in a bit more detail? Are short runs not critical to the data set if that’s how the system is actually operating?
Would that make a (hypothetical) system that only runs for a few minutes at a time look like it never runs due to it all being filtered out?
Very short heating or cooling runs are generally filtered out of the profiling. When your system starts, there’s usually a period where stale air is blown out of the ducts or otherwise a brief period before the temperature stabilizes. Air in the home is also moving and mixing which generally creates a lot of instability.
In order to have more accurate profiles, beestat enforces a minimum run duration before it even considers a heating or cooling event for the profiling. This reduces a lot of noise.
So ultimately, an oversized system or one set to keep the temperature with no swing might struggle to enough data points to generate profiles.
Hope that helps!