@ ruaandeysel
Very nice, thank you, setup was easy (- if I would have known only “root” gets ssh acces ist would be a pleasure to intall)
regards
Franky
Great work on this integration! I found out about it from the most recent Self-Hosted podcast episode and decided to set it up today.
I doubt it is a bug in the integration, but I am experiencing some warnings in the HA logs every 5 minutes:
2025-05-03 20:05:36.043 WARNING (MainThread) [custom_components.unraid.api.smart_operations] SMART command failed for nvme0n1: exit_code=2
2025-05-03 20:05:36.696 WARNING (MainThread) [custom_components.unraid.api.smart_operations] SMART command failed for nvme0n1: exit_code=2
2025-05-03 20:05:41.558 WARNING (MainThread) [custom_components.unraid.coordinator] Skipping invalid date: 1969 Dec 31 18:00:00
Do you have any insight as to how I could go about address this issue? I tried to figure out which disk was connected as nvme0n1 but I can’t find it anywhere on the unRAID GUI or filesystem.
Keep up the great work!
You can try the updated source code by manually copying the unraid folder to your HA instance.
I did a manual update of copying the code on top. Deleted my old UNRAID servers to start clean. Restarted HA. Added servers back. And now I have nice clean naming of entities. Double names gone. Thank you.
Am i correct that it kinda takes a long time when a container goes offline on unraid to show the change in HA ? Is there a way to live monitor a container?
I really love this integration and it is working very well. But would it also be possible to include GPU usage in the Unraid sensors?
It’s possible. I tested it in the past and could only get it to work on Intel as I have iGPU in my Unraid Server. I’ll need AMD and Nividia GPUs to get code to work on them.