Dear all,
On Sunday 16 January 2011 16:44:07 Joachim Ott wrote:
> The LEDs are just off. In frameworkd.log I see:
> 2011.01.16 15:30:44.779 oeventsd.fso_triggers INFO Receive
> PowerStatus, status = full
> 2011.01.16 15:30:44.795 oeventsd ERROR DBus call
> returned an error
> 2011.01.16 15:30:44.802 oeventsd ERROR DBus call
> returned an error
>
> However, I'm able to set the LEDs by hand with
>
> mdbus2 -s org.freesmartphone.odeviced
> /org/freesmartphone/Device/LED/gta02orangepower
> org.freesmartphone.Device.LED.SetBrightness 100
I've investigated the issue a bit and have seen that it is based on rules.yaml
file:
root@om-gta02 /etc/freesmartphone/oevents # diff rules.yaml rules.yaml.sav
--- rules.yaml
+++ rules.yaml.sav
@@ -61,15 +61,15 @@
-
while: PowerStatus()
filters: HasAttr(status, "charging")
- actions: SetLed("gta02orangepower", "light")
+ actions: SetLed("gta02_orange_power", "light")
-
while: PowerStatus()
filters: HasAttr(status, "critical")
- actions: SetLed("gta02orangepower", "blink")
+ actions: SetLed("gta02_orange_power", "blink")
-
while: PowerStatus()
filters: HasAttr(status, "full")
- actions: SetLed("gta02bluepower", "light")
+ actions: SetLed("gta02_blue_power", "light")
-
trigger: PowerStatus()
filters: HasAttr(status, "empty")
With that setting LEDs are working again
Regards,
Sebastian
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user