Home Assistant add-ons for monitoring and controlling Dell PowerEdge servers through their iDRAC via IPMI, with support for 12th- and 13th-generation servers (iDRAC 7/8, e.g. R720, T430, R430, R630, R730) and robust fan control and hardware monitoring.
- 13G CPU temperature sensors are found. iDRAC 8 reports
CPU1 Temp/CPU2 Temp(processor entities3.x); the original stable add-on only matched a sensor literally namedTempand therefore never controlled fans on a T430/R730. Parsing now uses the entity ID and falls back to the 12G-style name, so both generations work. - PSU status is no longer wrong on 13G. The old check required a
Voltage 1sensor that iDRAC 8 does not expose; presence plusPSn PG Failis used instead. - Inlet/exhaust sensors are matched at the start of the name, so a
PSU1 Inlet Tempsensor can no longer replace the chassis inlet reading. This is the same trap tigerblue77's controller fixed in issue #231. - Refused fan control is remembered. A 14G+/iDRAC 9 server, or an account below Administrator, answers the Dell OEM fan commands with 0xc1/0xd4/0xd5. The add-on detects it once, stops retrying, and keeps monitoring.
- Optional third-party PCIe cooling response. Per-server setting that sends the 12G/13G OEM command to disable Dell's default cooling response for non-Dell cards, and restores Dell's setting on shutdown. The exact command bytes are the ones used by tigerblue77's controller.
- Partial fan failures are handed back to Dell auto instead of leaving the fans pinned at the previous manual speed.
- Diagnostics: firmware version and service tag/serial are read from the
iDRAC and published on the MQTT device (
sw_version,serial_number). - Sanity checks: implausible temperature readings (-20..125 °C) and
contradictory thresholds (
critical <= low,high < base) are ignored or corrected with a warning. - Fan control no longer flaps. A 2 °C hysteresis band is applied to the base/high thresholds and to the hand-back-to-iDRAC critical threshold.
- Safe fan floor. 0–4 % requests are clamped to 5 %; the web UI and add-on schema reject values below 5 %.
- MQTT outages no longer kill monitoring. The BETA add-on retries the broker instead of stopping the worker, and re-subscribes/re-publishes discovery after a reconnect.
- Passwords are no longer on the
ipmitoolcommand line.-E+IPMI_PASSWORDis used, so the iDRAC password does not appear inps. - Watchdog enabled so Supervisor restarts an add-on that exits unexpectedly; the BETA
add-on also exposes
/health, which fails only if every server worker has died. - Removed the unused
master_encryption_keyoption. It was never used by the code; iDRAC credentials live in the add-on's private/datavolume. - Tests + CI for the SDR parsers and the fan hysteresis logic.
- The stale
multi-serveradd-on was removed; the BETA add-on already supports multiple servers and is the only one still maintained.
| Name | For whom | Servers | Fan control | Extras |
|---|---|---|---|---|
HA iDRAC Controller Standard (ha_idrac_controller_standard, 0.2.0) |
Recommended for everyday use | Multi-server | Simple, Multi-Point Curve, Self-learning Target Temperature | Fan failure detection, SNMP disk health, watchdog, live UI settings |
HA iDRAC Controller BETA (ha_idrac_controller_development) |
Testing new features | Multi-server | Simple, Multi-Point Curve, Self-learning Target Temperature | Same as Standard, receives changes first |
HA iDRAC Controller (ha_idrac_controller, 0.1.2) |
Legacy / under review | Single server | Simple 3-tier with hysteresis | No self-learning, no disk monitoring, has not received recent sensor fixes |
Use HA iDRAC Controller Standard for normal use. Only install HA iDRAC Controller BETA if you want to test upcoming changes before they land in Standard. Never run two add-ons against the same iDRAC server at the same time, as both will send competing IPMI fan commands.
Both add-ons use the standard 12G/13G Dell fan-control sequence:
raw 0x30 0x30 0x01 0x00(manual) andraw 0x30 0x30 0x02 0xff <pct>. Do not use these add-ons on iDRAC 9 (14G+) without checking the raw commands for your firmware.
-
In Home Assistant go to Settings → Add-ons → Add-on Store.
-
Open the three-dot menu → Repositories.
-
Paste this URL (no markdown, no brackets):
https://github.com/Aesgarth/HA-iDRAC -
Install HA iDRAC Controller BETA for a T430.
-
Enable IPMI over LAN on the iDRAC (iDRAC Settings → Network → IPMI Settings), set the privilege limit to Administrator, and make sure HA can reach UDP 623 on the iDRAC.
-
Start Mosquitto (or another MQTT broker) before starting the add-on, fill in the MQTT settings, save, start the add-on, then add the server in the web UI (Manage Servers) and restart the add-on once.
The repository previously defined a third add-on, multi-server, which was
an older snapshot of the BETA code and has been removed. If you were using
multi-server, switch to the HA iDRAC Controller BETA add-on instead.
- Fan values are percentages of the iDRAC's maximum fan speed, not RPM.
Start with
base_fan_speed_percent: 20,low_temp_threshold: 45,high_temp_fan_speed_percent: 50,critical_temp_threshold: 65and watch the temperatures for a day before lowering anything. - The BETA add-on stores servers in
/data/servers_config.json(root-only on HA OS) with the iDRAC password in plain text. Do not reuse an administrator password from another system. - The add-on needs an iDRAC account with Administrator privilege. A lower account gets the fan commands refused with 0xd4 and the add-on switches to monitoring-only automatically.
- On stop the BETA add-on hands the fans back to Dell's automatic profile. If
the container is killed without running its shutdown handler, the iDRAC
stays in manual mode at the last speed — enable the Supervisor watchdog
(done in
config.yaml) and keep an eye on the server after host crashes. - Sensor naming differs between firmware versions. If the log shows
"No CPU temperature sensor found", set
log_level: debug, check the raw SDR output in the log, and open an issue with thesdr type temperaturelines for your model.
- The third-party PCIe cooling-response command is a Dell OEM command for 12G/13G. Some firmware does not accept it; the add-on logs that once and leaves the setting untouched. It is only applied when fan control is enabled.
- iDRAC 9 / 14th generation and newer are not currently targeted. The raw fan commands and sensor layout differ.
- A
SIGKILL, OOM kill or host power loss cannot run the shutdown handler, so the iDRAC can stay in manual mode. The Supervisor watchdog restarts the add-on in that case, which re-applies the configured fan profile. - The 13G parsing is covered by unit tests and a fake-IPMI run, not by a physical T430. The first start on real hardware should be monitored.
python -m pytest -qThe tests run without an iDRAC and without Flask/paho installed; they cover 12G/13G SDR parsing, fan RPM/power/PSU parsing and the hysteresis logic. GitHub Actions runs the same suite on every push.
- sam2kb for the 13G/T430 support and hardening work (PR #2).
- tigerblue77, Breina, and rztw for ideas and reference implementations adopted from their projects.
MIT License. See LICENSE for details.