minimq
minimq copied to clipboard
quartiq
Minimal no_std MQTT v5.0 client implementation
Add support for a TLS-based connection with the broker. This may necessitate the development of new `embedded-nal` traits for the TCP stack. [`embedded-tls`](https://github.com/drogue-iot/embedded-tls) can provide the necessary TLS components.
Add support for accepting a domain name for the broker. When a domain name is provided, the name must first be resolved into an IP address before being used for...
Add support for providing authentication credentials as part of the connection process
Currently, QoS support is only implemented for sending QoS > 0 messages, but not for receiving. We need to respond with PubAck if the server ever sends us a publish...
Because of the usage of const-generics on the `MqttClient` and `SessionState`, there's a number of code that gets generated twice in final binaries. This can result in significant binary bloat...
When a user wants to `subscribe` to a topic, they generally want to do some explicit action or acquire some data from the device to construct a response. Generally, the...
For publication, it's possible that the client may not want to transmit the `topic` in every message. By using `TopicAlias` properties, the size of the MQTT publication packet can be...
Currently, messages with QoS > AtMostOnce are stored in the `SessionState`. MQTT requires that we republish these messages upon reconnection with the broker in the same order as originally published....
It would be really nice to be able to use `minimq` as an async MQTT client as well. We should investigate what it would take. Ideally, we would be able...