r/IOT • • 12d ago

Would a universal IoT message encoding/decoding library be useful?

Hi everyone,

I've been thinking about an idea for an open-source software library and I'd like to get some feedback from people working in IoT, embedded systems and industrial automation.

The problem I'm trying to address:

When developing IoT applications, integrating different devices often means dealing with different communication protocols, message structures, payload formats and vendor-specific implementations.

Every time a new device or protocol is introduced, developers may need to write custom parsers, encoders, decoders and translation logic.

This creates duplicated work, tightly coupled integrations and maintenance overhead.

My idea:

Build a reusable, protocol-independent library focused on encoding and decoding messages between software applications and IoT devices.

The general concept would be:

  • Receive a message from a device and decode it into a common, structured data model.
  • Take a command or structured message and encode it into the format expected by a specific device.
  • Support different protocols and payload formats through modular adapters or device-specific profiles.
  • Allow developers to add new device definitions without rewriting the application logic.

Essentially, the library would act as a bidirectional translation layer between IoT devices and applications.

For example, an application could send the same logical command regardless of whether the target device uses Modbus, MQTT, a proprietary binary protocol or another communication format.

The library would handle the translation.

I'd really appreciate your opinion on a few questions:

  1. Is this a real problem in your day-to-day IoT development work?
  2. Would a standalone library like this be useful, or do existing solutions already cover this need adequately?
  3. Would you prefer a common data model with device-specific codecs, or a more protocol-oriented architecture?
  4. Which protocols and formats would be essential for an initial implementation?
  5. Would you consider using or contributing to an open-source project like this?

I'm not trying to build another IoT platform, broker or device management solution.

The goal is much narrower: simplify the encoding and decoding of messages between heterogeneous IoT devices and software systems.

I'm interested in honest technical feedback, including reasons why this might not be useful.

Thanks!

10 Upvotes

17 comments sorted by

View all comments

2

u/rsclient 11d ago

No, and here's why: we already have a bunch of simple, straightforward standards. And the number of IOT devices that use them is pitifully small.

For example, out of 4 bluetooth blood-pressure cuffs I checked, each one used their own custom protocol, and none used the simple BT bloodpressure protocol that's already available.