Model 100 example firmware breaks LED key

Help and Getting Started
1

Hi all, I have just followed this tutorial Build and install the latest firmware for your keyboard — Kaleidoscope documentation to get a sketch for my Model 100 built from

File > Examples > Kaleidoscope > Devices > Keyboardio > Model 100

The sketch compiled and uploaded, and the keyboard seems to work as expected for all the buttons I’ve tested – except for the “led” key which no longer cycles through the various LED states that it used to on the stock firmware. The leds just stay powered off.

I see some logic in the setup function

  // Unless configured otherwise with Chrysalis, we want to make sure that the
  // firmware starts with LED effects off. This avoids over-taxing devices that
  // don't have a lot of power to share with USB devices
  DefaultLEDModeConfig.activateLEDModeIfUnconfigured(&LEDOff);

but there are also other settings higher up

  // Set the rainbow effects to be reasonably bright, but low enough
  // to mitigate audible noise in some environments.
  LEDRainbowEffect.brightness(170);
  LEDRainbowWaveEffect.brightness(160);

which makes me think it is intended to work by default.

Is this known / expected?

2

Based on advice from Jesse, I used focus-send eeprom.erase which fixed the LEDs for me. It seems that if you’ve ever used Chrysalis, it puts configuration “on top” of the deployed firmware, which can be really confusing.

focus-send is in the Kaleidoscope repo in the bin/ directory, and is basically a wrapper around stty