[GH-ISSUE #284] [Request] Possibility to disable blinking LED toggled by ledWakePulse()? #129

Open
opened 2026-10-22 05:05:14 +00:00 by roman · 1 comment
Owner

Originally created by @DragRedSim on GitHub (Sep 10, 2026).
Original GitHub issue: https://github.com/safijari/openpuck/issues/284

Hi there,
I was wondering if there was the possibility of adding a feature to stop the LED status light that is used to debug wake commands from illuminating? I'm not referring to a charging LED, but rather the one mapped on the recommended nRF58240 board to P0.15 (inside status_led.cpp). Preferably this would be exposed as an option in the WebUI, though theoretically it could also be toggled via a button on a GPIO.

Originally created by @DragRedSim on GitHub (Sep 10, 2026). Original GitHub issue: https://github.com/safijari/openpuck/issues/284 Hi there, I was wondering if there was the possibility of adding a feature to stop the LED status light that is used to debug wake commands from illuminating? I'm not referring to a charging LED, but rather the one mapped on the recommended nRF58240 board to P0.15 (inside status_led.cpp). Preferably this would be exposed as an option in the WebUI, though theoretically it could also be toggled via a button on a GPIO.
Author
Owner

@DragRedSim commented on GitHub (Sep 16, 2026):

Looking a little closer into the behaviour, I’m noticing that my device is flashing at roughly two times a second, but in an inverse pattern to the suggested one of having the light on for half a second per pulse. So on second thoughts, rather than it being driven by an alternate code path as I originally thought, it may be that my board simply has the LED on the alternative activation scheme (active-high rather than active-low, or vice-versa).

<!-- gh-comment-id:5692130645 --> @DragRedSim commented on GitHub (Sep 16, 2026): Looking a little closer into the behaviour, I’m noticing that my device is flashing at roughly two times a second, but in an inverse pattern to the suggested one of having the light on for half a second per pulse. So on second thoughts, rather than it being driven by an alternate code path as I originally thought, it may be that my board simply has the LED on the alternative activation scheme (active-high rather than active-low, or vice-versa).
Sign in to join this conversation.
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
safijari/openpuck#129
No description provided.