ci / test (push) Successful in 1m49s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
Instructions for an AI agent setting this up
meshcore-repeater-observer reads a MeshCore repeater's console and publishes what the repeater hears. README.md is the reference; these are the rules.
- Read only, with two exceptions the user must approve: the observer
itself sets the node's clock (
time <epoch>) and, for the community feed, reads its private key (get prv.key) into memory. Never send other CLI commands to the repeater (set …,reboot,erase,advert) — it is part of a community network. - The repeater needs the observer build of meshcore-tth. Ask which board and firmware it runs; do not flash anything yourself.
- Prefer USB (
/dev/serial/by-id/…, never/dev/ttyACM0). BLE: the console is off after flashing and has no login, only the BLE PIN (123456in the public build). The user sets their own withble pin <6 digits>(USB console, or as admin over the mesh) and thenble on; never type, print or store their PIN yourself, neverble onfor them. Releases up to tth-654d53f3 lackble pin: USB only there. Pairing is interactive (bluetoothctl pair) — the user does it. Neverbluetoothctl removea paired repeater. - Community feed only for a node on the Czech preset (869.432 / 62.5 / SF7 /
CR5), with
MC_OBS_IATAset; leaveMC_OBS_AUDIENCEat its default. - Passwords and PINs go to the env file (mode 600), never into commands you print, commits or logs. The private key never leaves the process.
- Done = the log shows
observer: připojen k …and packets are counted; on the community analyzer the node appears under observers within minutes.
Developing: python3 -m pytest, ruff check, ruff format --check,
mypy meshcore_repeater_observer.py. --help must work without bleak/paho.