October 14Oct 14 The earlier plugin allowed setting the network LED based of the link speed (10M/100M/1G/2.5G/10G) with customizable colors. I thought that was cool and I used it.
October 14Oct 14 3 hours ago, lsaranto said:The earlier plugin allowed setting the network LED based of the link speed (10M/100M/1G/2.5G/10G) with customizable colors. I thought that was cool and I used it.Quick question: Apart from it being cool (I do no doubt that and thought about it the same way, assuming you speak about the deprecated plugin by ich777), your comment made me wonder if there are operation scenarios where the change of colors due to different network speeds gives the admin/user a real information advantage. At least I do not know any set-ups where the link speed is changing a lot/regularly (and I could detect the change by a quick glance on the according led) and when testing equipment I would rather check it via a desktop computer or laptop than plugging in and out of a server with potentially spinning disks and running applications.
October 15Oct 15 Author 11 hours ago, lsaranto said:The earlier plugin allowed setting the network LED based of the link speed (10M/100M/1G/2.5G/10G) with customizable colors. I thought that was cool and I used it.Thanks for the idea, lsaranto – the link-speed colour is in (version 0.22.1, Plugins → Check for Updates).Where: LED settings → card “Network LED” → “Network LED by link speed”. It gives each speed its own colour (10M, 100M, 1G, 2.5G, 5G, 10G), all changeable, and it’s off by default.On top of that, the case picture and the dashboard tile now draw the network ports next to the LAN LED as RJ45 sockets: a connected port in the colour of its speed with “2.5G”, “10G” and so on, and a port without a link as a dimmed socket with a cross and the speed it supports.@ivolution – to your question: a real use is a cable or port that only negotiates 1G instead of 2.5G or 10G. That often goes unnoticed for years, and a different LED colour shows it at a glance.
October 15Oct 15 Hi Schubi05,Just a quick thanks for the big improvement done your plugin, I was a former user of ich777 plugin and really all the customization available in yours are amazing !All working well on DXP4800 Plus.I hope it will be published soon in the Community plugins so more people can discover it !
October 15Oct 15 5 hours ago, Schubi05 said:@ivolution – to your question: a real use is a cable or port that only negotiates 1G instead of 2.5G or 10G. That often goes unnoticed for years, and a different LED colour shows it at a glance.Thanks - that was one of the use cases I thought of (and also assumed I have described) and for me it was just unimaginable that users who are sufficiently interested in the link speed would actually "test"/confirm their setup via the network led instead of what the (Unraid) OS shows them via the WebGUI. So I think it was rather a lack of imagination or a strict view on how it makes more sense (to me!) to test that - solely on my end! 😅
October 15Oct 15 This plugin is awesome so thank you for the work you've put into it.I recently moved to a DXP6800 Pro and this plugin alone made it so much better.I had an issue where the wrong lights would light up but that was an issue on my side, i had to physically re arrange the hard drives to the correct bays.
October 15Oct 15 9 hours ago, Schubi05 said:Where: LED settings → card “Network LED” → “Network LED by link speed”. It gives each speed its own colour (10M, 100M, 1G, 2.5G, 5G, 10G), all changeable, and it’s off by default.First of all: great plugin, I really enjoy it!The LED-by-link feature however does not work on my DXP4800 Plus. Upon activation, the network LED just stays in its default color and does not adapt to the link speed as configured, neither in the overview window nor on the chassis itself. Do you have any idea what might be causing this?
October 15Oct 15 13 minutes ago, hsf said:... Upon activation, the network LED just stays in its default color and does not adapt to the link speed as configured, neither in the overview window nor on the chassis itself. Do you have any idea what might be causing this?I am not the plugin author, but in the past when I reported errors, more information nearly always helped the author to identify the issue faster/easier.Questions that came up for me:What version of Unraid is your machine running?Any other observation? E.g. did this feature work properly in ich777's plugin before (in case you used that before)?Feedback from my end (with a DXP4800 Plus and Unraid 7.3.3): No issues, works as I expect it to work.
October 16Oct 16 18 hours ago, ivolution said:Questions that came up for me:Thanks for the tip - I could have thought of that myself.I'm using Unraid 7.3.3 and yes, ich777's plugin was previously installed. I just found out today that the old plugin already offered this feature, but it didn't work with that one either (the LED stayed white the whole time, even though it should have been yellow since I'm using 2.5 Gbps LAN). With Schubi05's UGREEN LED Control plugin, the following features work for me:Manually setting the LEDs' colorsStatic/Breathe/Pulse/off settings plus the Rainbow/Temperature effectsWhat doesn't work for me:Network LED by link speed (just stays at the color manually set)Disks in standby: Dimmed/Normal/Off/Pulse slowly (LEDs just stay at the color manually set)Not tested yet: Color change on SMART warnings and parity checks.I'm a bit at a loss as to how I can get to the bottom of the cause.
October 16Oct 16 Author 22 minutes ago, hsf said:Thanks for the tip - I could have thought of that myself.I'm using Unraid 7.3.3 and yes, ich777's plugin was previously installed. I just found out today that the old plugin already offered this feature, but it didn't work with that one either (the LED stayed white the whole time, even though it should have been yellow since I'm using 2.5 Gbps LAN).With Schubi05's UGREEN LED Control plugin, the following features work for me:Manually setting the LEDs' colorsStatic/Breathe/Pulse/off settings plus the Rainbow/Temperature effectsWhat doesn't work for me:Network LED by link speed (just stays at the color manually set)Disks in standby: Dimmed/Normal/Off/Pulse slowly (LEDs just stay at the color manually set)Not tested yet: Color change on SMART warnings and parity checks.I'm a bit at a loss as to how I can get to the bottom of the cause.Thanks for the detailed list, hsf. Both things that don’t work for you (network LED by link speed, and the standby look of the disks) are done by the status daemon, while the manual colours and effects are written once directly to the LEDs. So my first guess is that the daemon isn’t running for you. Two possible reasons:The default mode is still “Manual”. Under Overview, set the default mode to “Status-based”.A leftover of ich777’s plugin is still running and the daemon steps aside for it (it logs “ugreenleds-driver monitor is running”).Could you run this in the Unraid terminal and paste the result?/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl status | grep -E '"mode"|daemon|netdev|network_ports'pgrep -af ugreen-ledslsmod | grep -i ugreengrep ugreen-led-control /var/log/syslog | tail -15
October 16Oct 16 Hi,I have this startup script installed on my DXP-480T Plus on Unraid 7.4.0-RC1. It seems not to work, the LED remains in blinking status. The Plugin is installed.#!/bin/bashI2C_DEV=$(i2cdetect -l | grep "SMBus I801 adapter" | grep -Po "i2c-\d+" | cut -d'-' -f2)modprobe -v i2c-devi2cset -y ${I2C_DEV} 0x26 0xa0 1 b # red offi2cset -y ${I2C_DEV} 0x26 0xa0 2 b # white offi2cset -y ${I2C_DEV} 0x26 0xb1 2 b # white oni2cset -y ${I2C_DEV} 0x26 0x51 0 b # slow flash offi2cset -y ${I2C_DEV} 0x26 0x50 0 b # permanently onDo you have any ideas?Thx and bestdatarepos Edited October 16Oct 16 by datarepos
October 16Oct 16 Author 41 minutes ago, datarepos said:Hi,I have this startup script installed on my DXP-480T Plus on Unraid 7.4.0-RC1. It seems not to work, the LED remains in blinking status. The Plugin is installed.#!/bin/bashI2C_DEV=$(i2cdetect -l | grep "SMBus I801 adapter" | grep -Po "i2c-\d+" | cut -d'-' -f2)modprobe -v i2c-devi2cset -y ${I2C_DEV} 0x26 0xa0 1 b # red offi2cset -y ${I2C_DEV} 0x26 0xa0 2 b # white offi2cset -y ${I2C_DEV} 0x26 0xb1 2 b # white oni2cset -y ${I2C_DEV} 0x26 0x51 0 b # slow flash offi2cset -y ${I2C_DEV} 0x26 0x50 0 b # permanently onDo you have any ideas?Thx and bestdatareposHi datarepos, thanks for the details. I haven’t been able to test the DXP480T Plus myself, so I need a bit of data to see what your LED controller looks like. Could you run these in the Unraid terminal and paste the output?/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl smbus/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c probei2cdetect -li2cdetect -y $(i2cdetect -l | grep "SMBus I801" | grep -Po "i2c-\K\d+")And two questions: where does the script run (User Scripts “At first array start”, or the go file?) and is the plugin’s page showing the controller as found? Two possible reasons for the blinking: the script runs before the SMBus driver is loaded (then I2C_DEV is empty), or the plugin writes the LED again afterwards. The output will tell which.If the controller at 0x3a answers, you could simply set the power LED in the plugin (colour, static) instead of the script.
October 16Oct 16 4 hours ago, Schubi05 said:The default mode is still “Manual”. Under Overview, set the default mode to “Status-based”.Thank you very much - that did the trick. Unfortunately, I completely missed that option.
October 17Oct 17 I'm having trouble getting UGREEN LED Control to work on my DXP2800 running Unraid 7.3.3.The plugin installs successfully and correctly identifies the NAS model, but it cannot detect or control any LEDs.System information:Hardware version: EM_DXP2800_SUB2_V1.0.27Kernel: 6.18.54-Unraid{ "ok": true, "model": "DXP2800", "bays": 2, "controller": "ugreen-led-i2c", "i2c_bus": null, "i2c_address": null, "leds": [] }Manual controller probe:{ "address": "0x3a", "bus": "/dev/i2c-0", "leds": null } ERROR: no LED answered on /dev/i2c-0The SMBus adapter is detected correctly:SMBus I801 adapter at 0000:00:1f.4The required kernel modules (i2c_dev, i2c_i801, i2c_smbus) are loaded.The system log also reports:[UGREEN LED Control] WARNING: The LED controller does not answer on the SMBus; no LEDs available.Troubleshooting performed:Updated Unraid to 7.3.3.Updated UGREEN LED Control.Verified the SMBus adapter and kernel modules.Tested the controller manually using /dev/i2c-0.Checked for conflicting LED plugins and leftover startup scripts.Confirmed that no other UGREEN LED driver is currently loaded.Unfortunately, none of these steps resolved the issue.I'd appreciate any suggestions or additional diagnostic steps that could help identify the problem.Thanks for your work on the plugin!
October 17Oct 17 Author 2 hours ago, d4nnmuerte said:I'm having trouble getting UGREEN LED Control to work on my DXP2800 running Unraid 7.3.3.The plugin installs successfully and correctly identifies the NAS model, but it cannot detect or control any LEDs.System information:Hardware version: EM_DXP2800_SUB2_V1.0.27Kernel: 6.18.54-Unraid{ "ok": true, "model": "DXP2800", "bays": 2, "controller": "ugreen-led-i2c", "i2c_bus": null, "i2c_address": null, "leds": [] }Manual controller probe:{ "address": "0x3a", "bus": "/dev/i2c-0", "leds": null } ERROR: no LED answered on /dev/i2c-0The SMBus adapter is detected correctly:SMBus I801 adapter at 0000:00:1f.4The required kernel modules (i2c_dev, i2c_i801, i2c_smbus) are loaded.The system log also reports:[UGREEN LED Control] WARNING: The LED controller does not answer on the SMBus; no LEDs available.Troubleshooting performed:Updated Unraid to 7.3.3.Updated UGREEN LED Control.Verified the SMBus adapter and kernel modules.Tested the controller manually using /dev/i2c-0.Checked for conflicting LED plugins and leftover startup scripts.Confirmed that no other UGREEN LED driver is currently loaded.Unfortunately, none of these steps resolved the issue.I'd appreciate any suggestions or additional diagnostic steps that could help identify the problem.Thanks for your work on the plugin!Hi d4nnmuerte, thanks for the very complete report, that saves a lot of back and forth. The SMBus and modules are fine, so this looks like a hardware revision where the LED controller isn’t at 0x3a (the DXP2800 V1.2 board is already known to be different, and I haven’t seen your revision yet). To find out where it is, could you run this in the Unraid terminal and paste the output?i2cdetect -l for b in $(i2cdetect -l | grep -Po 'i2c-\K\d+'); do echo "== bus $b"; i2cdetect -y $b; done dmidecode -s baseboard-manufacturer; dmidecode -s baseboard-product-name; dmidecode -s baseboard-version; dmidecode -s bios-versionPlease also tell me what the LEDs do right now (power LED colour and whether it blinks, any disk LEDs lit). If an address other than 0x3a shows up, I can try it; I’d need you to test carefully, because I can’t test your board myself.
October 17Oct 17 On 10/16/2026 at 5:24 PM, Schubi05 said:Hi datarepos, thanks for the details. I haven’t been able to test the DXP480T Plus myself, so I need a bit of data to see what your LED controller looks like.Could you run these in the Unraid terminal and paste the output?/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl smbus/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c probei2cdetect -li2cdetect -y $(i2cdetect -l | grep "SMBus I801" | grep -Po "i2c-\K\d+")And two questions: where does the script run (User Scripts “At first array start”, or the go file?) and is the plugin’s page showing the controller as found? Two possible reasons for the blinking: the script runs before the SMBus driver is loaded (then I2C_DEV is empty), or the plugin writes the LED again afterwards. The output will tell which.If the controller at 0x3a answers, you could simply set the power LED in the plugin (colour, static) instead of the script.Hi,here ist my terminal output:# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl smbus/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c probei2cdetect -li2cdetect -y $(i2cdetect -l | grep "SMBus I801" | grep -Po "i2c-\K\d+")SMBus adapter: /sys/bus/i2c/devices/i2c-0/name:SMBus I801 adapter at 0000:00:1f.4{ "address": "0x3a", "bus": "/dev/i2c-0", "leds": null}ERROR: no LED answered on /dev/i2c-0-bash: i2cdetect: command not found-bash: i2cdetect: command not found-bash: i2cdetect: command not foundThe script ist configured to run at first start of array. But the blinking also does not stop when i run the script manually after everything is started. A screenshit from the plugin is attached.Many thanks for you support! Best datarepos
Sunday at 07:44 AM5 days Author 11 hours ago, datarepos said:Hi,here ist my terminal output:# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl smbus/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c probei2cdetect -li2cdetect -y $(i2cdetect -l | grep "SMBus I801" | grep -Po "i2c-\K\d+")SMBus adapter: /sys/bus/i2c/devices/i2c-0/name:SMBus I801 adapter at 0000:00:1f.4{"address": "0x3a","bus": "/dev/i2c-0","leds": null}ERROR: no LED answered on /dev/i2c-0-bash: i2cdetect: command not found-bash: i2cdetect: command not found-bash: i2cdetect: command not foundThe script ist configured to run at first start of array. But the blinking also does not stop when i run the script manually after everything is started. A screenshit from the plugin is attached.Many thanks for you support! Best datareposThanks again, datarepos. I looked at ich777’s plugin: your script is exactly what he runs for the DXP480T Plus (the dxp480t_static function), and it needs the i2c-tools package that his plugin shipped. Since that plugin is deprecated and you’ve removed it, i2cset is gone, which is why the LED keeps blinking.I’ll add native support for the DXP480T to my plugin: it will set the power LED to static white by itself, without any script or extra packages. I’ll ask you to test it once it’s ready, since I don’t have this model.New Update 0.23.0 sets the DXP480T Plus power LED to static white by itself at boot (no script or i2c-tools needed; it uses the same register writes as ich777’s driver). Please update, remove your startup script, reboot and tell me if the LED stops blinking. If it doesn’t, please run /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c dxp480t white; echo $? and /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c scan all and paste the output.
Sunday at 06:51 PM5 days Hi Schubi05,thank you your plugin!I just tested it on a DXP480T Plus (after uninstalling ich777's first + reboot) and the LED is staying white as intended. 🙂 Edited Sunday at 06:51 PM5 days by Squirt6346
Sunday at 10:32 PM5 days Author Thanks a lot for testing, @Squirt6346, that’s exactly what I hoped for, as I can’t try this model myself. Good to know the DXP480T Plus works without any script or extra packages.@datarepos, same for you: update to 0.23.0, remove your startup script and reboot. If the LED still blinks, the two commands above would show why.
Monday at 07:22 PM4 days On 10/18/2026 at 9:44 AM, Schubi05 said:Thanks again, datarepos.I looked at ich777’s plugin: your script is exactly what he runs for the DXP480T Plus (the dxp480t_static function), and it needs the i2c-tools package that his plugin shipped. Since that plugin is deprecated and you’ve removed it, i2cset is gone, which is why the LED keeps blinking.I’ll add native support for the DXP480T to my plugin: it will set the power LED to static white by itself, without any script or extra packages. I’ll ask you to test it once it’s ready, since I don’t have this model.New Update 0.23.0 sets the DXP480T Plus power LED to static white by itself at boot (no script or i2c-tools needed; it uses the same register writes as ich777’s driver).Please update, remove your startup script, reboot and tell me if the LED stops blinking.If it doesn’t, please run/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c dxp480t white; echo $?and/usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c scan alland paste the output.Hi Schubi05,Thank you for this quick update.After disabling the script and installing version 0.23.0, the LED stays on continuously after a reboot and no longer flashes. The color is now orange; previously, it was always white.Bestdatarepos
1 hour ago1 hr Any plans to support the iDX6011 Pro or variants? It almost works as-is. It's detecting the NAS, but it's listing 8 drive bays instead of the 6 that are actually there. It also doesn't reset the "MCU hardware marquee" where it cycles the drive bay LEDs 1 through 6 when you don't have UGOS running. There's a specific iDX6011 plugin, (GitHub) but it doesn't have the beautiful GUI you've created. I also realize the output below says 8 bays, but that's not actually true. My drives are in bays 1 and 2, and your plugin shows them in 3 and 4. Also, it can read the LED status because it reflects the drive bay LEDs cycling accurately.This is what Google claims: The standard ugreen-led-control plugin communicates via the "DXP-style" protocol (i2c_smbus_write_i2c_block_data), whereas your iDX 6011 Pro requires a strict SMBus block-write protocol with a count byte to break out of the MCU hardware marquee.Output of the commands:root@Unraid:~# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl status { "ok": true, "foreign_monitor": false, "model": "iDX6011 Pro", "bays": 8, "kernel": "6.18.58-Unraid", "mapping": "guessed", "mode": "manual", "daemon": false, "fx": "", "fx_leds": "", "identify": [], "sync_action": "", "sync_percent": 0, "sync_enabled": true, "sync_color": "0 120 255", "standby_mode": "dim", "standby_level": 30, "smart_enabled": true, "error_enabled": true, "activity_enabled": true, "smart_color": "255 140 0", "disk_color_mode": "own", "netdev_status": "activity", "alert_enabled": false, "alert_level": "warning", "alert_color": "255 59 48", "shutdown_blink": true, "shutdown_color": "255 140 0", "shutdown_effect": "blink", "alert_count": 1, "alert_active": false, "fx_speed": 2, "fx_reverse": false, "fx_idle": false, "night": false, "disk_error_color": "255 59 48", "saved_brightness": {}, "network_device": "eth0", "netdev_speed": 2500, "network_ports": [{"name": "eth0", "link": true, "speed": 2500, "max": 10000}, {"name": "eth1", "link": false, "speed": 0, "max": 10000}], "netdev_speed_enabled": false, "netdev_speed_colors": {"10": "255 59 48", "100": "255 140 0", "1000": "255 214 10", "2500": "0 200 83", "5000": "0 200 200", "10000": "0 120 255"}, "controller": "ugreen-led-i2c", "i2c_bus": 0, "i2c_address": "0x3a", "leds": ["power", "netdev", "disk1", "disk2", "disk3", "disk4", "disk5", "disk6", "disk7", "disk8"] }root@Unraid:~# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl smbus SMBus adapter: /sys/bus/i2c/devices/i2c-0/name:SMBus I801 adapter at 0000:00:1f.4root@Unraid:~# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c probe { "address": "0x3a", "bus": "/dev/i2c-0", "leds": [ "power", "netdev", "disk1", "disk2", "disk3", "disk5", "disk6", "disk7", "disk8" ] } Edited 1 hour ago1 hr by arcmodo Added detail about it reading the LED status and displaying it in the GUI.
16 minutes ago16 min Author 1 hour ago, arcmodo said:Any plans to support the iDX6011 Pro or variants? It almost works as-is. It's detecting the NAS, but it's listing 8 drive bays instead of the 6 that are actually there. It also doesn't reset the "MCU hardware marquee" where it cycles the drive bay LEDs 1 through 6 when you don't have UGOS running. There's a specific iDX6011 plugin, (GitHub) but it doesn't have the beautiful GUI you've created. I also realize the output below says 8 bays, but that's not actually true. My drives are in bays 1 and 2, and your plugin shows them in 3 and 4. Also, it can read the LED status because it reflects the drive bay LEDs cycling accurately.This is what Google claims: The standard ugreen-led-control plugin communicates via the "DXP-style" protocol (i2c_smbus_write_i2c_block_data), whereas your iDX 6011 Pro requires a strict SMBus block-write protocol with a count byte to break out of the MCU hardware marquee.Output of the commands:root@Unraid:~# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl status { "ok": true, "foreign_monitor": false, "model": "iDX6011 Pro", "bays": 8, "kernel": "6.18.58-Unraid", "mapping": "guessed", "mode": "manual", "daemon": false, "fx": "", "fx_leds": "", "identify": [], "sync_action": "", "sync_percent": 0, "sync_enabled": true, "sync_color": "0 120 255", "standby_mode": "dim", "standby_level": 30, "smart_enabled": true, "error_enabled": true, "activity_enabled": true, "smart_color": "255 140 0", "disk_color_mode": "own", "netdev_status": "activity", "alert_enabled": false, "alert_level": "warning", "alert_color": "255 59 48", "shutdown_blink": true, "shutdown_color": "255 140 0", "shutdown_effect": "blink", "alert_count": 1, "alert_active": false, "fx_speed": 2, "fx_reverse": false, "fx_idle": false, "night": false, "disk_error_color": "255 59 48", "saved_brightness": {}, "network_device": "eth0", "netdev_speed": 2500, "network_ports": [{"name": "eth0", "link": true, "speed": 2500, "max": 10000}, {"name": "eth1", "link": false, "speed": 0, "max": 10000}], "netdev_speed_enabled": false, "netdev_speed_colors": {"10": "255 59 48", "100": "255 140 0", "1000": "255 214 10", "2500": "0 200 83", "5000": "0 200 200", "10000": "0 120 255"}, "controller": "ugreen-led-i2c", "i2c_bus": 0, "i2c_address": "0x3a", "leds": ["power", "netdev", "disk1", "disk2", "disk3", "disk4", "disk5", "disk6", "disk7", "disk8"] }root@Unraid:~# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl smbus SMBus adapter: /sys/bus/i2c/devices/i2c-0/name:SMBus I801 adapter at 0000:00:1f.4root@Unraid:~# /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-i2c probe { "address": "0x3a", "bus": "/dev/i2c-0", "leds": [ "power", "netdev", "disk1", "disk2", "disk3", "disk5", "disk6", "disk7", "disk8" ] }Thanks for the detailed report, arcmodo, and for the output. I looked at how the vendor driver and the other iDX6011 plugins talk to your MCU and built it in: six bays, the LED registers of the Pro (two LAN LEDs, so disk1 is register 3), the SMBus-block frames, and the bay numbers by SATA controller (ASMedia ports are bays 1-4, Intel ports 5-6, which fits what you saw). It's version 0.25.0, which I can't test myself. Could you update and tell me: (1) are your two drives now in bays 1 and 2? (2) do the LED colours you set show up on the right bays, and does the lighting marquee stop? (3) if something is wrong: the output of /usr/local/emhttp/plugins/ugreen-led-control/backend/ugreen-led-ctl status and which LED lit up when you pressed "Identify" on bay 1.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.