Connection lost after 3-4hrs with update version 13.0.1 #1446

maurcabezas · 2022-12-01T08:18:47Z

maurcabezas
Dec 1, 2022

After having the system working perfectly for the last two months, I did the update to the current version, and now the system is working well for around 3-4 hrs.. then no connection.. I have to reset manually and start working again.. for no more than 4 hrs. When is not working the build in led of the esp32-cam module is blinking slowly.. any advice?
Just to say that before it was working perfect, thus I do not think is problem of the SD memory.

Answered by jomjol

Dec 5, 2022

I suggest to update to v13.0.4. There was an update with respect to MQTT

View full answer

caco3 · 2022-12-03T19:57:38Z

caco3
Dec 3, 2022
Collaborator

Do you use MQTT?
There is a stability issue which can cause the device to start hanging.
Restart it and check the Log!

You could try the latest rolling which hopefully brings improvement, see #1455

1 reply

maurcabezas Dec 5, 2022
Author

Yes, I am using MQTT, this mosquito broker log after restart of esp32cam AI:

2022-12-05 11:16:12: New connection from 10.0.1.62:55361 on port 1883.
2022-12-05 11:16:12: Client AIOTED-54:43:B2:AA:AC:AC already connected, closing old connection.
2022-12-05 11:16:12: New client connected from 10.0.1.62:55361 as AIOTED-54:43:B2:AA:AC:AC (p2, c1, k1859, u'mqtt_user').
2022-12-05 11:16:13: Client AIOTED-54:43:B2:AA:AC:AC disconnected.
2022-12-05 11:16:13: New connection from 10.0.1.62:55362 on port 1883.
2022-12-05 11:16:13: New client connected from 10.0.1.62:55362 as AIOTED-54:43:B2:AA:AC:AC (p2, c1, k1859, u'mqtt_user').
2022-12-05 11:16:13: Client AIOTED-54:43:B2:AA:AC:AC disconnected.
2022-12-05 11:16:13: New connection from 10.0.1.62:55363 on port 1883.
2022-12-05 11:16:13: New client connected from 10.0.1.62:55363 as AIOTED-54:43:B2:AA:AC:AC (p2, c1, k1859, u'mqtt_user').
2022-12-05 11:16:14: Client AIOTED-54:43:B2:AA:AC:AC disconnected.
2022-12-05 11:16:14: New connection from 10.0.1.62:55364 on port 1883.
2022-12-05 11:16:14: New client connected from 10.0.1.62:55364 as AIOTED-54:43:B2:AA:AC:AC (p2, c1, k1859, u'mqtt_user').

And this is the log of AI on the edge

2022-12-05T10:17:48 <INF> [MAIN] =============================================================================================
2022-12-05T10:17:48 <INF> [MAIN] =================================== Main Started ============================================
2022-12-05T10:17:48 <INF> [MAIN] =============================================================================================
2022-12-05T10:17:49 <INF> [MAIN] Branch: 'HEAD', Revision: 575d59d, Date/Time: 2022-11-28 20:04, Web UI: Release: v13.0.1 (Commit: 575d59d)
2022-12-05T10:17:49 <INF> [MAIN] Reset reason: Via esp_restart
2022-12-05T10:17:49 <WRN> [MAIN] Web UI version does not match firmware version!
2022-12-05T10:17:51 <INF> [MAIN] Initialization completed successfully!
2022-12-05T10:17:52 <INF> [FLOW MQTT] Digitizer interval is 12.4 minutes => setting MQTT LWT timeout to 31.0 minutes.
2022-12-05T10:17:52 <INF> [MQTT INTERFACE] URI: mqtt://10.0.1.42:1883, clientname: AIOTED-54:43:B2:AA:AC:AC, user: mqtt_user, password: XXXXXXXX, maintopic: powermeter, last-will-topic: powermeter/connection, keepAlive: 1859
2022-12-05T10:17:52 <INF> [MQTT INTERFACE] Init
2022-12-05T10:17:52 <INF> [FLOW MQTT] Digitizer interval is 12.4 minutes => setting MQTT LWT timeout to 31.0 minutes.
2022-12-05T10:17:52 <INF> [MQTT INTERFACE] Init
2022-12-05T10:17:52 <INF> [MQTT INTERFACE] Connected
2022-12-05T10:17:52 <INF> [MQTT SERVER] MQTT - Sending Homeassistant Discovery Topics (Meter Type: energy, Value Unit: kWh , Rate Unit: kW)...
2022-12-05T10:17:53 <INF> [MQTT INTERFACE] Init successful

For now it has been working for almost a day:

And this is the log when its fail:

2022-12-04T14:13:53	<WRN>	[MAIN] Web UI version does not match firmware version!
2022-12-04T14:13:55	<INF>	[MAIN] Initialization completed successfully!
2022-12-04T14:13:56	<INF>	[FLOW MQTT] Digitizer interval is 12.4 minutes => setting MQTT LWT timeout to 31.0 minutes.
2022-12-04T14:13:56	<INF>	[MQTT INTERFACE] URI: mqtt://10.0.1.42:1883, clientname: AIOTED-54:43:B2:AA:AC:AC, user: mqtt_user, password: XXXXXXXX, maintopic: powermeter, last-will-topic: powermeter/connection, keepAlive: 1859
2022-12-04T14:13:56	<INF>	[MQTT INTERFACE] Init
2022-12-04T14:13:56	<INF>	[MQTT INTERFACE] Init successful
2022-12-04T14:13:56	<INF>	[FLOW MQTT] Digitizer interval is 12.4 minutes => setting MQTT LWT timeout to 31.0 minutes.
2022-12-04T14:13:56	<INF>	[MQTT INTERFACE] Connected
2022-12-04T14:13:56	<INF>	[MQTT SERVER] MQTT - Sending Homeassistant Discovery Topics (Meter Type: energy, Value Unit: kWh , Rate Unit: kW)...
2022-12-04T14:13:57	<INF>	[MQTT INTERFACE] Init
2022-12-04T14:13:57	<INF>	[MQTT SERVER] Publishing static MQTT topics...
2022-12-04T14:13:57	<INF>	[MQTT SERVER] Publishing system MQTT topics...
2022-12-04T14:13:57	<WRN>	[MQTT INTERFACE] Could not start client (ret=-1), retrying...
2022-12-04T14:13:57	<INF>	[MQTT INTERFACE] Init successful
2022-12-04T14:13:57	<INF>	[MQTT INTERFACE] Connected
2022-12-04T14:13:58	<WRN>	[MQTT INTERFACE] Could not start client (ret=-1), retrying...
2022-12-04T14:13:59	<WRN>	[MQTT INTERFACE] Could not start client (ret=-1), retrying...

Thank you for your help and effort!

jomjol · 2022-12-05T17:49:01Z

jomjol
Dec 5, 2022
Maintainer

I suggest to update to v13.0.4. There was an update with respect to MQTT

5 replies

maurcabezas Dec 6, 2022
Author

Thank you I did it now.. so for now working perfect!

maurcabezas Dec 7, 2022
Author

Still the problem, in less than 24hrs it has been disconnected twice, I al ready have version 13.0.4, what more I could try?
Thank you

caco3 Dec 7, 2022
Collaborator

use 13.0.5 :)

Kreatinbulle Dec 7, 2022

similar thing here - already on 13.0.5

caco3 Dec 7, 2022
Collaborator

@Kreatinbulle Please provide log file in debug level, else its hard to understand the problem!

I have several devices running and they all are quite stable now!

maurcabezas · 2022-12-08T15:08:51Z

maurcabezas
Dec 8, 2022
Author

UPDATE:
In my case, It seems wiith version 13.0.5 I do not have that problem (for now more than 1 day without loose connection.

1 reply

maurcabezas Dec 8, 2022
Author

Ok, is starting to fail again :( This is the log.

[       4] 2022-12-08T21:12:36 <INF> [MAIN] Reset reason: Via esp_restart
[       8] 2022-12-08T21:12:40 <INF> [MAIN] =================================================
[       8] 2022-12-08T21:12:40 <INF> [MAIN] ================== Main Started =================
[       8] 2022-12-08T21:12:40 <INF> [MAIN] =================================================
[      10] 2022-12-08T21:12:42 <INF> [MAIN] Initialization completed successfully!
[       4] 2022-12-08T21:37:48 <INF> [MAIN] =================================================
[       4] 2022-12-08T21:37:48 <INF> [MAIN] ==================== Startup ====================
[       4] 2022-12-08T21:37:48 <INF> [MAIN] =================================================
[       4] 2022-12-08T21:37:48 <INF> [MAIN] Branch: 'HEAD', Revision: e23c89a, Date/Time: 2022-12-06 19:34, Web UI: Release: v13.0.5 (Commit: e23c89a)
[       4] 2022-12-08T21:37:48 <INF> [MAIN] Reset reason: Exception/panic
[       8] 2022-12-08T21:37:52 <INF> [MAIN] =================================================
[       8] 2022-12-08T21:37:52 <INF> [MAIN] ================== Main Started =================
[       8] 2022-12-08T21:37:52 <INF> [MAIN] =================================================
[      10] 2022-12-08T21:37:54 <INF> [MAIN] Initialization completed successfully!
[      10] 2022-12-08T21:37:54 <WRN> [TFLITE] Restarted due to an Exception/panic! Postponing first round start by 5 minutes to allow for an OTA or to fetch the log!
[      10] 2022-12-08T21:37:54 <WRN> [TFLITE] Setting logfile level to DEBUG until the next reboot!
[      35] 2022-12-08T21:38:19 <DBG> [MAIN SERVER] info_get_handler
[      35] 2022-12-08T21:38:19 <DBG> [MAIN SERVER] info_get_handler
[      35] 2022-12-08T21:38:19 <DBG> [MAIN SERVER] info_get_handler
[      46] 2022-12-08T21:38:30 <DBG> [OTA FILE] log_get_last_part_handler
[      80] 2022-12-08T21:39:04 <DBG> [OTA FILE] log_get_last_part_handler
[      83] 2022-12-08T21:39:07 <DBG> [OTA FILE] log_get_last_part_handler
[      85] 2022-12-08T21:39:09 <DBG> [OTA FILE] log_get_last_part_handler
[     123] 2022-12-08T21:39:47 <DBG> [OTA FILE] log_get_last_part_handler
[     153] 2022-12-08T21:40:18 <DBG> [OTA FILE] log_get_last_part_handler
[     308] 2022-12-08T21:42:53 <DBG> [OTA FILE] log_get_last_part_handler

Any idea? version 13.0.5 :(

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Connection lost after 3-4hrs with update version 13.0.1 #1446

{{title}}

Replies: 3 comments 7 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Connection lost after 3-4hrs with update version 13.0.1 #1446

maurcabezas Dec 1, 2022

Replies: 3 comments · 7 replies

caco3 Dec 3, 2022 Collaborator

maurcabezas Dec 5, 2022 Author

jomjol Dec 5, 2022 Maintainer

maurcabezas Dec 6, 2022 Author

maurcabezas Dec 7, 2022 Author

caco3 Dec 7, 2022 Collaborator

Kreatinbulle Dec 7, 2022

caco3 Dec 7, 2022 Collaborator

maurcabezas Dec 8, 2022 Author

maurcabezas Dec 8, 2022 Author

maurcabezas
Dec 1, 2022

Replies: 3 comments 7 replies

caco3
Dec 3, 2022
Collaborator

maurcabezas Dec 5, 2022
Author

jomjol
Dec 5, 2022
Maintainer

maurcabezas Dec 6, 2022
Author

maurcabezas Dec 7, 2022
Author

caco3 Dec 7, 2022
Collaborator

caco3 Dec 7, 2022
Collaborator

maurcabezas
Dec 8, 2022
Author

maurcabezas Dec 8, 2022
Author