Just follow Unraid’s guide to get started and get API key and run the Unraid Connect integration in another HA instance.
@kevinconsen I’ll have to experiment with reducing update intervals to 5 seconds for certain sensors like system metrics.
Sadly it didnt worked for me.
Newest version, even tried your fix wirh downloading the newest code and past it into the unraid folder in custom_components
Any ideas for a fix?
hey,
i just started using your integration.
thanks for your work and for sharing it!
i had no problem with setting up, so great work on that and on your documentation.
what i would like to do, is being able to visualise the uptime/downtime of my array disk 1 and array parity disk. i would really love to see their current status and with this data i could also see the history of their status, depending on my interval of checking.
is that already possible somehow?
thanks,
Mario
1 Like
Interesting question, To implement disk uptime/downtime history tracking I’ll have to create new binary sensors.
Thanks @ruaandeysel , the integration works a treat. Had to upgrade Unraid to v 7.0.1 to get VMs. Is there a way to get data for unassigned disks?
My Logs are full of failed SSH sessions, and confirmed that it’s this integration is causing it. I looked up on your github the error and found unRAID Logs Full From Too Many Sessions. At the bottom the solve is to copy files from the gihub to custom_components directory. My HA is in a VM on my unraid server and I don’t have access to the file system to copy the files. Is this issue going to be fixed in an upcoming update? I really want to use this integration but I’ll have to keep this disabled and go back to Glance until it is.
For me even this fixed changed anything. So lets see whats coming
Good morning everyone,
in the new version the following two entities are no longer available from unraid?
- unraid_server_pool_cache_usage
- unraid_server_pool_cache_health
Good morning,
unfortunately i am not able to connect the plugin to unraid.
2025-07-17 08:46:51.877 ERROR (MainThread) [custom_components.unraid.api.connection_manager] Connection failed to 192.168.1.210: [Errno 111] Connect call failed ('192.168.1.210', 22)
I checked everything twice, did restart hassio, did reinstall the plugin, ssh is enabled on unraid and i am able to access unraid via the ip i entered.
Any ideas?
Can you ssh into unraid with something like Putty?
I had to restart the ssh agent in unraid via the console. Dont know why it was off. In the settings it was always set to YES. Works now.
Are there plans to include the entities again?
no support for this integration anymore?
@ruaandeysel having the same issue here. Had to disable the integration due to spammed File Syslog.
Any solution or maybe an update to fix?
I’m leaving it up to that the original dev I think is in Europe and it’s their holiday season so they could be gone for several weeks. I don’t know if there is a second chair dev on this project. I’ve just unfortunately disabled the integration as I’ve already applied the proposed fix from Github and the log spamming remains.
same here.
And missing the two entities:
- unraid_server_pool_cache_usage
- unraid_server_pool_cache_health
same issue here. Log is filled. And issue are no longer available in github. @ruaandeysel is this still developed?
Project Direction Update: Moving to GraphQL API
I wanted to share an important update regarding the future development of this integration. After careful consideration, I’ve decided to focus my efforts on developing a new version that utilizes Unraid’s official GraphQL API instead of continuing with the current SSH-based implementation.
Why this change?
- Improved Reliability: The GraphQL API provides a more stable and officially supported method of interacting with Unraid
- Better Performance: Direct API access should result in faster response times and less system overhead
- Future-Proof: As Unraid continues to develop their API, we’ll benefit from new capabilities without requiring extensive rewrites
- Reduced Edge Cases: Many of the current integration’s limitations stem from the varied environments where SSH commands can behave differently
What this means for users
The current SSH-based integration will remain available but will enter maintenance mode. I won’t be actively developing new features or addressing edge cases for it. Instead, I’m channeling those efforts into the new GraphQL-based integration, which I believe will provide a better experience for everyone in the long run.
For those who need immediate fixes for specific edge cases in the current integration, I encourage you to fork the repository and adapt it to your needs. Pull requests are still welcome and will be reviewed, though my primary development focus will be on the new approach.
1 Like