Hardware under development

Field hardware surfaces

CBBS hardware combines hub coordination, LoRa field nodes, local browser access, quick-check displays, and guarded agriculture integration for practical field deployment.

Actual UI capture

Node-local room service

The Heltec room-node story is easiest to understand through the local browser UI: node status, board ledger, access policy, mesh status, and theme policy are visible from a nearby client.

CBBS node console screenshot showing local access, board ledger, access policy, mesh status, and theme policy panels.
Current interface

Current system

Raspberry Pi hub

The CBBS hub is the durable coordinator, archive, scheduler, and browser operator surface for the mesh.

  • 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.

  • 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.

Prototype display

OLED and P070 display surfaces

CBBS uses small displays for quick-check field status and richer controller-style views for configured interfaces.

  • 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

Agriculture runtime overlays

CBBS includes agriculture-facing source paths for field observations, review desks, input-cost records, and guarded gateway integration.

  • 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.