IoT common libraries

[cocoaway]

Pure nim MQTT client

[majj]

+1

[pigmej]

Definitely +1 for MQTT. Would be awesome to have MQTTv5

[zevv]

https://github.com/zevv/nmqtt

[ponyatov]

IoT also requires portable binary serialization with very dense encoding and fragmentation+retry support:

• LoRaWAN works with packages not more than 50 bytes (in a worst-case), and sensor nodes can be built on dead-end low-profile microcontrollers such as ATtiny/ATmega8/STM32F030.
• CAN bus: 8 bytes packages

[ponyatov]

Generic binary parser generator/library required for arbitrary protocol description. The symmetrical parser must have: generate both data decoder and encoder from single declarative grammar specification.

• http://kaitai.io
• https://github.com/zeek/binpac

Option for procedural switch/automata code generation (not tables) required for debugging.

[ponyatov]

Full cross-compiler support at least for STM32F0/L0 series, Arduino and Raspberry Pi.

• STM32L0 mostly used in IoT modems, some vendors provide user code integration

[ponyatov]

For IoT applications Nim requires integration with newlib+FreeRTOS+FAT32+lwip for all embedded devices, and bare metal i386 (IoT platform over unikernel): threading, realtime task switching, lwip, minimal file system (maybe RAM-only stub, but SD cards require at least FAT32 support).

• http://elm-chan.org/fsw/ff/00index_e.html
• https://www.silabs.com/documents/public/application-notes/AN0030.pdf
• https://www.nongnu.org/lwip/2_1_x/index.html

[ponyatov]

For IoT server: embedded Linux or unikernel, message-passing distributed computing including load balancing and on-demand scalability, async Web server/interface with process control widgets, and math&ML plugins interface (for custom user data analysis).

[ponyatov]

End nodes require a DSP library for measurement processing and signal filtering.

[Clonkk]

Bindings on littelvGLl for embedded GUI would be useful

[teroz]

Use c2nim to create the bindings you need