avluis

Looking to make use of a python based application that interacts with Home Assistant and Elgato Stream Deck (runs on the unraid host, not Docker) which requires this library: https://github.com/libusb/hidapi Slackware builds is making use of https://github.com/signal11/hidapi which is no longer supported/outdated. On Debian these would be the packages I would be seeing to install: libudev-dev libusb-1.0-0-dev libhidapi-libusb0 Since Fix Common Problems now warns about packages being installed via the extras (and because this would be a great utility to have in NerdPack) I'd like to make the request to have hidapi included.

I've had a few python scripts that run in the background which I needed to start/stop alongside the array; ex: #!/bin/bash #description=Starts Stream Deck Home Assistant Client. Req: python3 #arrayStarted=true #name=start stream deck HASS client # Change to app directory cd /mnt/user/appdata/homeassistant-streamdeck/ # Source python venv source venv/bin/activate # Change to app src directory cd /mnt/user/appdata/homeassistant-streamdeck/src # Check if already running and stop if pgrep -f "python3 HassClient.py" &>/dev/null; then echo "app is already running, killing" pkill -9 -f "python3 HassClient.py" sleep 5 fi # Start app python3 HassClient.py & pid=$! # User Scripts background fix echo $pid > /tmp/user.scripts/running/start-streamdeck-ha wait $pid I've been able to get the intended behavior by saving the child PID manually along with a wait command. Haven't looked too deep into exec.php for a better workaround but this is working for the moment.

When uninstalling this plugin, is it supposed to remove pigz/unpigz? After doing so was not able to update my docker containers until re-installed (didn't try restarting); Note that when I went to reinstall, got the following message so the plugin installs its packages but not shown as installed: plugin: run failed: /bin/bash retval: 1

All file operations should take place in the background -- WebUI updates itself as things progress -- kind of how things have shifted with the latest updates -- love the WebUI experience so much more now! For those that are unaware of solutions from QNAP and Synology, give their online demo a try -- should give a few ideas: https://www.qnap.com/en-us/live-demo/ https://demo.synology.com/en-us

I've the SNMP plugin working -- and it exhibits the same behavior as your plugin after a shutdown as well, so it does support what you are saying here. Would love to see that NUT plugin taken under someone's care

Not necessarily -- but some may require installing the Low-Noise Adaptor (NA-RC7). Also, I would love to have that exact same setup, but for the D-1541. Yep -- that's what I saw as well. That NUT plugin is currently unmaintained so I may have to fork and go from there. But thanks for confirming that, wanted a second set of eyes on that to dismiss any issues with your plugin. It's not often, but I have seen BIOS updates change the behavior of system accessories (fans, temp probes, etc) -- but I'm not going to sit here and tell you that's the issue since I have not worked with your particular board. What I would look into is that max rpm -- the system is, more than likely, simply pushing more than what the fan needs. Took a look at the Amazon listing (https://www.amazon.com/Nanoxia-Silence-140mm-Cooling-NDS140PWM-1400/dp/B00CHW8QD2) for additional info and in all honesty, unless they are running loud (which they shouldn't), I wouldn't worry about it. What I would give another try would be to play with these options: IPMI-IP -> Configuration -> Fan Mode I have seen a few SM systems get stuck at Full Speed while changing settings over ipmi -- so you'll need to get on the web interface and change it a few times (between full speed and another setting) to get it to apply.

Are any of those fans Noctua?

Had this happen again: This time around, I happen to notice a few things on the log that should make you happy~ From my quick look -- it seems as if some packages are forcing dependency 'upgrades' if already installed. So we end up with an older version of a dependency (in my case, freeipmi-1.4.11-x86_64-3.txz vs freeipmi-1.5.3-x86_64-1.txz). avnet-unraid-syslog-20170428-0218.zip

Good to know -- I went ahead and switched over to connect over the network as well. I appreciate the heads up there since there is no point waiting for it to drop monitoring locally if it works via the network~

I'm currently connecting locally so I'll give network a try if the issues presents itself once again. I'll make sure to keep an eye out to confirm the single sensor, but I'm fairly certain it is HDD Temperature -- don't quote me on this yet (my memory ain't great -- need an upgrade).

Just to add to @saarg's response, as an owner of a X10SDV-TLN4F (Supermicro), the most we can realistically get with ipmi fan control would be what ipmi itself can control: Unless someone hasn't already offered though, and if @StevenD doesn't have the board above, please bother me as much as you can if you need the raw ipmi values for my board as I would like to have fan control (even if it's only changing the values above) from unRAID -- pretty certain that my values will be very similar if not the same to other Supermicro boards, even outside of the X10 line. Anyways, the only other thing that can precisely control the fans on most Supermicro boards to a granular level would be a fan controller -- I make use of a Corsair Commander Mini on my desktop, which supports PWM fans to a certain degree (some Noctua fans have trouble with 'hopping' -- when the controller thinks the fan is running too low). The only problem with the product above is that Linux support is non-existent -- so you either need a Windows VM or similar setup. Some progress has been made though. As a separate note, if you are having issues with hopping on your Supermicro board, you can set the lower threshold with the ipmi tool. For the plugin developer: Awesome plugin! Great to have for those with IPMI -- first thing I look at when I get on my unRAID box. I have noticed one little bug that currently requires me to re-install the plugin. The effects of the bug; it will only be able to read a single sensor from ipmi. It usually presents itself after power cycling the unRAID box from a full shutdown, though it doesn't happen every time. One thing I can link to it is that the SNMP plugin I have installed would show in the failed plugins tab (or whatever it's called, the tab is usually hidden). Re-installing both plugins brings them both to working condition -- so I'm wondering if there is some sort of conflict. In closing; here is a great post on STH when it comes to IPMI and some raw values to play with~ You might want to take a double take at this part though: You know what that means