Problems connecting to a broker with QtMqtt
-
@glasen77 not that I'm an expert with MQTT protocol, but comparing your client with Qt simpleclient example, it seems that you're not subscribing to any topic at all.
From this tutorial it looks like even if you connect successfully to the MQTT broker (or server) then you need to register your client to "publish" or "subscribe" for a particular topic. -
The problem is that i can't subscribe to any topic because the connection is not completed. Is it possible that i do set the hostname in a wrong way? Or can i only use QtMqtt with QApplication and not QCoreApplication?
The only difference between my code and the simpleclient example is that my code only uses the command line.
-
You should also connect the QMqttClient::errorChanged signal to see if you have something going wrong.
-
You should also connect the QMqttClient::errorChanged signal to see if you have something going wrong.
-
@SGaist : Also tried that. "errorChanged" does nothing. I've completely run out of ideas.
@glasen77
So basically your sample stays in
QMqttClient::Connecting state ?do you have multiple clients ?
seems you have multiple plugins.
you do follow the rule that docs says:
"The connection request must contain a unique client identifier. " -
@glasen77
So basically your sample stays in
QMqttClient::Connecting state ?do you have multiple clients ?
seems you have multiple plugins.
you do follow the rule that docs says:
"The connection request must contain a unique client identifier. "@mrjj :
At the moment there is only one client running. And setting an identifier is optional because the class will do that for you:Each client needs to have a unique ID to be able to connect to an MQTT broker. If no client ID is specified by the user, one will be generated automatically when a connection is established.
I can run multiple versions of the "simpleclient" example without specifying an identifier.
-
@glasen77 ok, so at this point another difference I see is that you're using your code as a plugin vs the simpleclient being just an app.
Is there a real need to use a plugin?
Could you try your code as a regular app to see if it works? This way you could discard coding errors regarding network and just focus on the plugin side... -
@glasen77 ok, so at this point another difference I see is that you're using your code as a plugin vs the simpleclient being just an app.
Is there a real need to use a plugin?
Could you try your code as a regular app to see if it works? This way you could discard coding errors regarding network and just focus on the plugin side...Yes, i need to use a plugin. But i solved the problem:
After playing around with the Unit-tests of QtMqtt i found out that you explicitly need to inherit from QObject for your Mqtt-Class. Because i'm already inheriting from QObject in the interface for my PluginClass, it was not possible to inherit another time (Don't ask me why, i'm new to C++).
I solved my problem by making another class named MqttWrapper which calls all the code to establish the connection to the broker. This class is called from my DummyPlugin-Class. Now the code works perfectly.
-
Yes, i need to use a plugin. But i solved the problem:
After playing around with the Unit-tests of QtMqtt i found out that you explicitly need to inherit from QObject for your Mqtt-Class. Because i'm already inheriting from QObject in the interface for my PluginClass, it was not possible to inherit another time (Don't ask me why, i'm new to C++).
I solved my problem by making another class named MqttWrapper which calls all the code to establish the connection to the broker. This class is called from my DummyPlugin-Class. Now the code works perfectly.
@glasen77 Hello, I have the same exact problem as yours. Can you please explain me better how did you solve it?
