Experimental MQTT support #5173
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bagder
force-pushed
the
bagder/mqtt
branch
2 times, most recently
from
9ef5659
to
9d16ac3
Compare
bagder
pushed a commit
that referenced
this pull request
Apr 3, 2020
Support MQTT using the mqtt://host/topic URL scheme. 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: curl http://host/home/bedroom/temp Example publish: curl -d 80 http://host/home/bedroom/dimmer Limitations: - No username support - Only QoS level 0 is implemented for publish - No way to set retain flag for publish - No username/password support - No TLS (mqtts) support Co-authored-by: Daniel Stenberg Closes #5173
bagder
pushed a commit
that referenced
this pull request
Apr 6, 2020
Support MQTT using the mqtt://host/topic URL scheme. 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: curl http://host/home/bedroom/temp Example publish: curl -d 80 http://host/home/bedroom/dimmer Limitations: - No username support - Only QoS level 0 is implemented for publish - No way to set retain flag for publish - No username/password support - No TLS (mqtts) support Co-authored-by: Daniel Stenberg Closes #5173
bagder
pushed a commit
that referenced
this pull request
Apr 7, 2020
Support MQTT using the mqtt://host/topic URL scheme. 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: curl http://host/home/bedroom/temp Example publish: curl -d 80 http://host/home/bedroom/dimmer Limitations: - No username support - Only QoS level 0 is implemented for publish - No way to set retain flag for publish - No username/password support - No TLS (mqtts) support Co-authored-by: Daniel Stenberg Closes #5173
bagder
force-pushed
the
bagder/mqtt
branch
2 times, most recently
from
423d99d
to
a64b969
Compare
bagder
force-pushed
the
bagder/mqtt
branch
3 times, most recently
from
3725c62
to
b8ea009
Compare
The mqtt server is started using a "random" port.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is @zagor's initial work taken a bit further, with polish and test cases (1190 - 1193).
Merge plan
Once the CI builds are green and the checkboxes here are all checked, we merge. This feature is EXPERIMENTAL anyway and must be explicitly enabled in the build so therefore I'm allowing this to get merged even in feature freeze. Assuming it looks fine.
Todo and remaining lissues
The wiki has more details.
Videos of the initial work
Videos showing how we got here: episode 1 episode 2