⚙️ Reason for Beeton

Beeton exists for one reason only: IoT should be simple.

Currently, Wi-Fi and Zigbee dominate the IoT space, but both come with one major drawback: making your own Thing requires massive boilerplate.

I originally tried using Zigbee to control my model trains. Once I saw:

• Over 200 lines in a user-defined header,
• Three separate libraries,
• Nothing integrated into standard Arduino setup() and loop() methods...

I said, enough.

That’s when Beeton was born.

🔄 What Beeton Is

Beeton is a simple, consistent, binary yet human-readable application protocol for IoT. It’s based on one core idea:

You have Things. Things do Actions. You send Parameters.  
That’s it.

All the complexity of communication is handled by:

• LightThread, which manages the application layer
• OpenThread, which handles the mesh network beneath that

You never need to touch either.

✨ Key Design Principles

• 4-parameter structure: [ ThingID, InstanceID, ActionID, Payload ] Simple, efficient, and universal.

• Broken Star topology: Like a standard star network with one Leader and many Joiners, but Joiners can relay through each other.
  This creates resilience without extra configuration.

• No nested complexity: If it’s a Thing, it has an ID.
  If it does something, it has an Action.
  You define it. You send it. That’s all.

🛤️ Why It Matters

Beeton empowers hobbyists, tinkerers, and engineers to build powerful IoT systems without becoming a network engineer.

You don’t need cloud APIs.
You don’t need a corporate certificate.
You don’t need to read 17 PDFs to turn on a light.

1. You define a Thing.
2. You define an Instance (InstanceID).
3. You give it an Action.
4. You send the command.

And through this simplicity,
comes the opportunity for great things.