dmacias

I just haven't had time to figure that out yet.

I added git back in

What version of unraid and what other plugins you have installed?

It's included with unraid now

This is what I've been working with to replace speedtest-cli plus no python necessary https://github.com/dmacias72/unRAID-speedtest/raw/master/packages/SpeedTest-1.14-x86_64-1.txz This is the repo I compiled it from https://github.com/taganaka/SpeedTest The only reason I haven't finished incorporating it into the plugin was the full server list. I believe it wasn't sortable for closest or something like that. Otherwise, ran automatically, it worked fine.

There is a speedtest plugin that uses speedtest-cli although I'm moving away from that since it's wildly inconsistent.

Added both

I can't test right now but I update both to newer packages. Let me know if that fixes it.

I should be able to add that.

The newer versions of tmux don't seem to come with the terminal info. It's all included in ncurses which they strip down for unraid. I added them to the 2.8 version. I had to do the same for the screen package. So it should work for you now.

I'm not sure but I think it's unraid that's missing the terminal info. I believe it was ncurses that is stripped down. I thought someone earlier in the thread fixed it but changing their terminal emulation. What unraid version and terminal are you using and what emulation?

What version of unRAID?

Added

Added

Added

If it shows up then it's working. Just a bunch of annoying errors in the log.

Only thing I could do is possibly add multiple or secondary temp sensors and choose the highest temp from them.

Sorry. Thanks for reminding me. I compiled and added vnstat 2.1.

What happens when you run it with the usbhid-ups selected?

Does it continue to work? I get similar errors. Nut 2.74 would just drop the connect and not reconnect, leaving you unprotected. I compiled the plugin's current version off a different libusb branch and you get errors but it reconnects.

You need msgpack, setuptools and Python3

@CowboyRedBeard I would probably switch up my fans. I would have cpu and case fans on the numbered fans. And cool the hard drives with a & b. If you have your cpu fans at 100 but the case fans are running slow there would be a build up of heat inside your case. Same could be said for the hdds. It all depends on how your case is set up. But with the plugin you have a little more control. I would find out what temp your cpus are throttling at and set the fans to max at that temp or a little sooner.

[mention=77388]CowboyRedBeard[/mention] Make sure you have the latest bios 3.3 and bmc firmware 3.48. Reason being, they sometimes update ipmi functionality and sensor names. Supermicro boards have 2 fan zones. Usually one zone is FANA (peripherals) and another zone for all other numbered fans like FAN1 FAN2 FAN3 FAN4. (FAN1234). Some boards have more numbered fans (FAN5 or 6) that are tied to the other numbered fans or like yours have FANB which I believe is tied to the same zone as FANA. The original intent of fan control was to monitor hard drive temps and control a zone of fans to cool hard drives. Since the bios fan control is based on cpu temps the fans don't usually spin up fast enough to maintain lower hard drive temps. E.g. during a parity check the cpu temps would not get hot enough to spin up the fans and the hdds would hit high 40C or 50s. So the fan control script monitors the hdds and uses the highest temp. So in order to control any zones you have to select a Temperature sensor to monitor in order for the fan control to work. If you want to use CPU temps you have to change from auto to a CPU temp sensor for that particular fan group. For your board you will have 2 zones: FANA & B on one zone and FAN1-6 on another zone. So you can select a temp sensor to use for each zone. You can use any temp sensor the bmc has listed or hdds temp. You can use the same for both zones if you like. Also the bmc thresholds still may be relevant. These aren't the same as what's on the Fan Control webgui page. These are alert thresholds set in the bmc. You can use Config Editor and select sensors to view and edit them. They cause a warning to appear in the bmc event log if the fan rpms go outside the thresholds set. So if the default threshold is 1000 rpms and your cpu fan drops below this, then the bmc kicks the fan to full speed and logs an alert. I hope all this helps clear up everything. Edit: you can change the high and low temp threshold after you select a sensor. They determine at what temp the fan will be at maximum speed and minimum speed.

Added

Did you give it some time after you started the fan control? How long is your polling time? Also are your thresholds set with the editor for your fans?