maxandcheese

Hey all! This started with a simple problem: I wanted to know when my Unraid array was running a parity check or disk rebuild so I could trigger a cooling fan automatically. There wasn't a reliable way to get that signal into Home Assistant, so I built a native plugin instead. Once that worked, I kept going, and now it publishes a pretty comprehensive set of server metrics to MQTT with full HA auto-discovery support. What it monitors Array & Cache — status, capacity, used %, disk count, disabled/invalid/missing disks Parity & Rebuild — status, progress %, speed, and ETA (this is where it all started!) Disks — per-disk temp, state (Active/Standby/Disabled), SMART health, reallocated/pending/uncorrectable sectors, read/write speeds, power-on hours System — uptime, Unraid version, server ID, network RX/TX per interface, share usage Each metric can be published on an interval, on-change, or both — so you're not flooding your broker unnecessarily. Home Assistant Entities appear automatically via MQTT discovery the moment the daemon starts. You get full sensor.unraid_* entities with state attributes for things like disk size, free/used GB, SMART details, and share metadata. No manual configuration needed. A small taste of what shows up: sensor.unraid_array_status sensor.unraid_parity_status sensor.unraid_parity_progress sensor.unraid_disk1_temp sensor.unraid_disk1_smart_health sensor.unraid_net_eth0_rx sensor.unraid_share_media_infoInstallation Go to Plugins → Install Plugin and paste: https://raw.githubusercontent.com/maxandcheeses/unraid-stats2mqtt/refs/heads/main/plugin/unraid-stats2mqtt.plgAll settings are managed through the Unraid WebUI under Settings → Stats to MQTT. Supports plain MQTT, MQTTS (TLS), WS, and WSS — including mutual TLS and self-signed certs. GitHub: https://github.com/maxandcheeses/unraid-stats2mqtt This is an early release so feedback, bug reports, and feature requests are very welcome. Curious what metrics others would find useful, and would love to see what HA automations or dashboards people build with it!

I was under the assumption you got the thunderbolt drive mounted manually and wanted to automate the process. Have you tried echo 1 > /sys/bus/thunderbolt/devices/0-*/authorized to get the device mounted. A reboot shouldn’t be required.

Try putting the rule in /boot/config/udev/99-local.rules Edit /boot/config/go and add this before any emhttp line: #!/bin/bash # Copy udev rule to system directory at boot cp /boot/config/udev/99-local.rules /etc/udev/rules.d/ udevadm control --reload-rules udevadm trigger --subsystem-match=thunderbolt

I ran into this issue myself last night when it was doing a parity rebuild. The system rebooted itself and the parity check/build continued.zimacube-diagnostics-20240801-0004.zip

I just ran into a similar issue today. I have a second nic attached to a private lan with no gateway on it but I filled in the field IPv4 default gateway with 10.10.10.1. After removing this and keeping the field blank, I was finally able to connect to my smb share.