← ClaudeAtlas

espos-ecosystemlisted

Orientation for working on espOS or any of its child repos (registry, signalk-espos-manager, espos-p4-cockpit, espos-ble-gateway, espos-nmea-gateway, espos-bathy-bridge, espos-zigbee-coordinator, the cockpit WASM, signalk-hmi-designer, signalk-espos-stream). Which repo owns what, the contracts between them, and the house rules that differ per repo. Load first in any espOS session.
signalk-espOS/skills · ★ 0 · Code & Development · score 72
Install: claude install-skill signalk-espOS/skills
# The espOS ecosystem Snapshot: espOS **v0.24.0** on ESP-IDF **v6.0.3**, late October 2026. Versions move; read `version.txt` and `.idf-version` in the checkout instead of trusting the numbers here. espOS is a firmware base for ESP32 boards that talk to Signal K. Despite the name it is not an operating system: it is a set of ESP-IDF components a firmware links in, much like SensESP, but on plain ESP-IDF 6 instead of Arduino and PlatformIO. It does the parts every such device needs (WiFi or Ethernet, the setup portal, a settings page, finding the Signal K server and getting approved, sending deltas, PUT and REST, mDNS, a health watchdog, logs, core dump, signed OTA), started with one `espos_start()` call. Firmware projects sit on top. A registry lists their releases, and a Signal K plugin keeps a boat's devices updated from it. ## Repos and what each owns | Repo | Role | Language / gate | |---|---|---| | `signalk-espOS/espOS` | **Primary.** Components `components/espos_*`, CMake prologue, sdkconfig layers, partition tables, reusable release workflows, docs site | C11 (+C++ for n2k/voice/audio). `test/host/run_all.sh`, `scripts/build.sh` | | `signalk-espOS/registry` | `projects/<id>.json` per firmware, the `boards/` and `usecases/` catalogue, and the CI-generated `index.json` | Node 24 scripts, no deps | | `signalk-espOS/signalk-espos-manager` | Signal K plugin: mDNS discovery, registry client, firmware mirror, OTA jobs, radio co-processor updates, fleet API key, plus the b