Skip to content

Roles

One beebo firmware runs as a companion or a repeater. The role is a setting (board.node.role) and a node runs exactly one at a time.

Switching

From the app's CLI screen:

settings board.node.role
> companion
settings board.node.role repeater

The node saves the new role, reboots and does not reply, so the app drops the connection and reconnects. Each role keeps its own name, keys, contacts and settings on the node, so switching back restores them. A switch is refused while an over-the-air update or a bulk monitor download is running.

What each role is for

  • Companion. The gateway between your phone and the mesh: messages, contacts and channels, over BLE, WiFi or USB. Beebo adds the status feed and the CLI screen.
  • Repeater. Relays packets for other nodes and is configured from the CLI screen. It is the role that runs setting trials.

Static builds

A static build, heltec-v4-<version>.companion or .repeater, compiles the other role out. It cannot switch, and board.node.role rejects the role it does not have. Use the multi-role image unless you need a fixed role.

Transports

BLE, WiFi (TCP) and USB are each switched on or off by a setting; see Connections for the defaults and how one conversation at a time is kept, and Install and Connect to provision WiFi.