CoolerControl daemon health: version, uptime, warning/error counts.

List hardware CoolerControl knows about (CPU, GPUs, fan hubs, AIOs, PSUs, drives) with their speed-controllable channels and temperature sensors. Use the uids and channel names here for other tools.

Latest sensor readings: temperatures (°C), fan rpm, duty (%), power (W) and frequencies (MHz). Optionally limited to one device and channel.

What each speed-controllable channel is set to: a profile (by name), a fixed duty, or the default. Covers all devices unless one is given.

Fan profiles (fixed, graph curves temp→duty, mixes) with their temperature source.

Functions that shape how profiles apply duty changes (min/max duty, step sizes, hysteresis).

Saved modes (snapshots of all channel settings) and which one is active.

Configured alerts and the recent alert log.

User-defined custom sensors (mixes of other temps, or file-based sensors).

Set a fan/pump channel to a fixed duty %. Values below 20% are refused (COOLERCONTROL_MIN_DUTY). Returns the previous setting so it can be restored.

Assign an existing profile (see list_profiles) to a fan/pump channel. Returns the previous setting.

Reset a fan/pump channel to its hardware default, removing any profile or fixed speed. Returns the previous setting.

Activate a saved mode (see list_modes), applying all of its channel settings.

Create a fan profile. Fixed: a constant duty. Graph: a temperature→duty curve following one sensor. Mix: combines member profiles (Min/Max/Avg/Diff/Sum). Overlay: offsets one base profile. Assign it to a channel afterwards with apply_profile.

Change an existing profile. Only the fields given change; a new curve or offset replaces the old one. Changing type requires the new type's fields. Channels using the profile pick up the change immediately.

Delete a profile. Refuses if any channel, Mix/Overlay profile or mode uses it, listing where, unless force is true; with force, channels using it fall back to their default and modes drop it.

The channel settings saved in a mode, with device and profile names.

Save the current settings of every channel as a new mode, which activate_mode can restore later.

Rename a mode and/or overwrite its saved settings with the current channel settings.

Copy a mode, including its saved settings.

Delete a saved mode. Channel settings currently applied are not changed.

Create a function. Required: name. Unset fields copy the Default Function. Common fields: f_type (Identity | Standard), duty_minimum / duty_maximum (step size per change, %), step_size_min_decreasing / step_size_max_decreasing, threshold_hopping, bypass_min_at_extremes; Standard also takes deviance, response_delay, only_downward.

Change fields of an existing function; fields not given keep their values.

Delete a function. Refuses if it is in use unless force is true.

Create a alert. Required: name, min, max, warmup_duration (s), channel_sources: [{device_uid, channel_name, channel_metric}] where channel_metric is Temp | Duty | Load | RPM | Freq (all sources share one metric; channel_name is the sensor/channel name, e.g. temp1 or fan1). Optional: cooldown_duration, repeat_interval, enabled, desktop_notify, desktop_notify_audio, desktop_notify_recovery, shutdown_on_activation.

Change fields of an existing alert; fields not given keep their values.

Delete a alert.

Create a custom sensor. Required: id (unique; becomes the sensor's name) and cs_type. cs_type Mix: mix_function (Min | Max | Delta | Avg | WeightedAvg | Sum) and sources: [{temp_source: {device_uid, temp_name}, weight}]. File: file_path. Offset: offset, optional scale, one source. TimeAverage / ExponentialMovingAvg: time_window_seconds (1-300), one source. Optional metric (Temp default; Duty | Load | RPM | Freq use channel_source instead of temp_source in sources).

Change fields of an existing custom sensor; fields not given keep their values.

Delete a custom sensor. Refuses if it is in use unless force is true.

Every CoolerControl 5.1.1 REST endpoint a token can call, for use with call_api: lighting, LCD, calibrations, name overrides, daemon settings, stats, hardware detection, power profiles, ThinkPad / AMD overdrive, logs, metrics and the endpoints behind the other tools. Filter by tag or text.

Call any endpoint from list_api_endpoints directly. Prefer the dedicated tools when one fits; they validate inputs. Non-GET calls change daemon state and need a token with Write Access.