From fadefcc748954cbdec436bf9f862a6aa5e82417d Mon Sep 17 00:00:00 2001
From: David Montero Crespo <davidmonterocrespo24@gmail.com>
Date: Mon, 17 Aug 2026 15:30:39 +0200
Subject: [PATCH] fix(examples): the Bluetooth LED example ignored every
 command
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

It printed "Bluetooth Control Ready" and then did nothing, no matter what
you sent — David typed `on` and `off` into the Serial Monitor and neither
reached it.

It reads UART(0), and on this port UART0 IS the REPL's channel: the code
runs through the raw REPL, so bytes typed into the monitor are consumed
there and uart.read() never sees them. `UART(0, 9600)` also retunes the
very port the monitor is talking to at 115200.

Upstream drives this from a phone through an HC-05, where "Bluetooth" is
only the transport and the ESP32 just sees serial. Velxio has no HC-05 on
the canvas, so the Serial Monitor is that link — read sys.stdin through a
select.poll (100 ms timeout, so the loop yields instead of spinning).

Verified in the app: `on` -> "Received: on / LED ON" with the LED lit,
`off` -> "Received: off / LED OFF" with it dark.
---
 frontend/src/data/examples-100-days.ts | 33 +++++++++++++++++++-------
 1 file changed, 24 insertions(+), 9 deletions(-)

diff --git a/frontend/src/data/examples-100-days.ts b/frontend/src/data/examples-100-days.ts
index c008a63e..aa4beb98 100644
--- a/frontend/src/data/examples-100-days.ts
+++ b/frontend/src/data/examples-100-days.ts
@@ -750,30 +750,45 @@ while True:
     boardType: "esp32",
     languageMode: 'micropython',
     files: [
-      { name: "main.py", content: `from machine import Pin, UART
+      { name: "main.py", content: `from machine import Pin
+import sys
+import select
 
-uart = UART(0, 9600)
-# There is no named "LED" pin on this port — GPIO2 is the DevKit v1 onboard
-# LED position, and the Velxio canvas wires an LED + 220R there.
+# Upstream drives this from a phone over an HC-05, which reaches the ESP32 as
+# plain serial — the "Bluetooth" part is just the transport. Velxio has no HC-05
+# on the canvas, so the Serial Monitor IS that link: type \`on\` / \`off\` into it.
+#
+# It has to be sys.stdin rather than UART(0). UART0 is the REPL's own channel on
+# this port, so bytes typed into the monitor are consumed by the REPL and
+# uart.read() never sees them — and \`UART(0, 9600)\` also retunes the very port
+# the monitor is talking to at 115200. The example looked alive (it printed
+# "Bluetooth Control Ready") and then ignored every command.
+#
+# There is no named "LED" pin on this port — GPIO2 is the DevKit v1 onboard LED
+# position, and the Velxio canvas wires an LED + 220R there.
 led = Pin(2, Pin.OUT)
 
+poll = select.poll()
+poll.register(sys.stdin, select.POLLIN)
+
 print("Bluetooth Control Ready")
+print("Type 'on' or 'off' in the Serial Monitor.")
 
 while True:
-    if uart.any() > 0:
-        data = uart.read().decode().strip()   # decode bytes → string
+    # 100 ms timeout instead of a busy spin, so the loop yields to the emulator.
+    if poll.poll(100):
+        data = sys.stdin.readline().strip()
+        if not data:
+            continue
         print("Received:", data)
 
         if "on" in data.lower():
             led.value(1)
             print("LED ON")
-            uart.write("LED ON\\n")
 
         elif "off" in data.lower():
             led.value(0)
             print("LED OFF")
-            uart.write("LED OFF\\n")
-
 ` },
     ],
     code: '',