2020-04-14 17:19:12 +08:00
|
|
|
# MQTT in curl
|
|
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
A plain "GET" subscribes to the topic and prints all published messages.
|
|
|
|
|
Doing a "POST" publishes the post data to the topic and exits.
|
|
|
|
|
|
|
|
|
|
Example subscribe:
|
|
|
|
|
|
2023-09-29 23:42:39 +08:00
|
|
|
curl mqtt://host.home/bedroom/temp
|
2020-04-14 17:19:12 +08:00
|
|
|
|
|
|
|
|
Example publish:
|
|
|
|
|
|
2023-09-29 23:42:39 +08:00
|
|
|
curl -d 75 mqtt://host.home/bedroom/dimmer
|
2020-04-14 17:19:12 +08:00
|
|
|
|
|
|
|
|
## What does curl deliver as a response to a subscribe
|
|
|
|
|
|
|
|
|
|
It outputs two bytes topic length (MSB | LSB), the topic followed by the
|
|
|
|
|
payload.
|
|
|
|
|
|
|
|
|
|
## Caveats
|
|
|
|
|
|
|
|
|
|
Remaining limitations:
|
|
|
|
|
- Only QoS level 0 is implemented for publish
|
|
|
|
|
- No way to set retain flag for publish
|
|
|
|
|
- No TLS (mqtts) support
|
2021-10-31 23:34:44 +08:00
|
|
|
- Naive EAGAIN handling will not handle split messages
|
