Why It Mattered
It shows Badge.Team's platform crossing national communities and being used both as an event puzzle object and as a post-event MicroPython device.
Disobey 2019 · Finland · 2019
Disobey 2019 Badge
ESP32 MicroPython and puzzle badge
A Finnish Disobey badge with ESP32 MicroPython, Hatchery apps, puzzle pointers, screen, buzzer, IR, buttons, and RGB LEDs around the PCB outline.
EventDisobey 2019
SeriesBadge.Team Adjacent Events
LocationHelsinki
CountryFinland
People
Attribution Gap
No public individual author, designer, firmware, or team credits have been seeded for this badge yet. Add named credits only when a primary badge-team page, repository, talk, or other source identifies the people or team behind the work.
Hardware
Buttons, small backlit screen, buzzer, IR receiver/transmitter, ESP32, batteries, and multiple rear SMD RGB LEDs.
Software & Apps
Badge.Team MicroPython, USB serial at 115200 baud, OTA update, WiFi configuration, menu navigation, Python shell, Hatchery app installation, and hardware-specific APIs.
Lore
The first-boot WiFi window mattered: attendees who missed the event network had to manually reflash for post-event use.
Lifecycle
Add-ons & Upgrades
event puzzle content
historical
Puzzle pointers
The Disobey 2019 badge firmware contained pointers used as part of the event's hacker puzzle competition.
Source
hardware API surface
historical
RGB LED, IR, buzzer, and screen APIs
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.
Source
software add-on ecosystem
historical
Hatchery eggs
Disobey 2019 could download MicroPython applications from Hatchery once configured for WiFi.
SourceOperational history
Issues & Camp Impact
event-network dependency
note
The first boot expected the event WiFi named 'badge' with credentials hardcoded into firmware; missing that window required manual reflashing for post-event configuration.
Post-event use depended on either successful event-time setup or manual reflashing.
- Confidence
- primary docs
- Status
- historical
- Timeframe
- during and after event
- Source note
- Disobey 2019 Badge.Team docs.
firmware drift caveat
note
The programming API section says its hardware examples match the firmware flashed before and during Disobey 2019, and could have changed if the badge was later flashed with updated Badge.Team MicroPython.
The compendium should treat the preserved API examples as historical firmware behavior, not a guarantee for every reflashed device.
- Confidence
- primary docs
- Status
- documented caveat
- Timeframe
- post-event firmware updates
- Source note
- Disobey 2019 Badge.Team docs.
missing rights-cleared image
note
No Disobey 2019 badge image is published because the current Badge.Team source trail has not been paired with a reusable original badge photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.
The Finnish record remains source-backed and image-free rather than copying Badge.Team page media, documentation screenshots, event photos, placeholders, or generated approximations.
- Confidence
- local project policy
- Status
- needs licensed original replacement
- Timeframe
- current catalogue build
- Source note
- badge.gallery image policy and Disobey 2019 Badge.Team docs.