Disobey 2019 Badge
A Finnish Disobey badge with ESP32 MicroPython, Hatchery apps, puzzle pointers, screen, buzzer, IR, buttons, and RGB LEDs around the PCB outline.
Country dossier
Worldwide badge coverage for Finland, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.
Seeded artifacts
A Finnish Disobey badge with ESP32 MicroPython, Hatchery apps, puzzle pointers, screen, buzzer, IR, buttons, and RGB LEDs around the PCB outline.
A Disobey badge operated by artwork-hidden Game Boy inspired touch buttons, serial shell, Hatchery apps, nickname settings, and WiFi configuration.
A Finnish Disobey badge built around ESP32-S3, a 1.9-inch TFT display, SK6812MINI RGB LEDs, joystick/buttons, MicroPython game firmware, OTA setup, web flashing, badge competitions, and a public hardware/firmware repository.
Events
A Finnish event badge with ESP32 MicroPython, Hatchery apps, LEDs, screen, buzzer, IR, and puzzle pointers.
A Disobey badge with touch-button navigation, serial shell, Hatchery app installation, WiFi configuration, and text input.
The February 13-14, 2026 Disobey edition in Helsinki whose official badge page documents the delayed 2025/2026 ESP32-S3 badge, OTA setup, competition workflow, and public firmware/hardware archive.
Lifecycle
The badge page describes social-game firmware for badge-to-badge duels and asks miniapp authors to submit pull requests so apps can be built into shared firmware.
The badge exposed a 115200 8n1 serial menu for starting apps or dropping into a Python shell, plus a START-on-boot recovery path to restore the homescreen as the default app.
The official page documents a second CTF firmware path and a flashing station near the CTF area, with source release promised after the event.
The competition rules solicit hardware mods, 3D models, apps, games, and standalone firmware for the badge, and list public hardware-mod submissions.
The Disobey 2019 badge firmware contained pointers used as part of the event's hacker puzzle competition.
Badges shipped with minimal firmware for hardware testing and OTA update; the official page documents event-WiFi provisioning and a web-flash fallback if OTA failed.
Badge.Team preserved MicroPython examples for outline RGB LEDs, buttons, power saving, buzzer tones, screen rotation, raw touch reads, and virtual timers; the hardware also exposed infrared transmit and receive.
The hardware docs document ESP32-S3 WROOM-2, a 1.9-inch ER-TFT019-1 display, SK6812MINI RGB LEDs, joystick/buttons, GPIO mapping, schematic v11, and STEP mechanical model references.
The official badge page lists public Best Hardware Mod submissions, including 3D-printable battery holder and case approaches for carrying or protecting the badge.
The Disobey 2020 docs describe Gameboy-inspired touch buttons, a launcher opened with START, a nickname app, and an on-badge keyboard with input, cursor, and confirmation modes.
The official page links a post-event experiment for controlling extra addressable LEDs from the badge through WLED-style firmware work.
Disobey 2019 could download MicroPython applications from Hatchery once configured for WiFi.
Disobey 2020 exposed app installation and publishing through Hatchery and the badge's installer application.
The Rust repository documents badge examples including Breakout, Skyroads, Snake, Space Shooter, demoscene, shader, vector demo, display tests, LED bars, microphone, name-tag, scrolling, vibration, and async task-switch examples.
The MIT-licensed disobey2026badge crate and repository expose Rust APIs for the ST7789 display, nine GPIO buttons, WS2812 LEDs, display backlight, and vibration motor.
Operational history
The physical artifact has a documented handling caveat that belongs with the hardware record.
The catalogue keeps the CTF flashing-station workflow as source-backed event behavior while avoiding a false claim that the CTF firmware source has already been published.
The record uses the 2026 event edition while preserving the 2025/2026 naming split found in the badge URL and repository.
Post-event use depended on either successful event-time setup or manual reflashing.
Hatchery/app workflows depended on network context, so event-time and post-event behavior should be documented separately.
The record preserves the WLED-style extension idea while avoiding a claim that all badges shipped with that behavior or that it was part of the event firmware baseline.
The compendium should treat the preserved API examples as historical firmware behavior, not a guarantee for every reflashed device.
The catalogue can cite the competition workflow and hardware-mod entries, but should not claim a complete public miniapp archive until the official page or repository publishes it.
The Finnish record remains source-backed and image-free rather than copying Badge.Team page media, documentation screenshots, event photos, placeholders, or generated approximations.
The Finnish record remains source-backed and image-free rather than copying Badge.Team page media, documentation screenshots, event photos, placeholders, or generated approximations.
The Finnish record stays source-backed and image-free rather than copying official-page imagery, screenshots, social photos, or generated artwork.
Firmware and hardware facts can be sourced from the repository, but code-reuse and asset-reuse claims should not be collapsed into one blanket license statement.