Minor firmware LED bug

[hendersj]

Just got my Launch Heavy yesterday and I love it - getting used to the keys being in a different place for home/pgup/pgdn/end etc is taking a little time (but it's < 24 hours since I unboxed and started using it, so I expect I'll get there easily).

One thing I noticed is when switching the LEDs in the keyboard configurator from "per-layer solid color" to "bound keys only", the default layer 1 keyboard layout loses the LED over the "Up" key. The key is bound, but it doesn't show as bound.

I just tested this by assigning something to it other than "reuse" in layer 2, and I see the same behavior.

In all other LED configurations, the LED works as expected - just the bound keys one where it turns off no matter what the key is set to do.

LMK what info is needed - should be easy to duplicate, I believe.

[leviport]

Thanks for the report! I've been able to confirm this one as well. It's probably something that has to be fixed in firmware, so I'll move this to our QMK fork repo.

[hendersj]

Excellent! I had looked for the firmware project but didn't find this one (or if I did, I didn't find an 'issues' tab). Either way, glad it's in the right place now and has been reproduced.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.