search

martin-ger / uMQTTBroker

MQTT Broker library for ESP8266 Arduino
MIT License
448 stars 106 forks source link

Broker doesn't accept new connections after 24h running? #64

Open JFRosado opened 2 years ago

JFRosado commented 2 years ago

I'm using this library on a ESP8266 (i've tried wemos D1 mini, nodemcu, etc). The broker is running and also publishing a value to itself (topic /Home/Voltage). I've another esp8266 (let's call it board2) that publishes to the broker (topic /Home/Current) and subscribes the topic /Home/Voltage.

After 24h (this has happen with any of the mentioned boards used to the broker), I'm unable to connect to the broker with any other client, although the client in board 2 is still connected to the broker and receiving the subscribed topic.

martin-ger commented 2 years ago

Did you use the setting "lwip Variant: 1.4 High Bandwidth" in the "Tools" menu?

JFRosado commented 2 years ago

Yes, I did. I checked that when i changed from wemos to nodemcu, because on the first try I wasn't sure if I had used it.

JFRosado commented 2 years ago

OK..I've found out if i go down to core 2.5.0 on Arduino IDE, i no longer have the issue of blocking after 24h. The problem is that using the "lwip Variant: 1.4 High Bandwidth" the web page i have running on the esp8266 is almost "dead", taking forever to answer and every time i try to render the webpage, i get packet loss on a ping i'm running to the esp8266. If i use "lwip Variant: 2.0 High Bandwidth", the webpage is fine...

abdasgup commented 1 year ago

I'm running uMQTT on a ESP8266 as broker, subscriber and publisher. PubSubClient library on another ESP8266 as subscriber and on another one as publisher. After 5-6 minutes, the broker stops accepting any connection and both PubSubClient starts getting -4 (timeout), even though the device (on which broker is running) can still publish message.

Those ESP8266s are programmed to go into deepsleep for 2 minutes and they do disconnect their connection before going to sleep, which shows up on broker (when it works). I have also powered down and powered back up on those ESP8266 to see if it was the PubSubClient's fault. But nothing fixed this issue. Only solution is to reboot the ESP8266 on which uMQTT broker is running.

I have tried to turn on debug of this library by including #define MQTT_DEBUG_ON as the first line in the ino file (before even #include this library. But nothing shows up on serial monitor. So I have absolutely no idea what is causing this library to not accept any new connection. Additionally I have tried changing IwIP to "v2 Higher Bandwidth" and that made no difference.

As a side note, I do also have a web server running on the same device and it's accepting connection perfectly fine, even when this issue is occurring.