How can I make the keypad light up when numlock is enabled? It’s very annoying that I can’t know what state it’s in like I can with the caps lock LED.
I also noticed I can’t adjust the brightness of the keypad when Numlock is on.
Is fn exposed to software? My thought was I could use Autohotkey to do this.
I would buy an RGB keypad if that would let me do this but I want the markings which the macropad doesn’t have. I don’t even see a regular replacement keypad for sale by framework.
To control the back light on numpad press numlock 1 time and then enter if light does not turn on, press num lock again and then enter and back light turns on. Then you got 3 levels of brightness like the main keyboard has. 1 low, 2. medium, 3. Brightest. Pressing enter again turns back light off again. So once you got the brightness you want, press numlock again to prevent from pressing enter again and changing the back light.
That’s slightly easier than fn + enter at least. But my question was how can I make the backlight indicate numlock state since the backlight isn’t controllable per key like how pressing caps lock illuminates it.
Also I just found that fn + keyboard enter isn’t changing the backlight on the keyboard anymore.
To change back light on main keyboard that is FN and Space bar.
But yeah they forgot a numlock indicator 
Yes you’re right thank you. I also found this, doesn’t seem to let you map key combos though.
So how might I configure numlock to control the backlight. QMK seems like my best bet but if fn is exposed to software AHK will do. ChatGPT says most firmwares dont expose fn to software.
This would require some coding & getting into editing the open source firmware, qmk, which is in the keyboards. Search for more on qmk if you think you want to get into that, see what’s involved & learn how qmk works.
Fn is not an actual keycode. Not something keyboards are even able to send. Fn is always an internal function. But Fn isn’t really involed in this anyway.
I suppose fn could be programmed to send a ASCII or unicode control character in addition to everything else it does though and scripts in AHK etc could listen for that control code. Not unreasonable to think that every key on the keyboard should be configurable in software.
And I definitely will research how to configure QMK. I’m currently taking a C course at university so it would be a nice project.
The keyboard website does let you change what fn does after all.
How can I reset the keyboard to defaults? I can’t find an fn key to remap it after I changed it. I also messed up super by accident which was labeled lwin but that is not an option in the web page.
edit fixed it with
UF2 firmware method erase and then flashing the UF2 ansi firmware again
FWIW: I opened a support ticket to ask this question and if firmware could be updated. The answer was a clear NO and that it is not on the roadmap. I was surprised to see that a numlock indicator was missing as this is such a blatant oversight and could have been easily fixed. I am not sure why framework took such a weird decision and then not thinking it is important enough to improve.
Well if the hardware doesn’t support individual backlightable keys it makes sense that they wouldn’t think it’s worth it to update the firmware. Enabling the backlight for the whole keypad when NumLock is pressed is a pretty poor workaround. Just sucks that they went with the macropad instead of an RGB keypad. I suppose I could get standard keycaps for the macropad but it should be the other way around. Blank keys are a niche.
Now if the macropad instead had 7 segment displays or an LED matrix that would be worth something to me.
Could I put the black keypad caps on the macropad? It’s not a problem for me since I already have the keypad but no one should have to buy the macropad and then spend more for custom caps or get the keypad too.
I did a version of this:
Yeah, the indicator is the brightness level of the entire keypad, but it’s good enough for me. I also set Fedora to always start with num lock so I don’t have to worry about it as much since I almost never want it not on.