# Model 100 example firmware breaks LED key

**URL:** <https://community.keyboard.io/t/model-100-example-firmware-breaks-led-key/13547>\
**Category:** Help and Getting Started\
**Tags:** question\
**Created:** [June 4, 2025, 8:03pm UTC](https://community.keyboard.io/t/model-100-example-firmware-breaks-led-key/13547 "2025-06-04T20:03:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vmladenov](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/vmladenov/32/5249_2.png) [@vmladenov](https://community.keyboard.io/u/vmladenov)\
**Post date:** [June 4, 2025, 8:03pm UTC](https://community.keyboard.io/t/model-100-example-firmware-breaks-led-key/13547/1 "2025-06-04T20:03:19Z")

</div>

Hi all, I have just followed this tutorial [Build and install the latest firmware for your keyboard — Kaleidoscope documentation](https://kaleidoscope.readthedocs.io/en/latest/build_default_firmware.html#Install-latest-firmware) 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

```auto
  // 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

```auto
  // 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?

---

<div class="post-metadata">

**Author:** ![nyarly](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/nyarly/32/3434_2.png) [@nyarly](https://community.keyboard.io/u/nyarly)\
**Post date:** [September 9, 2025, 4:06pm UTC](https://community.keyboard.io/t/model-100-example-firmware-breaks-led-key/13547/2 "2025-09-09T16:06:36Z")

</div>

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`