Can keep alive be extended to try & fix MQTT disconnects? #465
Unanswered
anthemia010101
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The wifi connection was very stable but my m5stickcplus2 inside my Daikin ASHP is now dropping quite a bit.Looking in the container logs in Portainer I can see a lot of
2024-10-14T17:11:52: New client connected from 192.168.0.110:59465 as ESPAltherma-dev (p2, c1, k15, u'mqttu1').
2024-10-14T17:13:26: Client ESPAltherma-dev has exceeded timeout, disconnecting.
I have another device sending data to MQTT and it sets keep alive k=60
Is this a good idea for espaltherma to help stop the disconnects?
I couldn't see where exactly in the code, if it's a good idea, can anyone advise where?
I also just looked and got these already connected, then closed conncetion, then exceeded timeout
2024-10-14T17:24:28: New client connected from 192.168.0.110:59479 as ESPAltherma-dev (p2, c1, k15, u'mqttu1').
2024-10-14T17:24:52: Client ESPAltherma-dev already connected, closing old connection.
2024-10-14T17:24:52: New client connected from 192.168.0.110:59477 as ESPAltherma-dev (p2, c1, k15, u'mqttu1').
2024-10-14T17:24:52: Client ESPAltherma-dev closed its connection.
2024-10-14T17:24:58: New connection from 192.168.0.110:59480 on port 1883.
2024-10-14T17:24:58: New client connected from 192.168.0.110:59480 as ESPAltherma-dev (p2, c1, k15, u'mqttu1').
2024-10-14T17:25:26: Client ESPAltherma-dev has exceeded timeout, disconnecting.
Beta Was this translation helpful? Give feedback.
All reactions