Skip to content

Support and Feature Requests

Beebo is a one-person project, built and supported in spare time. Questions, bug reports and ideas are welcome, and I read them all. Replies can take a while, so thank you for your patience. This is a hobby project, and a clear, friendly report gets the fastest answer.

Where to ask

Bug reports and feature requests go through the issue tracker of the firmware repository: github.com/pasqo/beebo-meshcore-fw/issues

You need a free GitHub account. Search the open and closed issues first: your question may already be answered. Then choose New issue, pick the bug report or the feature request form, and write one issue per problem or idea.

For questions and open discussion, the MeshCore Discord firmware-development channel is a good place too.

Reporting a problem

The bug report form asks for what helps me reproduce it:

  • what you did, what you expected and what happened
  • the firmware version (ver on the node console, or beebo status node) and the board
  • the role the node was in, companion or repeater, and how you connect (app, USB, BLE or WiFi)
  • the output of the commands involved, copied as text (status, check, monitor status)
  • for a crash or a reboot loop, what the node printed over USB

Never post secrets: admin passwords, private keys, WiFi passwords or the files of config backup.

Asking for a feature

Say what you want to do, not only the feature you have in mind, and why the current behavior falls short. A real use case helps decide what to build.

Before you ask

Troubleshooting covers the common messages, and Commands lists what runs on the node and on the computer. For MeshCore itself (apps, packet formats, the mesh) see the MeshCore documentation.

What to expect

Fixes and features happen when I have time, in an order that suits the project. Some requests may wait, or be declined to keep beebo small and reliable. A thank-you note, or a star on the repository, is always appreciated.