October 27, 20241 yr I'm excited to share a new custom integration I've developed that brings Unraid server monitoring and control capabilities to Home Assistant. 🚀 Features System Monitoring - 📊 Real-time system metrics: - CPU usage and temperature - RAM utilization - Boot drive status - Cache drive usage - Array disk status - Individual disk monitoring - 🌡️ Temperature sensors: - CPU temperature tracking - Motherboard temperature monitoring - ⚡ UPS integration: - Battery status - Power monitoring Docker Management - 🐳 Complete Docker container control: - Start/stop containers - Monitor container status - Execute commands within containers - Container health monitoring VM Control - 💻 Virtual Machine management: - Start/stop VMs - VM status monitoring - Automated VM control Command & Script Management - 🛠️ Advanced control capabilities: - Execute shell commands - Run user scripts - Schedule automated tasks - Background task execution 🔧 Installation 1. Add through HACS (recommended): - Add custom repository: https://github.com/domalab/ha-unraid - Install "Unraid Integration" 2. Manual installation: - Download the repository - Copy to your `custom_components` folder - Restart Home Assistant 📚 Documentation - GitHub Repository https://github.com/domalab/ha-unraid - Comprehensive Wiki https://github.com/domalab/ha-unraid/wiki - Issue Tracker https://github.com/domalab/ha-unraid/issues 🤝 Contributing Contributions are welcome! Feel free to: - Report bugs - Suggest features - Submit pull requests - Share your automation examples 💬 Feedback I'd love to hear your thoughts and suggestions! Feel free to: - Share your use cases - Suggest improvements - Report any issues - Ask questions Edited January 12, 20251 yr by PanicMechanic007
October 31, 20241 yr Author @John Graham Here’s the link to the repo. Install via HACS https://github.com/domalab/ha-unraid
November 21, 20241 yr i try everything to login, but i've got an timeout error when i trying to connect. Enregistreur: custom_components.unraid.unraid Source: custom_components/unraid/unraid.py:91 Connection to Unraid server at ***** timed out its work when i log with SSH directly. Some one have an idea ? HA is on a VM in unraid.
November 21, 20241 yr Author Did you try to ssh to unraid from the HA VM using the HA Terminal add-on? Is your HA VM directly connected to same network as Unraid?
November 24, 20241 yr Thank you for this great Integration! It's included the temperatures of the HDDs/SSDs?
November 26, 20241 yr Author On 11/24/2024 at 11:48 AM, proxy4k said: Thank you for this great Integration! It's included the temperatures of the HDDs/SSDs? Yes, it’s reading the SMART health from disks. I will be releasing an update soon with better SMART integration
December 6, 20241 yr Is there a way to use this integration so that when the UPS attached to Unraid cleanly shuts the server down and then normal power is restored to the UPS and not using the battery Home Assistant can turn the Unraid server back on using something like wake on lan? For example; automation that checks if UPS is using the battery, if yes don't use wake-on-lan integration to wake up Unraid, if it's using mains power, send a magic packet using wake-on-lan integration. Edit: I just realised this probably isn't going to work as HA isn't going to know the status off the UPS (battery or mains power) if Unraid is off. I only want to turn Unraid on if the UPS is using mains and no longer using battery. Edited December 6, 20241 yr by nodii
January 9, 20251 yr This is great, thank you very much. However the SSH connections are spamming my unraid log like crazy. I know I could increase the polling interval but I'd prefer to keep it at 5 minutes if possible. Is there a way to reduce the log entries? Currently getting 364 lines every 5 minutes: Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0
January 10, 20251 yr Author Good to know. I'll investigate and try and fine tune the code to reduce it some more.
January 10, 20251 yr Author 15 hours ago, DJ Callyman said: This is great, thank you very much. However the SSH connections are spamming my unraid log like crazy. I know I could increase the polling interval but I'd prefer to keep it at 5 minutes if possible. Is there a way to reduce the log entries? Currently getting 364 lines every 5 minutes: Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Can you please log it as an issue? https://github.com/domalab/ha-unraid
January 11, 20251 yr could you somehow make it possible to read HDD temps? i would like to use HDD temp readings to turn on an room-exhaust-fan in my server closet. awesome plugin!
January 12, 20251 yr Author 2 hours ago, shorshi said: could you somehow make it possible to read HDD temps? i would like to use HDD temp readings to turn on an room-exhaust-fan in my server closet. awesome plugin! Yes you can, if your disks are on all the time then you should see the disk temperature attributes under disk usage and disk health sensors. In my case my disk spin down after 30 minutes of inactivity and temperature readings shows N/A (Standby) You can use the temperature attribute in your automation to trigger Fan or AC
January 12, 20251 yr ohhhh awesome thanks a lot! thats fantastic! really great integration you wrote there man. Dankeschön
January 12, 20251 yr Author 6 hours ago, shorshi said: ohhhh awesome thanks a lot! thats fantastic! really great integration you wrote there man. Dankeschön Checkout the wiki too for more info and automation ideas https://github.com/domalab/ha-unraid/wiki
January 12, 20251 yr Author On 1/9/2025 at 7:05 PM, DJ Callyman said: This is great, thank you very much. However the SSH connections are spamming my unraid log like crazy. I know I could increase the polling interval but I'd prefer to keep it at 5 minutes if possible. Is there a way to reduce the log entries? Currently getting 364 lines every 5 minutes: Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 1 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 2 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Close session: user root from 192.168.0.62 port 50074 id 0 Jan 9 19:49:24 NAServer sshd-session[21183]: Starting session: command for root from 192.168.0.62 port 50074 id 0 I looked at the code to see if I can optimise it further but it's already very optimised. I can only think of splitting the different sensor updates so that the user can specify the intervals for CPU, Temp, Disk, Network, UPS, etc Other option is you can look into whitelist / suppress the HA IP so that it doesn't show in the logs. https://github.com/domalab/ha-unraid/wiki/Troubleshooting#ssh-session-log-spam Edited January 15, 20251 yr by PanicMechanic007
January 12, 20251 yr Author On 1/10/2025 at 2:20 AM, faxxe71 said: That log spam was the reason for me to uninstall this actually useful tool. You can look into whitelist / suppress the HA IP so that it doesn't show in the logs. https://github.com/domalab/ha-unraid/wiki/Troubleshooting/_edit#ssh-session-log-spam Edited January 15, 20251 yr by PanicMechanic007
February 28, 20251 yr This is really awesome! Is there any way to have system fan speed accessible in HA? Specifically to control the case PWM fans attached to the motherboard?
June 6, 20251 yr Author On 4/26/2025 at 12:19 AM, mhinkle said:I'm not sure what I'm doing wrong, but this isn't showing up in HACS for me. You can add it as a custom integration in HACSGitHubGitHub - domalab/ha-unraid: Monitor and control your Unra...Monitor and control your Unraid server directly from Home Assistant. Track system metrics (CPU, RAM, disk usage), manage VMs and Docker containers, monitor UPS status, and receive real-time alerts....
June 6, 20251 yr Author Im working on the unraid integration that uses the Unraid GraphQL API. You can try it out and go through the list of issues to see what’s features are missing.GitHubGitHub - domalab/ha-unraid-connect: Unraid Connect Integr...Unraid Connect Integration for Home Assistant. Contribute to domalab/ha-unraid-connect development by creating an account on GitHub. Edited June 6, 20251 yr by PanicMechanic007
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.