Arduino + ESP32 Bench

← back to homework

Write, explain and compile-check Arduino and ESP32 sketches for Mike, working from the parts he already owns on an unsorted shelf.

Folder: /mnt/datapool/hermes_workspace/projects/arduino-esp32 · parts inventory done - ESP32 upload failed (board-side); no build chosen

Start a session here (paste into a terminal):

cd /mnt/datapool/hermes_workspace/projects/arduino-esp32 && hermes

What's in the folder

docs/
log.md · parts-inventory.md

output/
parts-inventory.pdf

Project notes

Project: Arduino + ESP32 Bench (arduino-esp32)

Hermes: this file is the context for the Arduino + ESP32 Bench project assistant.

You are in /mnt/datapool/hermes_workspace/projects/arduino-esp32. Work from here unless told otherwise.

Objective

Write, explain and compile-check Arduino and ESP32 sketches for Mike, working from the parts he already owns on an unsorted shelf.

Status

What "done" looks like

Any sketch Mike asks for comes back already compile-verified, explained block by block, and built from parts he actually has.

Paths (all under this project root)

```

/mnt/datapool/hermes_workspace/projects/arduino-esp32/

.hermes.md this file — auto-loaded project rules

README.md human quickstart (how to start THIS assistant)

src/ source code for the project

scripts/ runnable one-off scripts + generated tools

schemas/ JSON schemas for every custom tool (<name>.schema.json)

output/ generated artifacts, reports, exports

docs/ notes, decisions, references

venv/ per-project Python venv (created on demand)

```

Shared, project-independent facts (host, storage, runtime) live in

/mnt/datapool/hermes_workspace/ENVIRONMENT.md — read it instead of assuming.

Working rules

1. Save every generated script, schema, and output under /mnt/datapool/hermes_workspace/projects/arduino-esp32/ —

never leave artifacts in ~ or the scratch dir.

2. Every custom tool ships as two files in the same change:

scripts/<tool_name>.py and schemas/<tool_name>.schema.json.

Copy the working pair at /mnt/datapool/hermes_workspace/templates/example_tool.py +

example_tool.schema.json as the starting shape: pure function, stdin JSON →

stdout JSON, no side effects on import.

3. Test before marking anything complete. No Docker here: use

/usr/bin/python3 -m venv venv && ./venv/bin/pip install ... (bare python3

in a Hermes session is Hermes' own runtime and has no pip), or run the script

and show real output. Paste actual command output, never a description of it.

4. Keep terminal explanations to a single copy-and-pasteable command per step.

5. Never hand over a sketch that has not been compiled. Run arduino-cli compile for the target board first and say which board it was checked against.

6. One complete, copy-pasteable sketch per answer. No diffs, no insert-this-line-at-42 instructions - Mike works one-handed from a phone.

7. Write AND explain. A bare sketch is a partial answer: say what each block does, and why that pin, that library and that value.

8. Never ask Mike for a photograph. Ask him to count or describe in one line instead - a stated description is a complete answer.

9. Never claim flashing works. Upload has not been tested on the 3050 because no board has ever been attached. Say the code compiles, not that it runs.

10. Do NOT ask Mike to inventory his pile of add-on cards, shields and sensors up front. His instruction (2026-11-14): identify them one at a time, as a build needs them. Ask about a specific part only when the sketch or a wiring answer truly depends on it, then record just that one in docs/parts-inventory.md.

Tools, MCP & workgroup

arduino-cli (~/.local/bin), git, python3

Outputs / deliverables

sketches/, docs/

Environment

Shared Environment — 3050 / T130 (single source of truth)

This block is injected into every project's .hermes.md by bin/new-project, so

host facts live in ONE place. Update here, not per project.

(cifs, vers=3.1.1, uid/gid 1000, rw). There is NO /mnt/t130_storage on this host.

⚠ Inside a Hermes session, bare python3 resolves to Hermes' own bundled runtime

(3.14.7) which has no pip — python3 -m pip install x fails with

"No module named pip". Always build project venvs explicitly:

/usr/bin/python3 -m venv venv && ./venv/bin/pip install ...

2.5.4 (cp314 wheel) and tokenizers 0.23.3 all resolve — the HF/MCP stack is fine

on this Python, no downgrade needed.

Version control & backup

mandatory on the SMB share, not cosmetic: core.filemode=false (the share forces

0755) and core.trustctime=false — CIFS ctimes are unreliable, and with them

trusted git add can treat a just-written file as unchanged and commit a **stale

blob**. Commit when a unit of work is finished:

cd /mnt/datapool/hermes_workspace && git add -A && git commit -m "...", then

confirm git status --short is empty — if it still lists files, re-add and commit

again before trusting the commit.

gdrive:3050-HOME/hermes_workspace (one-way up, .git included, so the

Drive copy is a real clonable repo). Script ~/.hermes/scripts/backup_hermes_workspace.sh,

log ~/.hermes/cron/output/hermes-workspace-backup.log. It prints nothing on

success and pings Telegram only on failure.

rclone sync against a missing mount would delete the Drive copy, so it gates

on the mount, a sentinel file, and a minimum file count, and caps deletions.

job (sync_to_drive.sh, which covers $HOME/{book,hermes-3050,agent-os,projects,bookapp}).

Two sync jobs touching one tree is how you get conflicts.

Paperclip (agent orchestration) — installed on this host

chart, a ticket board, per-agent budgets, heartbeat runs and human approval gates.

It is not an agent — it is the organisation agents work in.

systemd user service paperclipai.service, state in ~/.paperclip/ (2.4 GB),

board token in ~/.paperclip/auth.json. Reads ~/.paperclip unless -d is passed.

LAN address — that is deliberate, --bind tailnet). /api/health returns 200 with

deploymentExposure: private. Sign-in page is /auth, not /.

isInstanceAdmin: true). Company: ndyinc, id 836f8e51-a961-4076-879c-7303bb53da72.

adapterType: hermes_local, model deepseek/deepseek-v4.1-flash (provider nous),

timeoutSec: 5400.

/mnt/datapool/hermes_workspace/projects/wind-sculpture-design, so the spawned Hermes

auto-loads that folder's .hermes.md — which is exactly how an employee gets its

project context. Point cwd at an assistant and it inherits the objective, rules and

next step with no prompt wiring.

connectors — and its runs can read credentials and write memory. Treat employee runs

as mutations of our own state.

({runId, store, logRef, content}) where content is a string of newline-separated

inner JSON records with .chunk. Decode: json.load(file)["content"] → split lines →

json.loads each → join .chunk. It is not NDJSON, and grepping it directly shows

nothing useful.

disabled, and run 1ca36568-f364-42c0-9195-8107538ec552 (2026-11-01 04:58–05:08) is

recorded failed even though its own log ends `[hermes] Exit code: 0, timed out:

false` after delivering NDY-3. The agent's own summary reports three rejected artifact

uploads (Another matching artifact upload is still in progress), so deliverables

exist in the project workspace but are not attached to the ticket.

Verified against live command output 2026-10-30. Re-verify with:

hostname; ip -4 addr; mount | grep datapool; python3 -V; node -v; docker --version

Session handoff

When work stops: update Status (state + next step) in this file, then log one

line in /mnt/datapool/hermes_workspace/projects/arduino-esp32/docs/log.md with date + what changed + what's next.

Built live from your own files — nothing here is typed by hand.