Skip to content
On this page

๐Ÿ“Ÿ Custom Sensors โ€‹

Custom Sensors let you build virtual sensors from existing data to improve control accuracy and efficiency. Use them to combine, transform, or adjust readings so your profiles respond to the right signals.

Types โ€‹

Mix โ€‹

Combine multiple sensors into a single output using a mix function (Average, Maximum, Minimum, Delta, Weighted Average). This is helpful when you want fans to respond to the hottest component (Max), or to overall system heat (Average).

Constraint: Custom sensors may reference only one level of other custom sensors (parent โ†’ child). This prevents circular dependencies.

Choosing a mix function:

  • Maximum: prioritize the hottest input (most common for case/exhaust fans).
  • Minimum: keep speeds low unless all inputs are hot (niche).
  • Average: smooth overall response when multiple parts contribute heat.
  • Delta: react to temperature gaps (e.g., internal vs. ambient) to maintain airflow margins.
  • Weighted Average: give more weight to more important inputs (e.g., liquid temperature).

TIP

When mixing two temperature sensors with different ranges and response dynamics, using a Mix Profile is preferred over a Mix Custom Sensor.

File โ€‹

Create a sensor that reads values from a file. Useful when an external tool exports a temperature not natively detected by CoolerControl.

Requirements:

  • Currently only temperature values are supported.
  • The file must use the Linux sysfs format (millidegrees Celsius). Example: 80000 for 80ยฐC.

Offset โ€‹

Apply a fixed offset to an existing sensor (positive or negative). Helpful to calibrate sensors or to compensate for known deltas (e.g., account for probe placement).

Released under the GPLv3+ License.