You might want to continue reading at the official BERadio documentation, all inline links will be working there.
BERadio is an encoding specification and implementation for efficient communication in constrained radio link environments. It is conceived and used for over-the-air communication within the Hiveeyes project.
Together with Kotori, a multi-channel, multi-protocol data acquisition and graphing toolkit for building flexible telemetry solutions, it powers the Hiveeyes system on the gateway side, which you can enjoy by visiting the Hiveeyes platform.
There are a number of Arduino sensor nodes in the field communicating unidirectionally via radio link to a central Arduino acting as a gateway. The gateway Arduino receives message payloads and writes them verbatim to the serial port connected to a Raspberry Pi, which transforms and forwards the messages to a MQTT bus.
The data now being on the bus, arbitrary systems can consume information by subscribing to specific MQTT topics where measurement events are delivered.
The Kotori multichannel DAQ subscribes to topics on the MQTT bus, receives telemetry data payloads and stores the measurements into a contemporary timeseries database. After that, Grafana is used to display the measurement information.
BERadio is a specification and also provides reference implementations for Arduino and Python.
- Some details have been written down in the BERadio specification document.
- It uses the
Bencodeformat on the wire to provide space-efficient data encoding.
beradio forwardprocesses data messages received over the air and forwards them to MQTT.
libberadiowill be an appropriate C++ library for Arduino.
The main workhorse¶
beradio forward ingests message payloads from a serial interface, sanitizes and
decodes them from
Bencode format and republishes the data to a MQTT topic.
The MQTT topic name used for publishing is derived from some parameters contained
in the data of the message, the topic template used for this is currently programmed
The actual values will get separated, mapped and formatted in different
variants before republishing them to MQTT.
We are always happy to receive code contributions, ideas, suggestions and problem reports from the community. Spend some time taking a look around, locate a bug, design issue or spelling mistake and then send us a pull request or create an issue ticket.
Thanks in advance for your efforts, we really appreciate any help or feedback.