-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT support #956
Comments
Thank you for your kind words! We'll support for MQTT for sure in the future, but we should finish with the brokers already in backlog at first 😞 |
@Timtam94 what lib are you currently using for MQTT? |
Thanks for your reply! I am currently using paho-mqtt |
How stable it is? It looks not well maintained |
As I know, this is the only one lib for MQTT in python |
Indeed, I am not aware of another library than that. So far I had no issues with it. In the industrial sector, MQTT is one of the major protocols, despite it's age. |
There's also an async wrapper for |
Yep, I known about it |
aiomqtt's dependencies are minimal. Here they are from pyproject.toml [tool.poetry.dependencies]
python = "^3.8"
paho-mqtt = "^2.1.0"
typing-extensions = {version = "^4.4.0", markers = "python_version < '3.10'"} Paho recently had a v2 release which aiomqtt is using. Paho uses a legacy callback system and is rather ugly (very non pythonic) to work with. The aiomqtt team is careful not to couple too deep into paho client as to ensure aiomqtt remains easy to maintain. The wrapper is light but non trivial. aiomqtt is likely worth coupling for this reason. |
I know, it's not native mqtt, but you can already use mqtt via the RabbitMQ MQTT Plugin. |
This looks great too. |
Yeah, but it is still imperative syntax Is it really maintained by the man, created anyio and aspcheduler? I think, we can contact with him and use this project as an underline client this case |
Hi there,
in a lot of my projects in the IoT space I tend to work with RabbitMQ and Kafka but also MQTT. I would really appreciate a framework such as yours, that combine these protocols into one.
Thank you very much for your work!
The text was updated successfully, but these errors were encountered: