Repeat the tested ESP32-S3 and OLED checks
Status: passed on the owner's kit on 12 October 2026 (record). Another person's reproduction is still needed. Compilation and simulated board tests do not complete this procedure.
On this page
Before the test
Follow the inspected kit and tested wiring. The YD-ESP32-23 v1.3 board and RG1.30 IIC v2.2 display have no fitted headers; establish secure connections before powering the display. Do not use C124 pin assignments or its firmware image. Flash only a board you own, with an image built for it. Use the released ESP32 SDK v0.2.0-alpha.9 build and recovery instructions. See the concise repeat-the-kit guide.
Run the local gateway and USB bridge on the host computer for the USB test. A hardware test needs no public tunnel. The gateway also has an opt-in private LAN TLS listener for the Wi-Fi test. The packaged remote MCP route for Grok Bot is not ready. An authenticated remote MCP endpoint with TLS and native Grok Bot invocation are still needed. A tunnel adds reachability, not authentication.
Grok Bot's normal cloud computer cannot reach your private LAN through its internet connection alone. On the owner's setup, Grok Bot used an approved local Mac command and showed text on the OLED. This verifies that local execution path only. It does not verify a packaged MCP integration. Read the hosting FAQ for the connection paths. Do not expose the device protocol directly.
Record the YD-ESP32-23 v1.3 board and ESP32-S3-N16R8 module markings. Record the Electrifier RG1.30 IIC v2.2 display, actual controller/address, breadboard wiring, pin table and USB-C data cable. Record firmware SHA-256, gateway and SDK commits, host operating system, port, time and tester. Do not record tokens. The 3.3 V GPIO8/GPIO9 wiring passed on the owner's kit.
M5 — Grok Bot use is partly done: Grok Bot showed text on this kit through an approved local command. Native tool calls need a separate check. M8 — Physical and independent verification is partly done: the owner's kit passed USB and Wi-Fi tests; independent reproduction is still needed. A Pi is not required for this ESP32-S3 experiment.
Procedure
- Discover the device. Check its model, boot identity, capabilities, firmware version and
simulated: falsevalue. - Request a short OLED message through the SH1106 driver. Observe the 128×64 display, change the message and clear it. Record command results and physical observations separately. Check that invalid or oversized text fails without an unintended change. Test the onboard RGB pixel on GPIO48.
- Press and release the onboard BOOT button on GPIO0. Check event order and reported state. Repeat the reads and check for duplicate events.
- Unplug the board. Try a command. Check that the result reports offline or unconfirmed status.
- Reconnect the board. Check state recovery.
- Restart the board and gateway separately. Check boot and session changes, cursor reset and stale state. Check that old actions do not run again.
- For native Grok Bot MCP, repeat after the remote route passes authentication and connection checks. Record it separately from the approved local-command route.
- Ask a second tester to follow the procedure. Record any differences.
Do not mark a failed or unavailable step as passed. Record its blocker and supporting evidence.