Troubleshooting¶
For how connections behave and why, see Connections.
| What you see | Why | What to do |
|---|---|---|
| The app or CLI gets no answer from the node | Only one connection drives the node at a time. Another app, the beebo CLI or a USB session may hold it. |
Disconnect the other client. |
settings board.node.role repeater gets no reply |
A role switch reboots the node by design. | Wait a few seconds and reconnect. |
ERR: needs role 'repeater', node is 'companion' |
The node is a companion. | Switch the role first: settings board.node.role repeater. |
trial waiting for traffic |
The node hears too little traffic to start a trial. | Wait. It starts by itself when traffic arrives. |
warn: txpower=<n> dBm underdrives the PA |
The transmit power is under 16 dBm. | settings radio.txpower 18 |
Unknown command |
The node does not know that command. | Check the spelling. Commands lists what the node answers and what needs the beebo command line. |
ERR: unknown setting |
The path is not one the node console knows. | settings lists the names, and settings <branch> the ones below it. The rest of the tree needs beebo settings. |
ERR: the trial is already on; run monitor tuning trial stop first |
A trial is running. | Stop it, then start again. |
ERR: battery.present is no; set it to yes first |
battery state <state> cannot force a state on a node without a battery. |
settings board.battery.present yes. |
| The trial stopped after a reboot | Trial settings are not saved across a reboot. | Enable it again. |
| The app cannot connect after flashing beebo | A pairing made with firmware that used an older BLE stack does not carry over. | Remove the node from the phone's Bluetooth list and pair again with PIN 123456. |
| The two beebo channels are missing | The app has not synced yet, or the node's channel table is full. | Reconnect. With a full table no feed is created. |
| A new board does not boot beebo | A board that never ran MeshCore needs a stock image first. | Flash a stock MeshCore companion in merged mode with the Web Flasher, once, then the beebo image. |
| An update failed | The node rolls back to the previous image if the new one does not boot. | Check the version, then try again. |
| The node's clock is wrong, for example years ahead | The clock only moves forward, so a normal sync cannot correct a clock that is ahead. | beebo clock shows the drift. beebo clock --boot reboots the node with the host's time. |
Still stuck? See Support and Feature Requests.