That’s not correlated - if a drive isn’t accessed for 15 mins it should spin down.
The suspend mode won’t impact that.
Sam
So… what is story now with LED… is settings added under v21.1 update?
If not, please give me instruction how to disable LED light completly, so make it allways OFF.
Tape, black tape does the job for me.
1 Like
Not a solution as SW update was promised to be done. Tape is quite guru solution - let’s say solution which is tape and not real solution…
Not sure where that was promised. Controlling the level of brightness as I mentioned above via PWM would be a hardware change.
The LED can already be controlled via software. To enable:
echo 1 | sudo tee /sys/class/leds/standby/brightness
To disable:
echo 1 | sudo tee /sys/class/leds/standby/brightness
1 Like
That can be done, but it’s low priority at the moment.
I thought you wanted to adjust the level of brightness on the LED. That isn’t something we could do with the current hardware.
Only option to disable it completly or to have option to be as-is mode or reversalbe option (to be on when is powered)…
Or is the same command echo 1 both time?
I don’t want to make it that complicated
Based on some Kodi settings 
3 options for LED do not seems to complicated for users…
If we expose the setting to Kodi, Kodi will need to be running for LED behaviour to be affected – it wouldn’t actually be system wide.
So I think it needs more thought
This settings should be in My OSMC menu based on HW (if Vero V - setting is enabled, otherwise simply disable setting)…
Just my proposal…
We don’t have a dedicated menu for Vero V in My OSMC. It might be odd to do that for a single setting. I will give it some thought.
I tested command and this only do reverse logic. I want to be LED off when Vero V is off and to be LED off when Vero V is on… so LEDs allways OFF…
For now, you can make it immutable and it will not toggle.
Thank you. For me this is OK. Please, can you give me the command.
Actually, it’s probably not possible with sysfs, otherwise I would have recommended sudo chattr +i /sys/class/leds/standby/brightness
Instead, you can use custom wake / sleep scripts for now. See [HOWTO] Vero 4K / 4K+ / Vero V: Performing actions programatically on Standby and Wakeup for an example. You can run any commands you want when the device is suspended / woken up.
As one of the people that wanted the blue led behavior to simply be reversed (on when the device is on and off when the device is in standby), I have pieced together from the various suggestions and links to other threads how to possibly do that and have come up with the following which has achieved my desired behavior.
Here is what I did…
Created a file called “wake.py” that contains the text:
import os
os.system(‘/bin/bash -c “echo “1” | sudo tee /sys/class/leds/standby/brightness”’)
Created a second file called “standby.py” that contains the text:
import os
os.system(‘/bin/bash -c “echo “0” | sudo tee /sys/class/leds/standby/brightness”’)
Both of these files were saved on the Vero V in the /home/osmc/.kodi/userdata/ folder. Please note that I did not already have wake and standby files so you may need to incorporate the above text into those files if they already exist, as opposed to replacing them.
So far the behavior is as expected. When you initially start up the Vero or reboot it, the light will initially be off (even though the Vero is in the ON state) as the Vero hasn’t actually awoken from the STANDBY state. However, once it first enters the STANDBY state and thereafter, the led behavior is as expected.
I will be the first to admit, I have no idea what those commands mean. I just picked the code from other threads and melded it with what Sam has stated above. If someone knows a more elegant way, I’m certainly open to it.
1 Like
So… this make LED OFF on wake mode and on standby mode? Do I understand correctly?
No that is already the default behaviour. It does the opposite