When I followed the guide in the updatefirmware/README.md to customize keybinds, it unfortunately broke all RGB toggling/control for me on the device. My assumption is the device shipped with some custom firmware that using the update flow overwrites. Even attempting to restore to defaults through QMK did not fix it.
I managed to get it working again by following the QMK build guide for newbies and spelunking in the old commits for the default keymaps for the leafcutterlabs/bigknob keyboard. In particular for default/keymaps.c and the (now removed) default/rules.mk.
I added these in my personal fork of the qmk_firmware repo in case it's useful for others to see: leafcutterlabs/bigknob/keymaps/with_tapdance.
I can PR this to the QMK repo if the devs here think it's a good idea; holding off in case all that was removed for a reason and should not be added back.
When I followed the guide in the
updatefirmware/README.mdto customize keybinds, it unfortunately broke all RGB toggling/control for me on the device. My assumption is the device shipped with some custom firmware that using the update flow overwrites. Even attempting to restore to defaults through QMK did not fix it.I managed to get it working again by following the QMK build guide for newbies and spelunking in the old commits for the default keymaps for the
leafcutterlabs/bigknobkeyboard. In particular fordefault/keymaps.cand the (now removed)default/rules.mk.I added these in my personal fork of the qmk_firmware repo in case it's useful for others to see:
leafcutterlabs/bigknob/keymaps/with_tapdance.I can PR this to the QMK repo if the devs here think it's a good idea; holding off in case all that was removed for a reason and should not be added back.