This is a Mqtt broker for embedded devices, developed in C++, FreeRTOS to use advanced multitasking capabilities, and arduino core. Tested in an Esp32 and esp8266.
Currently I use a Raspi with Mosquito as a broker to distribute the data from the Ahoy DTU and a Shelly Pro3EM. This also works very well.
Now I want to replace the Raspi with the broker with an ESP32 with PicoMqtt. The Ahoy DTU also connects to the ESP32, but the Shelly Pro3EM doesn't connect very well.
The Shelly Pro3EM publishes a data set about every 3 seconds. With the Raspi there is no problem. With the ESP32, most of them are lost.
In the diagnostics window of the Shelly there is a message with "MQTT0 queue overflow!".
shelly_notification:163 Status change of em:0:
{"id":0,"a_act_power":4.1,"a_aprt_power":66.2,"a_current":0.291,"a_pf":0.52,"a_voltage":227.9,"b_act_power":177.4,"b_aprt_power":263.5,"b_current":1.153,"b_pf":0.76,"b_voltage":228.6,"c_act_power":93.0,"c_aprt_power":104.1,"c_current":0.455,"c_pf":0.91,"c_voltage":228.9,"n_current":null,"total_act_power":274.478,"total_aprt_power":433.737,"total_current":1.899}
shos_mqtt_conn.c:857 MQTT0 queue overflow!
shos_mqtt_conn.c:857 MQTT0 queue overflow!
Hello,
Currently I use a Raspi with Mosquito as a broker to distribute the data from the Ahoy DTU and a Shelly Pro3EM. This also works very well.
Now I want to replace the Raspi with the broker with an ESP32 with PicoMqtt. The Ahoy DTU also connects to the ESP32, but the Shelly Pro3EM doesn't connect very well.
The Shelly Pro3EM publishes a data set about every 3 seconds. With the Raspi there is no problem. With the ESP32, most of them are lost.
In the diagnostics window of the Shelly there is a message with "MQTT0 queue overflow!".
I tried with PicoMQTT with the same result.
Any ideas?
BR Gerd