changing Pogoplug LED color

[permitivity]

There's an older thread on how to change the LED color, but the info seems outdated.

In Motion, there is a way to run a command when event starts, and run another command when motion event ends. I'd like to stick in a color change LED command (go green on start, go back to orange when event ends).

This thread does color changes, but runs it at the beginning based on some conditions I don't understand.
viewtopic.php?f=18&t=2101&start=10

[grayman4hire]

I've been meaning to give this script a test - http://gistflow.com/posts/741-control-t ... -linux-arm

If it works, please post back. Thanks

[calzon65]

Here are some commands you can play with if you want to build a script to control the LEDs. I am running the latest version of ArchLinuxARM and actually completed a full reinstall about a week ago. These settings all work on my PogoPlug V2, yes, I know the Orange LED is normally referred to as “:blue”, but on my system it’s “:orange”. This might be due to the fact that when I configured my system I set the machid to dd6 (fw_setenv machid dd6). So when I checked /sys/class/leds I was surprised to see ":orange" and ":green" versus ":blue" and ":green", or maybe the version of ArchLinuxARM was recently updated for the PogoPlug. In either case I don't know but I know these commands work on my PogoPlug V2.


Turn Orange LED off:
echo none > /sys/class/leds/status\:orange\:fault/trigger

Turn Orange LED on:
echo default-on > /sys/class/leds/status\:orange\:fault/trigger

Turn Orange LED blinking:
echo timer > /sys/class/leds/status\:orange\:fault/trigger

Turn Orange LED heartbeat:
echo heartbeat > /sys/class/leds/status\:orange\:fault/trigger

Turn Green LED off:
echo none > /sys/class/leds/status\:green\:health/trigger

Turn Green LED on:
echo default-on > /sys/class/leds/status\:green\:health/trigger

Turn Green LED blinking:
echo timer > /sys/class/leds/status\:green\:health/trigger

Turn Green LED heartbeat:
echo heartbeat > /sys/class/leds/status\:green\:health/trigger


Grayman4hire, to make your script work, I had to make some changes. Also, I don't understand the purpose of the [only] option.

$this->bbcode_second_pass_code('', '#!/bin/bash

usage()
{
echo "USAGE: led (all|orange|green) (off|on|blink|heartbeat|fs) [only]"
exit 1
}

switch()
{
echo "$2" > "/sys/class/leds/status:$1:$3/trigger"
}

if [ "$1" == "--help" ]; then
usage
fi

if [ "$3" == only ]; then
switch green none health
switch orange none fault
fi

case "$2" in
off) MSG="none" ;;
on) MSG="default-on" ;;
blink) MSG="timer" ;;
heartbeat) MSG="heartbeat" ;;
fs) MSG="mmc0" ;;
*) usage ;;
esac

case "$1" in
all) switch green "$MSG" health; switch orange "$MSG" fault ;;
orange) switch orange "$MSG" fault ;;
green) switch green "$MSG" health ;;
*) usage ;;
esac')

[grayman4hire]

@calzon65

Thanks for sharing! Just for clarification, that's not my script. Just something I found googling.

[calzon65]

Thanks for the clarification. I'm not sure what the original author intended with the only option, for now I will probably just delete it.

[permitivity]

$this->bbcode_second_pass_quote('calzon65', 'H')ere are some commands you can play with if you want to build a script to control the LEDs....

[calzon65]

Yes you can turn both on at the same time, but it's a bit hard to distinguish the "combined" color.

Here is the script with the [only] option removed:
$this->bbcode_second_pass_code('', '#!/bin/bash

usage()
{
echo "USAGE: led (all|orange|green) (off|on|blink|heartbeat|fs)"
exit 1
}

switch()
{
echo "$2" > "/sys/class/leds/status:$1:$3/trigger"
}

if [ "$1" == "--help" ]; then
usage
fi

case "$2" in
off) MSG="none" ;;
on) MSG="default-on" ;;
blink) MSG="timer" ;;
heartbeat) MSG="heartbeat" ;;
fs) MSG="mmc0" ;;
*) usage ;;
esac

case "$1" in
all) switch green "$MSG" health; switch orange "$MSG" fault ;;
orange) switch orange "$MSG" fault ;;
green) switch green "$MSG" health ;;
*) usage ;;
esac')

[grayman4hire]

Thanks for updating the script @calxon65!

@permitivity, I'm not in front of my pogoplug, so I can't tell you if this actually works, but try the below.

$this->bbcode_second_pass_code('', '
cd /usr/local/bin
wget http://dl.dropbox.com/u/42238/pogoplug/v2/led
chmod a+x led

led
led green blink
')

A little off topic, but is "/usr/local/bin" a good folder to store custom scripts/binaries?

My orange LED was call the "blue" led. If I went to "/sys/class/leds", I see

$this->bbcode_second_pass_quote('', 'p')lug:red:misc status:blue:health status:green:health

[calzon65]

It's strange the Orange LEDs being called "blue", but when I did a complete reinstall about a week ago, my Orange LEDs were also called blue at that time. I've run a few updates pacman -Syu after my complete reinstall, so all I can guess is that during one of the updates, something changed the name of my Orange LEDs in /sys/class/leds to actually be called "orange", I know I didn't change the name myself.

Running fw_setenv machid dd6 sets the correct machine ID to a PogoPlug v2 which makes the LED work properly after reboot. In essence, if you do a complete reinstall and don't set this, the PogoPlug LED will glow Orange after boot, setting the machine ID to dd6 makes the LED green after each reboot.

Maybe my setting the machine ID to dd6 followed by a few pacman -Syu over the past week captured some type of "update" that changed the name of my Orange LED from blue to orange because at that point, my system was "properly identified" as PogoPlug v2. I read a post from moonman saying with a fresh Arch install, the system (on a PogoPlug v2) thinks its a Sheeva Plug because the correct arcNumber is not properly initialized in the kernel, and maybe the Sheeve plug has a Green/Blue LED.

Anyway, after you run the fw_setenv machid dd6 I suggest rebooting then running a pacman -Syu, reboot, pacman -Syu again for grins, then check the name of your LED. I just don't want to go through yet another complete reinstallation to verify my theory.