emsesp/EMS-ESP

ems-esp might not reconnect to mqtt in some situations, after connection is lost

hamster65 opened this issue · 2 comments

hamster65 commented

Hi,

my raspberry was not reachable and I had to to power cycle it. Two days later, I noticed that data was not logged from the boiler. EMS-ESP showed that the connection to the broker was lost (I think it said "TCP error"). I rebooted ems-esp from the web interface and it worked again.

I'd have expected it to automatically reconnect to the broker... and it does, when I stop and start the mqtt service und the PI. So it seems that in some situations, this does not work.
I also found #705 where a similar observation was reported.

My version is v2.2.3b0

proddy commented

Yes this is a known problem in the Async and MQTT library. See emsesp/EMS-ESP32#42

The code needs changing to implement a more basic try & re-try mechanism.

  • 👍1
hamster65 commented

Ah, I didn't see this issue. Thanks!