Unreliable behaviour with reconnections about arduino-mqtt HOT 3 OPEN

I created a minimal (working) example for the Arduino IDE:

#include <Arduino_ConnectionHandler.h>
#include <WiFi.h>
#include <SSLClient.h>
#include <MQTT.h>
#include "certificates.h"

WiFiClient tcpClient;
SSLClient sslClient = SSLClient(tcpClient, TAs, (size_t)TAs_NUM, A0, SSLClient::SSL_WARN);
MQTTClient* mqttClient = new MQTTClient(192);
WiFiConnectionHandler wifiConnectionHandler(ssid, password);
int lastPublish = 0;

void setup() {
  wifiConnectionHandler.addCallback(NetworkConnectionEvent::CONNECTED, onNetworkConnect);
  wifiConnectionHandler.addCallback(NetworkConnectionEvent::DISCONNECTED, onNetworkDisconnect);
  wifiConnectionHandler.addCallback(NetworkConnectionEvent::ERROR, onNetworkError);
  mqttClient->begin(HiveMQ_URL, 8883, sslClient);
}

void loop() {
  wifiConnectionHandler.check();
  if (mqttClient->connected()) {
    mqttClient->loop();
    int currentMillis = millis();
    if (currentMillis - lastPublish > 10000) {
      mqttClient->publish("topic", "log");
      lastPublish = currentMillis;
    }
  }
}

void onNetworkConnect() {
  Serial.println(">>>> CONNECTED to network");
  mqttClient->connect(clientId, username, password);
}

void onNetworkDisconnect() {
  Serial.println(">>>> DISCONNECTED from network");
}

void onNetworkError() {
  Serial.println(">>>> ERROR");
}

To make the example work, a certificates.h needs to be generated from the SSLClient library.
If you are having problems with this and using HiveMQ to test, I can provide you with my generated file.

Hope someone can help me figure this out :)

from arduino-mqtt.

Same problem here, I'm using TinyGSM with qos = 0 everithing works fine, even in reconnections... when I change to qos = 1 and a disconnection occurs, it becomes very unstable.

obs.: I'm using AWS IoT Core broker.

from arduino-mqtt.

Hi @magmilo , updates here!

I solved this problem here for qos1 at least, because AWS IoT Core has no support for qos2, the solution was holding the next publications depending on PUBACK. I think it's something related to how to handle the PUBACK from broker, but doing that worked fine here. Including prepareDuplicated function with this adapted solution (#293) , everything works great!

@256dpi First, congratulations for this excellent job, if you can add this to the Readme I think it will help a lot!

Another thing that you could add is that your library can be installed with arduino-cli named as MQTT

Hi @256dpi I think I have a "kind of bug" in the way the duplicate is handled.

If you use the new function prepareDuplicate(duplicateID) it will publish as duplicate OK. But internally, it will not reset the class variable nextDupPacketID after publishing, thus every packet published afterwars will be marked as duplicate with the same ID unless you call prepareDuplicate(0) . Maybe it should be a good idea to reset nextDupPacketID after publish (successful or not)?

from arduino-mqtt.