Skip to content

Integration of opcodes #22

@aparcar

Description

@aparcar

Hi, great library, thanks for creating!

I'm working on a setup where used sensors may change over time, meaning a static decoding on the backend won't work. Searching for a solution I found things4u's message format - which isn't implemented anywhere.

The idea is to have 6 Bit prefixes announcing the type followed by a 2 Bit length field. The decode would read the first bite and may automatically add "temperature" or whatever as a dict key.

This would increase the message size by a single Byte per transported value but allows dynamic decoding.

A possible implementation could give the LoraMessage a parameter setting the use of opcodes, or not.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions