My query is regarding the MQTT (paho-mqtt-embedded) support in RIOT OS. This package is not been updated from last 3 years and also does not support MQTT5.
I am wondering what is the reason for choosing this package instead of any other package whose support is still provided by developers.
Hello, as @benpicco said it’s basically that. I used it for a project at work so I had some background using it and I decided to publish it from my account and giving support for native build. Which package were you thinking to use?
A nice package to have is wolfMQTT: it has support for MQTT 3.1, 5.0 and TLS. And it seems to also be MQTT-SN compliant.
It is compatible with a nice list of brokers and is quite active.
Someone should definitely try to port it to RIOT. That would allow communication with the main cloud providers (AWS IoT, Azure IoT, etc).
If no one is going to work on this I can give a look and try to port it on some spare times I might have. Was actually working in a VL53l0X driver but it’s giving me a headache so might need to leave it for some time to come back later.
@aabadie I started working on wolfMQTT porting… This package uses autoconf to build, should I replace it with a simple Makefile or we can ask the user to install autoconf package on his machine… or maybe adding it to docker? or even build the makefile myself and set them in riot pkg system… I guess that one is the best to do