u/NMTech-Official

Since launching the NM-CYD-C5 (the ESP32-C5 based CYD variant with dual-band WiFi 6), the single most common piece of feedback has been:

"Could you make a 1u variant that I could connect an antenna to?"

"Does it have external antenna connector"

"Will an external antenna be supported this time, or is a DIY solution again required to attach an external antenna?"

Fair point. 5GHz attenuates much faster than 2.4GHz, and a small PCB trace antenna surrounded by a display and ground planes has its limits.

So: the NM-CYD-C5-Colorful-Ant is coming.

• IPEX-1 connector + bundled dual-band 2.4G/5G antenna • External antenna only — no onboard PCB antenna on this version • Same ESP32-C5 (dual-band WiFi 6, BLE 5.3, Zigbee/Thread), same 16MB Flash + 8MB PSRAM, same CYD-compatible footprint • Still works with Bruce / Marauder / ESPHome, etc as before

The default External Antenna Parameters

• Frequency range: 2400-2500MHz / 5000-5800MHz
• VSWR: 2400-2500 ≤ 2.5, 5000-5800 ≤ 2.5
• Efficiency %: 2400-2500: 83.3 AVG; 5000-5800: 73.8 AVG
• Peak Gain (dBi): 2400-2500: 3.2 AVG; 5000-5800: 3.7 AVG
• Radiation Properties: Omni-directional
• Polarization: Linear

The 3D printed shells (see from the picture) will be released on GitHub repository soon.

https://github.com/RockBase-iot/NM-CYD-C5

We've been working on a Dual-Band Analyzer to make full use of the ESP32-C5's 5GHz capability in Bruce, and just opened PR #2804 for review.

What it does:

• Scans 5GHz channels (non-DFS channels only for now)
• Shows channel utilization and signal strength for both bands side-by-side

Current status:

Tested on NM-CYD-C5 (ESP32-C5 + ST7789). The code is working but we're looking for feedback before it gets merged – especially on UI layout and whether we should include DFS channel support (passive scan only) in a follow-up.

Try it:

Check out the PR: https://github.com/BruceDevices/firmware/pull/2804

Or flash the branch and look for "Dual Band Analyzer" in the WiFi menu.

Hi r/esp32,

Following up on our retro-go port for the NM-CYD-C5 — we've now added BLE-HID gamepad support. That means you can pair a Bluetooth controller and play without touching the screen. No wires, no mods, just pair and play.

We tested with the Shan Wan Q36 — a compact Bluetooth gamepad that maps cleanly to retro-go's input system — but any BLE-HID keyboard/controller should work.

Quick recap for context:

the NM-CYD-C5 is an ESP32-C5 board with 8 MB PSRAM, 16 MB flash, and a 2.8" 240×320 ST7789 display. Our retro-go port runs on it out of the box — no PSRAM soldering needed. Now it talks Bluetooth too.

What's new in this release:

• BLE-HID host mode: scanning for BLE HID keyboard devices at boot

• Auto-pair: picks up the first advertising BLE-HID keyboard in range and

connects automatically — you can also manually pair via the launcher menu

• Gamepad mapping: Shan Wan Q36 (D-pad + ABXY + shoulder buttons) mapped to

retro-go's standard input layout:

- D-pad → directional input

- A / B → retro-go A / B

- Start / Select → menu / select

A few technical notes:

• ESP32-C5's BLE 5.0 stack is handled via NimBLE in ESP-IDF 5.5+; we use the

standard esp_hid component with a thin HID→retro-go input bridge

• The Shan Wan Q36 advertises as a BLE-HID keyboard (mode: HID for Android), which is why the HID report parsing treats a subset of keycodes as gamepad buttons

• Pairing is stateless per session — no bonding or persistent storage needed; just turn on the controller before booting the board

Getting started:

1. Flash the latest retro-go .img to 0x0

2. Power on your Shan Wan Q36 (or any BLE-HID keyboard) — put it in pairing mode

3. Power on the NM-CYD-C5 — it auto-scans and connects

4. Launch a ROM and play with the gamepad

Software tag: https://github.com/RockBase-iot/retro-go/releases/tag/Retro-Go_1.46_NM_CYD_C5

(Updated .img includes BLE-HID support)

Would love to hear what controllers you test with — drop a comment if you try

something other than the Q36.

Happy gaming 🕹️

Hello, everyone, i wanted to share something we've been experimenting with that turned out way cooler than expected.

The Idea

What if your Meshtastic node wasn't just a dumb relay, but had an actual AI agent sitting behind it, reachable from Telegram or Feishu, capable of managing the mesh intelligently?

That's what we built: ESP-Claw + Meshtastic, connected over Serial PROTO.

How It Works

Meshtastic has a Serial Module mode (SERIAL_MODULE_MODE_PROTO) where the node exposes its full protobuf API over UART. Instead of using the Python CLI or a phone app, we wired it directly to an ESP-Claw board and implemented protocol-level command parsing inside esp-claw's Lua rule engine.

The stack looks like this:

Telegram / Feishu (your phone)
        │
   Cloud LLM (Claude / DeepSeek / GPT)
        │
   ESP-Claw Board ←── UART (Serial PROTO) ──→ Meshtastic Node (Heltec LoRa32 V3)
   (NM-CYD-C5 or                              (ESP32-S3 + SX1262)
    NM-Display-2.8inch)
        │
   LoRa Mesh Network

Hardware We Tested With

• NM-CYD-C5 – ESP32-C5 (WiFi 6!), 16MB Flash, 8MB PSRAM, 2.8" 320×240 touch display. About the size of your palm.
• NM-Display-2.8inch – ESP32-S3 based, 2.8" IPS touch screen, 6-axis IMU, RTC, audio codec. Beefy little board.
• Meshtastic node: Heltec LoRa32 V3 (ESP32-S3 + SX1262). Classic choice, rock solid.

What It Can Actually Do

Once the AI agent can speak Meshtastic's protocol, a lot opens up:

• Remote Node Management – "Hey Claude, what's the battery level of node !a3f2b1c4?" — done. No need to be within Bluetooth range.
• Intelligent Mesh Monitoring – The agent periodically polls telemetry from all reachable nodes, alerts you if someone's battery is dying or a node went offline.
• Automated Mesh Health Reports – Schedule daily summaries pushed to your Telegram: "12 nodes online, 2 nodes below 20% battery, 1 node with poor SNR."
• Natural Language Mesh Commands – Instead of remembering Meshtastic CLI syntax: "Send a message to the 'hiking-group' channel saying we're at the trailhead" — the LLM translates that into the correct protobuf calls.
• Event-Driven Automation – Lua rules on esp-claw trigger on incoming mesh packets. Got a node broadcasting emergency coordinates? Auto-escalate to a notification on your phone.
• Off-Grid Bridge – Mesh nodes in remote areas with no WiFi can be managed through a single ESP-Claw gateway that has both WiFi and LoRa reach.

Drop a comment if you're interested in trying it out, or if you have ideas for what else an AI agent should do on a mesh network. We'll share setup guides if there's enough interest!

Hi r/esp32,

We added support for the NM-CYD-C5 board to retro-go (the ESP32 retro emulator launcher/frontend).

If you haven't seen it, this excellent Instructables guide shows how to turn an ESP32-CYD into a RetroGo handheld:
https://www.instructables.com/Retro-Handheld-Based-on-the-ESP32-CYD-and-RetroGo/

The main difference with the NM-CYD-C5 is that the board already ships with 8 MB PSRAM, plus an ESP32-C5 (RISC-V @ 240 MHz), 16 MB flash, and a 2.8" 240×320 ST7789 display. That let me skip the external PSRAM mod/wiring that the original CYD build requires — it mostly works out of the box once the SPI display, SD card, and touch pins are mapped.

A few technical notes:

• New target: nm-cyd-c5
• Requires ESP-IDF 5.5+ (needed for ESP32-C5 support)
• The XPT2046 touch controller is mapped to a virtual gamepad for launcher nav and basic testing
• Audio defaults to the dummy sink because the board docs don't list an onboard DAC or speaker
• The CPU is single-core RISC-V, so it has less headroom than dual-core ESP32/S3 targets — start with launcher + retro-core before trying heavier emulators

If you want the full handheld build (case, physical buttons, controls), the Instructables guide linked above is still the best reference; this board just saves you the PSRAM soldering step.

Hardware ref: https://github.com/RockBase-iot/NM-CYD-C5 Software tag: https://github.com/RockBase-iot/retro-go/releases/tag/Retro-Go_1.46_NM_CYD_C5

you can just flash the .img file to 0x0 to run retro-go on your NM-CYD-C5.