MQTT stops sending after update to 11.2.0 #953
Comments
caco3
changed the title
|
Seems i have a very similar issue. MQTT function being called, but the connection etc not being established. Any further help most welcome again :) |
|
2022-08-30T00:25:10: Time zone set to CET-1CEST,M3.5.0,M10.5.0/3 [MQTT] |
|
Should be fixed in #971 |
|
I had exactly the same issue. Had to reboot with MQTT disabled, then reboot one more time with MQTT enabled, then it started to work again.
|
|
I just tested it with my version: At 14:48:35 connection is lost (I shut down my MQTT-broker) and after a view not working transmission (e.g. 14:48:35), the connection is automatically restored at 14:59:20 (MQTT-broker switch on) and the transmission is working. I'm using the following version: |
|
Just experienced an issue after reboot (Broker was up and running ) => see message |
|
I tried to improve it further, see #980 and the comments to it! |
|
Today I have updated my device to the version 11.2.0 and since then there are no MQTT messages issued. A search brought me to this thread. So I have tried the described workaround: |
|
Can you send a log file from start until the first round has been done? |
|
Thanks for your aswer and offering your help. I have just tried it again, since I want to send you the log file and now it worked. I do not believe in mystery, so I have checked the log file from yesterday. I guess I did not wait long enough before I rebooted the system with the re-activated MQTT settings.
|
|
Today I have rebooted the ESP32 and after that it does not send any MQTT messages. So i tried to use the disable/enable workaround but it does not help. Maybe it helps to understand why the MQTT service does not work in some cases. Here is an extract of the logfile: MQTT disabled by configuration page MQTT enabled again Thanks a lot in advance |
|
@tschaeffer2 : which version are you using exactly? There is no info about the MQTT, this is true for the current master version. Only with the rolling, there is currently an extended logging for the MQTT. |
|
I am using master - v11.2.0 - 2022-08-28 |
|
Then unfortuneatly there is no further info in the log file. You could upgrade, then there would be the chance to find something, when this happens next time. |
|
also in latest rolling it is not working stable. :( I just to not understand why MQTT is so unstable here. |
|
I've had the same problem. After an update to the "ROLLING" version, MQTT worked again. |
|
Same issue here. no more MQTT messages in 11.2.0, no matter if I disable/enable/reboot. |
|
You can change the brand directly on the main page: |
|
Or even easier, use the latest auto build of |
|
thanks for these pointers. I updated to the rolling release and can confirm that MQTT is working perfectly fine in that version. |
Yesterday I updated both my devices to the latest release.
Both are setup to send MQTT messages. One of them continued to send fine, the other one stopped sending.
To fix it, I had to:
Simply saving the config seemed not to work, neither did a restart! I explicitely needed a restart with disabled MQTT config...
There is no note in the log about a broker communication error or so:
I think this has nothing to do with the firmware update, but I restarted it so many times and never had an issue.
Also my 2nd device did not have the issue.
@jomjol Off Topic: I suggest to show ver firmware version in the log on startup for easier bug tracing.
The text was updated successfully, but these errors were encountered: