Migrate to aiomqtt #371
Open
Migrate to aiomqtt #371
Conversation
This file contains hidden or 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
bj00rn
force-pushed
the
chore/aiomqtt
branch
2 times, most recently
from
c4e8dbb to
8fd4c71
Compare
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.
Replace gmqtt with aiomqtt (async wrapper around paho-mqtt). I have major issues with getting TLS working when running broker behind reverse proxy. I've scoured the Issues section at gmqtt and TLS support seems patchy.
Sorry for spamming PRs 🤓
Rationale
Might seem a bit backward since the resent migration from paho-mqtt but aiomqtt is a wrapper around paho with async support.
gmqtt
seems to have patchy TLS support
not well maintained
aiomqtt (aka mqtt-asyncio)
well maintained 3+ releases 2025
good community support since uses underlying paho-mqtt
Working TLS
supports websockets and unix file connections