Mosquitto MQTT Broker

Hi
I run Mosquitto on Pi with a connection from ESP32.
I read data with ESP32 from Xiaomi temperature. Everything is fine, but after a while I lose contact with MQTT and I can’t publish anything. I checked and it doesn’t go into the “if (client.connected())” anymore, just in ” else { ”

void publish(const char* addr, char* valueName, char* value) {
char topic[50];
sprintf(topic, “%s/%s/%s”, MQTT_PREFIX, addr, valueName);
if (client.connected()) {
Serial.print(“connected —— “);
// client.publish(topic, value);
client.loop();
// Serial.print(“dupa loop – “);
}
else {
Serial.println(“don’t connected—– “);
// reconnect();
// Serial.println(“Dupa reconectare – “);
}

Best regards
Mihai

Hi Steve,

Thanks for your sharing the information.I have a question when using mosquitto and need your help.

I have mosquitto broker running on the Ubuntu, use 6 embedded devices as the client for publishing information, and another client running on the Ubuntu subscribes to the information.However, some embedded devices will be disconnected after running for 1 week or 2 weeks, and the log infomation,
1589849321: New connection from 192.168.1.114 on port 1883.
1589849322: Socket error on client , disconnecting.

The mosquitto.conf is as follows,
message_size_limit 0
port 1883
max_connections -1
require_certificate false
persistence false

I read a few posts you wrote and found that I did not use a CA certificate. Is this the problem? Can I use mosquitto normally without using this method?

Regards,

Andrew

Hi Steve.
Thanks for your publications. I recently had a question for you and your answer was very helpful. I have another one. I installed Mosquitto broker in Raspberry Pi. After a lot of problems I finally managed to have it running. I have one application (IoTView by an industrial software manufacturer) who is accessing the broker, suscribing and publishing. At the same time I have another application (Web Studio) from the same manufacturer running on a PC, acting as a server who records the information on a database. On the tests, only one of them (IoTView) could run with no problems, while the other one stop working. I have been doing modifications for several months thinking the problem was on the application. Yesterday the manufacturer let me know the problem was on the Broker running on Raspberry Pi. It could not attend two connections at the same time…. Since you know this subject more than anyone I know, I would like your opinion. Is that so? It makes no sense for me that the broker on Raspberry Pi can attend only one connection at the same time. Is there not a parameter whom I can modify to alter this? The manufacturer reccomendation was to switch and install a broker on the Server. The PC running windows.