I noticed my unraid drives do not spin-down anymore with this great integration. Also I see the max polling time for this integration is 3600 sec (1hr). Any chance to allow for higher interval like every 12 hours (43200 sec) ?
That’s interesting. The integration is not suppose to affect the spin-down of the drives. I know my drives go to standby after 30 minutes.
Can you please log an issue on the integration GitHub page? Helps me to keep track of issues to look at.
FYI: I created the power consumption monitor you asked for as feature request.
1 Like
An early Christmas! 
1 Like
This is perfect!
Thank you very much for your efforts here
1 Like
Just wanted to say thank you! 
2 Likes
Awesome, thank you so much 
1 Like
Having trouble connecting to my server via IP or via hostname. I tested from other clients and can successfully ssh via either, so doesn’t seem to be an issue with that. What can I do to diagnose?
Error from Home Assistant Log:
This error originated from a custom integration.
Logger: custom_components.unraid.unraid
Source: custom_components/unraid/unraid.py:89
integration: UNRAID (documentation, issues)
First occurred: 3:23:58 PM (1 occurrences)
Last logged: 3:23:58 PM
Failed to connect to Unraid server: [Errno 113] Connect call failed (‘192.168.1.50’, 22)
I figured out my issue and posting here in case it helps anyone else. I am running home assistant core as a docker in unraid with a custom network interface to give it an IP address (192.168.1.52) that is different from my unraid IP address (192.168.1.50). I learned that it isn’t possible for these separate docker containers with individual IP addresses to talk to one another without a special setting on unraid to enable “host access to custom networks”:
Once this setting was applied I was able to add the integration in HA without any issues!
2 Likes
Thanks for sharing and I was aware of this as it affected me in the past. I have since moved my HA off an Unraid docker (Space Invader in a box) and to a dedicated bare-metal mini PC.
Anyone else experiencing or can confirm drive spin-down no longer occurring with this integration? I’m eager to try the new feature that increases the HA polling to at least 12 hours
Loving this integration. I’m just missing sensors for network inbound and outbound. I added a feature request in the Github. Thank you for creating this!
2 Likes
I had major problems in getting this to work as repeated failure to connect during configuration. However, for dummies like me, maybe in installation you should mention that in UNRAID default setting for SSH is OFF. Therefore, settings->management access SSH to ON immediately solved my problem !
1 Like
@Gowah8 Thank you. I’ll update the installation section in readme to include SSH has to be enabled before using the integration.
1 Like
Ditto + 
When I tried to set up the automation for weekly backups, using the yaml example code above, I get this error when saving it:
Message malformed: extra keys not allowed @ data[‘automation’]
Just wanted to say thanks for this integration. I connected my Unraid servers without a problem.
My use case is switching off the Folding at Home docker (the one with a power-hungry GPU) if my home battery starts to run low. Works a treat - thanks again
1 Like
Does your UPS show this attribute?
CUMONKWHOURS
You can check for it by opening unraid terminal and typing apcaccess -u
Mine does:
ux 6.1.106-Unraid.
root@Towerxxxx:~# apcaccess -u
APC : 001,051,1199
DATE : 2024-11-12 06:22:14 -0500
HOSTNAME : Tower
VERSION : 3.14.14 (31 May 2016) slackware
UPSNAME : UPS_IDEN
CABLE : Custom Cable Smart
DRIVER : APC Smart UPS (any)
UPSMODE : Stand Alone
STARTTIME: 2024-11-10 04:40:03 -0500
MODEL : Smart-UPS 2200
STATUS : ONLINE
LINEV : 120.2
LOADPCT : 19.5
BCHARGE : 100.0
TIMELEFT : 68.0
MBATTCHG : 5
MINTIMEL : 5
MAXTIME : 0
MAXLINEV : 120.2
MINLINEV : 118.8
OUTPUTV : 120.2
SENSE : High
DWAKE : 0
DSHUTD : 90
DLOWBATT : 2
LOTRANS : 106.0
HITRANS : 127.0
RETPCT : 0.0
ITEMP : 26.5
ALARMDEL : 5
BATTV : 55.1
LINEFREQ : 60.0
LASTXFER : Automatic or explicit self test
NUMXFERS : 1
XONBATT : 2024-11-10 17:38:59 -0500
TONBATT : 0
CUMONBATT: 12
XOFFBATT : 2024-11-10 17:39:11 -0500
SELFTEST : NO
STESTI : 336
STATFLAG : 0x05000008
REG1 : 0x00
REG2 : 0x00
REG3 : 0x00
MANDATE : 08/29/06
SERIALNO : JS063600xxxx
BATTDATE : 08/29/06
NOMOUTV : 120
NOMBATTV : 48.0
EXTBATTS : 0
FIRMWARE : 654.13.D
END APC : 2024-11-12 06:22:38 -0500
root@Tower:~#
I must be blind but I don’t see the CUMONKWHOURS attribute in list
1 Like