Skip to content
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.

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

Closed
hamster65 opened this issue Jun 3, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@hamster65
Copy link

hamster65 commented Jun 3, 2021

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

@hamster65 hamster65 added the bug Something isn't working label Jun 3, 2021
@proddy
Copy link
Collaborator

proddy commented Jun 3, 2021

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.

@hamster65
Copy link
Author

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants