Current system
Raspberry Pi hub
The CBBS hub is the durable coordinator, archive, scheduler, and browser operator surface for the mesh.
- Role
- Durable coordinator and archive
- Surface
- Browser sysop console
- Coordinates hub-side records, scheduling, account review, and operator views.
- Persists hub state in SQLite-backed services.
- Uses attached radio heads for access and federation paths.
The hub is the authority for durable coordination; degraded node coordination is not a replacement for hub authority.
Current system
Heltec V2 field nodes
Heltec WiFi LoRa32 V2 nodes act as smart radio heads, relays, field terminals, and local room servers.
- Role
- Field node and relay
- Surface
- Local SoftAP browser room and OLED quick checks
- Relays LoRa mesh traffic and publishes state deltas, queue status, and command acknowledgements.
- Serves a local room-oriented WPA2 SoftAP browser interface for up to four nearby clients in the full room-node build.
- Supports optional build-flag-gated microSD cold storage.
The local browser surface can be omitted in configurations that only need mesh relay behavior.
Current system
Windows Sysop Manager
The Windows operator toolchain provides native lanes for provisioning, image building, SD writing, device lab work, and live operations.
- Role
- Native operator workbench
- Surface
- Unpackaged framework-dependent WinUI 3 shell
- Organizes Network Manager, Device Lab, Image Builder, SD Writer, and command-deck lanes.
- Uses bundled web assets in a locked-down WebView2 shell.
- Tracks hub session, telemetry, provisioning, image build, and device lab workflows.
The Windows operator tooling is active project work; packaged installer availability is not claimed.
Current system
Nearby room client
A phone, tablet, or laptop browser can join a room node over local Wi-Fi for account access and room browsing.
- Role
- Nearby browser client
- Surface
- Room-node HTML interface
- Connects by physical proximity to a room node WPA2 SoftAP.
- Supports nickname sessions, account application, login, logout, room browsing, themes, and policy views.
- Uses access levels from guest through network administrator and banned states.
Room clients require local node access; they are not a cloud-hosted chat service.
Prototype display
OLED and P070 display surfaces
CBBS uses small displays for quick-check field status and richer controller-style views for configured interfaces.
- Role
- Field display and controller surface
- Surface
- Onboard OLED quick screens and P070 prototype display captures
- Uses onboard OLED screens for quick local checks.
- Uses browser and Nextion/P070 style surfaces for richer operator views.
- Maps global-controller panels to hub APIs rather than direct SQLite writes.
P070 captures represent prototype controller screens unless explicitly labeled as current system interfaces.
Current system
Transport layers
CBBS treats LoRa as the authoritative long-range store-and-forward path, with local Wi-Fi for nearby browser presentation.
- Role
- Message and control transport
- Surface
- LoRa mesh, local Wi-Fi, and reserved adjacent acceleration paths
- Carries BBS records, alerts, listings, troubleshooting notes, telemetry, and command acknowledgements over the same mesh substrate.
- Uses Wi-Fi for local access and presentation near nodes.
- Keeps ESP-NOW reserved for adjacent acceleration rather than the authoritative long-range path.
Large files are not positioned for spoke LoRa mesh transport.
Current system
Agriculture runtime overlays
CBBS includes agriculture-facing source paths for field observations, review desks, input-cost records, and guarded gateway integration.
- Role
- Agriculture review and integration layer
- Surface
- Hub agriculture review desk and firmware gateway roles
- Supports irrigation schedules, standardized forms, sensor observation intake, input-cost tracking, and advisory review patterns.
- Includes sensor-node and gateway roles for Modbus, MQTT, HTTP, and normalized CBBS records.
- Limits current agriculture claims to review, records, advisory analysis, and approval workflows.
The current agriculture story centers on review, records, advisory analysis, and operator approval.
