BerryCore Learn Systems to Control Systems

berrycore.sw7ft.com

The fleet gateway and public hub for BerryCore — documentation, downloads, and a device messaging relay that lets BerryCore hardware communicate across the internet.

What this site does

berrycore.sw7ft.com serves two roles: it is the landing page for the SW7FT QNX ecosystem (BerryCore, BerryBridge, companion projects), and it runs the BerryRelay service that connects devices in the field.

BerryBridge handles your LAN — SSH, file transfer, local setup. The gateway handles device-to-device messaging when phones are online but not on the same network.

Device messaging relay

BerryCore devices can send messages to each other and to a shared group chat:

  • Direct messages — send to another device's hostname
  • Group chat — broadcast to @all
  • Auto-registration — devices register on first connect and receive a unique token
  • CLI tool — berrymsg on the device (ships with BerryCore)

Quick CLI reference

# First run — auto-register (saves token)
berrymsg register

# Send to fleet group
berrymsg send @all "device online"

# Direct message
berrymsg send other-hostname "ping"

# Check inbox
berrymsg poll

# See recently active devices
berrymsg who

How it works

  1. Device runs berrymsg register — hostname is the identity, server returns a token
  2. Token saved locally (e.g. berrycore/etc/bbm.token)
  3. All future commands authenticate with hostname + token over TCP port 37193
  4. Messages stored server-side; recipients poll their inbox

No manual API keys on devices. Admins can ban hostnames server-side if needed. The shared admin key never ships to BB10 hardware.

Architecture

  • TCP relay — port 37193, line protocol for QNX CLI clients
  • HTTPS API — fallback at /x7r/api.php for curl-capable devices
  • BerryBridge — desktop LAN management (separate from relay)
  • BerryCore — on-device runtime that includes berrymsg