-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Control LED - Causes Crash #59
Comments
Yep, sounds like a reasonable change. If you'd like to make a PR and test it on your device, we can merge that. |
What would you prefer me to do: |
I'd like to keep the LED function, but silently failing would be fine. If you think it's easy enough to add support for other devices, then it would be nice to get that included. |
I think the issue here is that in the latest PI os lite (Bullseye), the name of the "LED0" changes to "ACT". So need to change all the LED0 in the script to ACT to fix the issue. |
If it's a different Raspbian image (different version of Debian), then I'll be looking to update the project to use the latest version soon. |
I'm using Model: Raspberry Pi 3 Model B Rev 1.2
There are no LEDs listed under /sys/class/leds/, so I get:
When trying to run setup the remapper.service fails:
If I check the service, I can see it's due to the inability to control the LED:
It seems like it's a known problem and there's a different way to turn off the LED?
https://overflow.hostux.net/questions/19863723/turn-off-leds-of-raspberry-pi#71492090
https://github.com/seamusdemora/PiFormulae/blob/master/LEDControlForRPi.md
I believe it can be controlled via ACT:
It would be good if the LED thing was optional, I don't think it should crash the whole thing if it fails.
Update
For now I removed two lines from
bthidhub/install/on_rpi/remapper.service
Line 8 in 391044c
ExecStartPost=/usr/bin/bash -c 'echo none > /sys/class/leds/led0/trigger' ExecStopPost=/usr/bin/bash -c 'echo heartbeat > /sys/class/leds/led0/trigger'
Which allowed it to run, although I'm now getting this issue:
#55
The text was updated successfully, but these errors were encountered: