Skip to content
This is a Protobuf serialization / deserialization stream engine
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.

Build Status


This project houses the Protobuf serialization service

Data Types

Easybits recognizes all primitive protobuf types. Here is a complete list:

  • int32, int64
  • uint32, uint64
  • sint32, sint64
  • fixed32, fixed64
  • sfixed32, sfixed64
  • float, double
  • bool, string, bytes

Device's Service Config

Key Required Description Example
rxconfig Optional Field descriptor to transducer mapping for deserialization "temperature,sint32,1", "humidity,uint32,2", "pressure,int32,3"
txconfig Optional Transducer to field descriptor mapping for serialization "report_duty,uint32,4"

The elements are composed of "<trandsucer_name>,<protobuf_type>,<protobuf_field_number>".

Protobuf Example

The above example would describe the following .proto file description:

syntax = "proto2";

message ENVMessage {
	optional sint32 temperature = 1;
	optional uint32 humidity    = 2;
	optional int32  pressure    = 3;

	optional uint32 duty        = 4;

Protocol Choice

Using a custom serialization library has the benefit that the code size could be extremely small. This is key for devices whose ROM is measured in kB. The down side is maintainability and user familiarity. We could not account for every build system and device that people would want to use. Using a known and well supported serialization library can lower the learning curve and provide far better platform support.

Flatbuffers was a consideration due to it's nice reflection support and it's ability to load compiled IDL files on the fly. The problem with flatbuffers it that the data sent to wire is too large. A description with no fields serializes to following hex stream:

08 00 00 00 04 00 04 00  04 00 00 00

This amount of overhead is not cool when your wireless link is only designed for passing a few bytes.

Protobuf was a clear choice due its familiarity and great wire data size. Protobuf has been around for some time and has become the accepted standard for serialization. The data on the wire is understandable and compresses how you would expect. They even compress integers when the value is small! The down side is that the code to support all the IDL features is relatively slow and large in size. This problem is mitigated on the device side by an implementation called Nanopb.

The second major hurdle with using Protobuf is how to dynamically parse messages of many different types.


  • Although I do like the name HappyBitz because it makes me think of Happy Feet, it would probably make more sense to be called EasyBits.

Development Notes

This service always makes an additional REST request to fetch device information upon receiving a new device to link.

  • It uses the device's pubsub topic. This second call could now be eliminated, since pubsub info is now sent with device events.
You can’t perform that action at this time.