Description
On startup, the fan sensor briefly reports a value of 100% during fan spin-up, even though the fan never actually reaches that speed in normal operation.
For example, in my case the fans physically max out at around 28%, but Stats still sends a "Sensor 100%" notification because of that transient startup read.
This only appears momentarily during initialization/spin-up, suggesting the sensor value is unstable before settling to the real RPM or percentage.
It may also be related to how the fan voltage or control signal is interpreted during startup. The fan briefly appears as 100%, but this seems to be a transient initialization reading rather than the actual fan speed.
Suggested solution
It would probably make sense to debounce or stabilize the sensor read before triggering notifications. For example:
- Ignore the first sensor sample(s) after startup
- Require the value to remain above the threshold for a short duration
- Apply a small debounce window before dispatching notifications
This would help avoid false-positive alerts caused by transient initialization values.
Description
On startup, the fan sensor briefly reports a value of
100%during fan spin-up, even though the fan never actually reaches that speed in normal operation.For example, in my case the fans physically max out at around
28%, but Stats still sends a"Sensor 100%"notification because of that transient startup read.This only appears momentarily during initialization/spin-up, suggesting the sensor value is unstable before settling to the real RPM or percentage.
It may also be related to how the fan voltage or control signal is interpreted during startup. The fan briefly appears as
100%, but this seems to be a transient initialization reading rather than the actual fan speed.Suggested solution
It would probably make sense to debounce or stabilize the sensor read before triggering notifications. For example:
This would help avoid false-positive alerts caused by transient initialization values.