Monitor a NASty storage appliance from Home Assistant and optionally control its virtual machines and Apps.
This integration is an independent implementation built against NASty's public REST API. It does not contain or depend on code from an Unraid integration.
- CPU temperature and load, memory use, uptime, system health, and active alerts
- Filesystem capacity and mount state
- SMART health and temperatures for discovered disks
- UPS battery, runtime, load, input/output voltage, and connectivity from NUT
- App runtime statistics
- Optional start/stop switches for VMs and Apps
- Reauthentication and privacy-redacted diagnostics
NASty is polled locally every 30 seconds for runtime state and every five minutes for filesystem and SMART data. The integration does not use a cloud service.
- A NASty appliance with the REST gateway enabled
- A Viewer API token for monitoring
- An Operator or Admin API token only if VM and App controls are enabled
- Network access from Home Assistant to the appliance
Use the least-privileged token that satisfies your configuration. TLS certificate verification is enabled by default.
Until the repository is included in the HACS default catalog:
- Open HACS in Home Assistant.
- Open the menu in the top-right corner and select Custom repositories.
- Enter
https://github.com/nasty-project/nasty-ha, select the Integration category, and add the repository. - Search HACS for NASty and install it.
- Restart Home Assistant.
- Open Settings > Devices & services > Add integration, search for NASty, and complete the configuration flow.
Copy custom_components/nasty into Home Assistant's custom_components
directory and restart Home Assistant. Add NASty from the integrations UI.
Enter the appliance base URL and API token. The URL can include an existing path prefix, but must not include credentials, query parameters, or fragments.
Leave Enable VM and App controls disabled for monitoring-only setups. The integration never exposes destructive storage, VM creation, or App installation operations.
If NASty uses a private certificate authority, import that CA into Home Assistant where possible. Disabling certificate verification should be a last resort.
uv sync --extra dev
uv run ruff check .
uv run pytest
uv run python -m compileall -q custom_componentsThe integration source is GPL-3.0-only. See LICENSE.