v1.5.5.7
Thanks to @Inch-high for the detailed follow-up on #12 — network and disk telemetry on Unraid needed more than settings normalization.
What changed
templates/amud-agent.xml— AMUD Agent uses host network by default; optional read-only Array (/mnt/user) and Cache (/mnt/cache) bind-mounts for disk mappingdocker-compose.yml— commentednetwork_mode: hostand bind-mount examples for production telemetryamud-agent—AMUD_PROC_NET_DEV,telemetry_scope, visible iface/mount lists, bond/zero-traffic heuristic, per-mountdisk_volumes,telemetry_discoveractionamud-protocol—DiskMountTelemetryand newAgentTelemetryfieldsamud-server—/api/telemetry/discoverfor Settings Test host visibility- Dashboard UI — separate disk tile per configured mount; (container scope) / (auto-detect) admin hints
- Docs — Unraid Step 3b, expanded troubleshooting decision tree
Install / Upgrade
Proxmox / bare metal:
curl -sSL https://github.com/boubli/AMUD-Dashboard/releases/latest/download/update-amud.sh | bashDocker / Unraid:
docker compose pull && docker compose up -d --force-recreateOn Unraid: Force Update both AMUD-Dashboard and AMUD-Agent, re-apply agent template (host network + array/cache mounts), then hard-refresh (Ctrl+Shift+R). Use Settings → Test host visibility to confirm Scope: host.