DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to test the ESP32 board over BLE from a Mac with Esp32 Iphone Agent

Play the app's role from a Mac to check the board's BLE link, hotspot and HID output.

Authorization notice. Esp32 Iphone Agent is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA firmware developer who needs to check the board without the phone app running.

The problemWhen the agent fails, it is hard to tell whether the board, the BLE link or the phone app is at fault.

The outcomeThe board is exercised from a Mac over BLE, which isolates firmware problems from app problems.

What you need first

  • An ESP32-S3 board, tested with a Seeed Studio XIAO ESP32S3 (plain version, 8 MB PSRAM)
  • An iPhone on iOS 18 or later with cellular data
  • An OpenAI-compatible vision model endpoint and API key
  • A Mac with Xcode, needed once to flash the board and build the app

Steps

  1. Install arduino-cli, the ESP32 core 3.3.x and NimBLE-Arduino 2.5.x, then run arduino-cli lib install "[email protected]".
  2. Run hardware/flash.sh with the board plugged into the Mac.
  3. Read hardware/tools/README.md and the BLE protocol in docs/ble-protocol.md.
  4. Run hardware/tools/board_test.py to play the app over BLE from the Mac.
  5. Record which board command fails and compare it to the app's behavior.

Prompt for your agent

Using the repo onehumanbeing/esp32-iphone-agent, run hardware/tools/board_test.py against the board at <serial port> and summarize each BLE command it sends. Expected output: a list of commands with pass or fail. Verify the protocol names match docs/ble-protocol.md.

Caveat. The README says the test harness plays the app from a Mac, but it does not list the board_test.py arguments, so read its help output before running it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page