Monitor and control your OpenMediaVault NAS from Home Assistant.
Note: This is an independent community project and is not affiliated with or endorsed by the OpenMediaVault project or its developers.
This integration is a full modernization of tomaae/homeassistant-openmediavault, building on the groundwork laid by cneuen/homeassistant-openmediavault. Selected compatibility improvements from Boci-HA/homeassistant-openmediavault have also been incorporated.
The original integration relied on a synchronous, poll-based controller that no longer fits the current Home Assistant architecture. This fork replaces that foundation with a native async client, a DataUpdateCoordinator-driven update cycle, and a platform structure aligned with modern HA conventions. Alongside that architectural shift, the scope of what the integration monitors has grown substantially: per-resource device modeling, Docker Compose support, ZFS pool awareness, RAID synthesis, dynamic localized entity names, capacity sensors, and a richer options flow are all new additions rather than ports of existing functionality.
- Async OMV JSON-RPC client based on aiohttp
- DataUpdateCoordinator architecture for predictable polling and updates
- CPU, memory, temperature, filesystem, disk, SMART, network, RAID, and optional ZFS monitoring
- Per-resource device modeling — disks, RAIDs, filesystems, ZFS pools, and Docker containers each appear as separate HA devices
- Docker Compose support with per-container state, version, and lifecycle button entities
- Binary sensors for package updates, reboot requirement, and OMV services
- Reboot and shutdown buttons
- Localized dynamic entity names that follow the active HA language
- OpenMediaVault 7 and 8
- Home Assistant 2025.5 or newer
- Python 3.13.2 or newer for local development and CI
The active integration domain is omv.
- Open HACS.
- Go to Integrations.
- Add the custom repository https://github.com/slybase/homeassistant-openmediavault.
- Install OpenMediaVault (OMV).
- Restart Home Assistant.
- Add the OMV integration from Settings, Devices & Services.
The config flow asks for:
- Host
- Username
- Password
- Port
- SSL
- SSL verification
After setup, the options flow lets you adjust:
- The scan interval
- Whether SMART polling should be disabled
- Virtual passthrough mode for hypervisor-backed setups (e.g. Proxmox) — disables SMART polling and temperature entities automatically
- Which disks, filesystems, network interfaces, services, RAIDs, ZFS pools, Compose projects, and containers are monitored — resources not selected simply disappear from Home Assistant
- CPU utilization, memory usage, CPU temperature, uptime, available package updates
- Intel iGPU load and current frequency (when available via sysfs)
- Docker container summary: total, running, and not-running counts
- Binary sensors: update available, reboot required
- Buttons: Reboot, Shutdown
- Temperature
- Used %, free %, used size, free size, total size
- SMART status and SMART attributes (Raw Read Error Rate, Reallocated Sector Count, Pending Sector Count, Uncorrectable Sector Count, Power On Hours, Start Stop Count, Load Cycle Count)
- Used %, free %, used size, free size, total size
- TX rate (Mbps), RX rate (Mbps)
- RAID health status
- Pool status
- Binary sensor: service running / not running
- Project status, total containers, running containers, not-running containers
- Buttons:
compose up,compose down,start,stop,pull
docker image prune,docker container prune
- State, status detail, created timestamp, started timestamp, image version
- Volume size (when reported by OMV)
Install the local test and development dependencies with:
pip install -e ".[test,dev]".venv/bin/python -m ruff check custom_components tests
.venv/bin/python -m pytest tests -q
.venv/bin/python -m pytest tests --cov=custom_components/omv --cov-report=term-missinglogger:
default: info
logs:
custom_components.omv: debugSee docs/omv-rpc-compatibility.md for the current RPC compatibility summary and the live probe workflow for validating OMV7 and OMV8 side by side.