-
## Feature Request
MQTT 3.1.1 is an ancient protocol (2014), that has been superseded for many years now by MQTTv5 (2018), it comes with a whole heap of important feature for IoT that were overlook…
-
Using org. eclipse. paho. mqttv5. client exception, connection returned error code 130.
windows11
nanomq-0.21.10-windows-x86_64
-
Hi I have found the [mqtt-format](https://github.com/TheNeikos/cloudmqtt/tree/main/mqtt-format) library and it looks promising for developing an ESP32 MQTT broker. I have already got it running using …
dscso updated
1 month ago
-
Even with v2.0.0 now released, the default protocol is still MQTTv311:
https://github.com/eclipse/paho.mqtt.python/blob/ebffdc2ca0a43fd87dfd270bbb16007591139626/src/paho/mqtt/client.py#L735
Isn'…
-
We've been using this library for a while and have been really happy with the performance and usage. However, we recently took a look at how we could improve some of our cloud communication and discov…
-
**Which AWS Services is the feature request for?**
AWS IoT Core
**Is your feature request related to a problem? Please describe.**
AWS IoT Core released support for MQTTv5 in November 2022 ([…
mixja updated
1 month ago
-
Allow the client to connect in accordance to the [MQTT Version 5.0 specification](http://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html).
It would be great to have it running as soon as the RFC …
-
- [x] Bug exists Release Version 1.2.5 ( Master Branch)
- [ ] Bug exists in MQTTv3 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
- [ ] Bug exists in MQTTv5 Client on Snapshot Version 1.…
-
It needs a clientID to initialize the Network::Client::MQTTv5, but if we don't have clientID, how to connect to the server? for example, connect to a remote broker.
-
relates to https://github.com/inovex/mqtt-stresser/issues/53