MQTT TLS reboot error #23217

ece1815868 · 2025-03-31T08:07:59Z

ece1815868
Mar 31, 2025

Hello, i have an sudden issue with sonoff/nodemcu devices using tasmota firmware. I use a hivemq mqtt tls server at port 8883 for years without problem, but suddenly last day devices started to reset themselves . i entered on console on each device and it shows it tries to connect and says TLS error 0. Unable to connect to server rc-2. Sometimes it will connect but after many reboots. I updated to latest 14.5.0 but to no avail. The strange is that after first try and failure to connect it seems to restart itself. heres a log:

<134>tasmota-B0CCB8-3256 ESP-9.862 CFG: C	192.168.50.5	31/03 10:59:50.862	
<134>tasmota-B0CCB8-3256 ESP-CMD: Grp 0, Cmd 'LOGHOST', Idx 1, Len 13, Pld 192, Data '192.168.50.91'	192.168.50.5	31/03 10:59:50.885	
<134>tasmota-B0CCB8-3256 ESP-CFG: CR 385/699, Busy 0	192.168.50.5	31/03 10:59:50.888	
<134>tasmota-B0CCB8-3256 ESP-RSL: RESULT = {"LogHost":"192.168.50.91"}	192.168.50.5	31/03 10:59:50.888	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '192.168.50.91' (192.168.50.91) in 0 ms	192.168.50.5	31/03 10:59:50.888	
<134>tasmota-B0CCB8-3256 ESP-SRC: Backlog	192.168.50.5	31/03 10:59:50.888	
<134>tasmota-B0CCB8-3256 ESP-CMD: Grp 0, Cmd 'LOGPORT', Idx 1, Len 3, Pld 514, Data '514'	192.168.50.5	31/03 10:59:50.888	
<134>tasmota-B0CCB8-3256 ESP-RSL: RESULT = {"LogPort":514}	192.168.50.5	31/03 10:59:50.888	
<134>tasmota-B0CCB8-3256 ESP-SRC: Backlog	192.168.50.5	31/03 10:59:50.901	
<134>tasmota-B0CCB8-3256 ESP-CMD: Grp 0, Cmd 'TELEPERIOD', Idx 1, Len 3, Pld 300, Data '300'	192.168.50.5	31/03 10:59:50.901	
<134>tasmota-B0CCB8-3256 ESP-RSL: RESULT = {"TelePeriod":300}	192.168.50.5	31/03 10:59:50.904	
<134>tasmota-B0CCB8-3256 ESP-RSL: STATE = {"Time":"2025-03-31T08:59:50","Uptime":"0T00:02:22","UptimeSec":142,"Heap":23,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":25,"MqttCount":0,"POWER":"OFF","Wifi":{"AP":1,"SSId":"Xiaomi_A8A6","BSSId":"8A:30:92:0C:B4:F	192.168.50.5	31/03 10:59:51.376	
<134>tasmota-B0CCB8-3256 ESP-CFG: Saved to flash at FB, Count 128, Bytes 4096	192.168.50.5	31/03 10:59:51.814	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 10:59:51.860	
<134>tasmota-B0CCB8-3256 ESP-HTP: Other	192.168.50.5	31/03 11:00:07.771	
<134>tasmota-B0CCB8-3256 ESP-HTP: Configuration	192.168.50.5	31/03 11:00:09.827	
<134>tasmota-B0CCB8-3256 ESP-HTP: Main Menu	192.168.50.5	31/03 11:00:11.430	
<134>tasmota-B0CCB8-3256 ESP-HTP: Main Menu	192.168.50.5	31/03 11:00:11.515	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:00:11.846	
<134>tasmota-B0CCB8-3256 ESP-HTP: Tools	192.168.50.5	31/03 11:00:12.444	
<134>tasmota-B0CCB8-3256 ESP-HTP: Console	192.168.50.5	31/03 11:00:13.299	
<134>tasmota-B0CCB8-3256 ESP-CMD: SetOption103 1	192.168.50.5	31/03 11:00:23.524	
<134>tasmota-B0CCB8-3256 ESP-SRC: WebConsole from 192.168.50.91	192.168.50.5	31/03 11:00:23.524	
<134>tasmota-B0CCB8-3256 ESP-CMD: Grp 0, Cmd 'SETOPTION', Idx 103, Len 1, Pld 1, Data '1'	192.168.50.5	31/03 11:00:23.526	
<134>tasmota-B0CCB8-3256 ESP-RSL: RESULT = {"SetOption103":"ON"}	192.168.50.5	31/03 11:00:23.530	
<134>tasmota-B0CCB8-3256 ESP-CFG: Saved to flash at FA, Count 129, Bytes 4096	192.168.50.5	31/03 11:00:23.845	
<134>tasmota-B0CCB8-3256 ESP-HDW: ESP8266EX	192.168.50.5	31/03 11:00:29.221	
<134>tasmota-B0CCB8-3256 ESP-UFS: FlashFS mounted with 1992 kB free	192.168.50.5	31/03 11:00:29.222	
<134>tasmota-B0CCB8-3256 ESP-CFG: Loaded from File, Count 129	192.168.50.5	31/03 11:00:29.222	
<134>tasmota-B0CCB8-3256 ESP-QPC: Count 1	192.168.50.5	31/03 11:00:29.223	
<134>tasmota-B0CCB8-3256 ESP-CFG: CR 385/699, Busy 0	192.168.50.5	31/03 11:00:29.230	
<134>tasmota-B0CCB8-3256 ESP-ROT: Mode 1	192.168.50.5	31/03 11:00:29.231	
<134>tasmota-B0CCB8-3256 ESP-SRC: Restart	192.168.50.5	31/03 11:00:29.234	
<134>tasmota-B0CCB8-3256 ESP-Project tasmota - Tasmota Version 14.5.0(TasmoCompiler-esp82664M)-2_7_8(2025-03-20T06:41:27)	192.168.50.5	31/03 11:00:29.237	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:00:29.242	
<134>tasmota-B0CCB8-3256 ESP-WIF: Attempting connection...	192.168.50.5	31/03 11:00:29.243	
<134>tasmota-B0CCB8-3256 ESP-WIF: Connecting to AP1 Xiaomi_A8A6 Channel 11 BSSId 8A:30:92:0C:B4:F6 in mode 11n as tasmota-B0CCB8-3256...	192.168.50.5	31/03 11:00:29.244	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:00:29.247	
<134>tasmota-B0CCB8-3256 ESP-WIF: Attempting connection...	192.168.50.5	31/03 11:00:29.249	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:00:29.251	
<134>tasmota-B0CCB8-3256 ESP-WIF: Connected	192.168.50.5	31/03 11:00:29.252	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '192.168.50.91' (192.168.50.91) in 0 ms	192.168.50.5	31/03 11:00:29.252	
<134>tasmota-B0CCB8-3256 ESP-HTP: Web server active on tasmota-B0CCB8-3256 with IP address 192.168.50.5	192.168.50.5	31/03 11:00:29.466	
<134>tasmota-B0CCB8-3256 ESP-WIF: Sending Gratuitous ARP	192.168.50.5	31/03 11:00:30.117	
<134>tasmota-B0CCB8-3256 ESP-NTP: Sync time...	192.168.50.5	31/03 11:00:30.117	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '2.pool.ntp.org' (44.32.63.52) in 52 ms	192.168.50.5	31/03 11:00:30.117	
<134>tasmota-B0CCB8-3256 ESP-RTC: UTC 2025-03-31T08:00:30Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00	192.168.50.5	31/03 11:00:30.117	
<134>tasmota-B0CCB8-3256 ESP-RTC: Synced by NTP	192.168.50.5	31/03 11:00:30.117	
<134>tasmota-B0CCB8-3256 ESP-MQT: Attempting connection...	192.168.50.5	31/03 11:00:35.605	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved 'a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud' (54.73.92.158) in 76 ms	192.168.50.5	31/03 11:00:35.605	
<134>tasmota-B0CCB8-3256 ESP-MQT: TLS connection error: 0	192.168.50.5	31/03 11:00:35.605	
<134>tasmota-B0CCB8-3256 ESP-MQT: Connect failed to a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud:8883, rc -2. Retry in 10 sec	192.168.50.5	31/03 11:00:35.605	
<134>tasmota-B0CCB8-3256 ESP-QPC: Reset	192.168.50.5	31/03 11:00:36.686	
<134>tasmota-B0CCB8-3256 ESP-APP: Boot Count 112	192.168.50.5	31/03 11:00:38.633	
<134>tasmota-B0CCB8-3256 ESP-ROT: Mode 1	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-SRC: Restart	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-Project tasmota - Tasmota Version 14.5.0(TasmoCompiler-esp82664M)-2_7_8(2025-03-20T06:41:27)	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-WIF: Attempting connection...	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-WIF: Connecting to AP1 Xiaomi_A8A6 Channel 11 BSSId 8A:30:92:0C:B4:F6 in mode 11n as tasmota-B0CCB8-3256...	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-WIF: Connected	192.168.50.5	31/03 11:00:52.735	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '192.168.50.91' (192.168.50.91) in 0 ms	192.168.50.5	31/03 11:00:52.751	
<134>tasmota-B0CCB8-3256 ESP-HTP: Web server active on tasmota-B0CCB8-3256 with IP address 192.168.50.5	192.168.50.5	31/03 11:00:52.970	
<134>tasmota-B0CCB8-3256 ESP-WIF: Sending Gratuitous ARP	192.168.50.5	31/03 11:00:53.532	
<134>tasmota-B0CCB8-3256 ESP-NTP: Sync time...	192.168.50.5	31/03 11:00:53.532	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '2.pool.ntp.org' (83.212.117.131) in 13 ms	192.168.50.5	31/03 11:00:53.532	
<134>tasmota-B0CCB8-3256 ESP-RTC: UTC 2025-03-31T08:00:53Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00	192.168.50.5	31/03 11:00:53.532	
<134>tasmota-B0CCB8-3256 ESP-RTC: Synced by NTP	192.168.50.5	31/03 11:00:53.532	
<134>tasmota-B0CCB8-3256 ESP-MQT: Attempting connection...	192.168.50.5	31/03 11:00:59.038	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved 'a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud' (52.31.149.80) in 7 ms	192.168.50.5	31/03 11:00:59.038	
<134>tasmota-B0CCB8-3256 ESP-MQT: TLS connection error: 0	192.168.50.5	31/03 11:00:59.038	
<134>tasmota-B0CCB8-3256 ESP-MQT: Connect failed to a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud:8883, rc -2. Retry in 10 sec	192.168.50.5	31/03 11:00:59.038	
<134>tasmota-B0CCB8-3256 ESP-HDW: ESP8266EX	192.168.50.5	31/03 11:01:03.431	
<134>tasmota-B0CCB8-3256 ESP-UFS: FlashFS mounted with 1992 kB free	192.168.50.5	31/03 11:01:03.431	
<134>tasmota-B0CCB8-3256 ESP-CFG: Loaded from File, Count 130	192.168.50.5	31/03 11:01:03.447	
<134>tasmota-B0CCB8-3256 ESP-FRC: Some settings have been reset (2)	192.168.50.5	31/03 11:01:03.447	
<134>tasmota-B0CCB8-3256 ESP-CFG: CR 385/699, Busy 0	192.168.50.5	31/03 11:01:03.447	
<134>tasmota-B0CCB8-3256 ESP-ROT: Mode 1	192.168.50.5	31/03 11:01:03.462	
<134>tasmota-B0CCB8-3256 ESP-SRC: Restart	192.168.50.5	31/03 11:01:03.462	
<134>tasmota-B0CCB8-3256 ESP-Project tasmota - Tasmota Version 14.5.0(TasmoCompiler-esp82664M)-2_7_8(2025-03-20T06:41:27)	192.168.50.5	31/03 11:01:03.478	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:01:03.478	
<134>tasmota-B0CCB8-3256 ESP-WIF: Attempting connection...	192.168.50.5	31/03 11:01:03.478	
<134>tasmota-B0CCB8-3256 ESP-WIF: Connecting to AP1 Xiaomi_A8A6 Channel 11 BSSId 8A:30:92:0C:B4:F6 in mode 11n as tasmota-B0CCB8-3256...	192.168.50.5	31/03 11:01:03.494	
<134>tasmota-B0CCB8-3256 ESP-WIF: Checking connection...	192.168.50.5	31/03 11:01:03.494	
<134>tasmota-B0CCB8-3256 ESP-WIF: Connected	192.168.50.5	31/03 11:01:03.494	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '192.168.50.91' (192.168.50.91) in 0 ms	192.168.50.5	31/03 11:01:03.494	
<134>tasmota-B0CCB8-3256 ESP-HTP: Web server active on tasmota-B0CCB8-3256 with IP address 192.168.50.5	192.168.50.5	31/03 11:01:03.682	
<134>tasmota-B0CCB8-3256 ESP-WIF: Sending Gratuitous ARP	192.168.50.5	31/03 11:01:04.222	
<134>tasmota-B0CCB8-3256 ESP-NTP: Sync time...	192.168.50.5	31/03 11:01:04.222	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved '2.pool.ntp.org' (91.217.155.60) in 6 ms	192.168.50.5	31/03 11:01:04.238	
<134>tasmota-B0CCB8-3256 ESP-RTC: UTC 2025-03-31T08:01:04Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00	192.168.50.5	31/03 11:01:04.253	
<134>tasmota-B0CCB8-3256 ESP-RTC: Synced by NTP	192.168.50.5	31/03 11:01:04.253	
<134>tasmota-B0CCB8-3256 ESP-MQT: Attempting connection...	192.168.50.5	31/03 11:01:09.738	
<134>tasmota-B0CCB8-3256 ESP-WIF: DNS resolved 'a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud' (54.73.92.158) in 9 ms	192.168.50.5	31/03 11:01:09.753	
<134>tasmota-B0CCB8-3256 ESP-MQT: TLS connection error: 0	192.168.50.5	31/03 11:01:09.753	
<134>tasmota-B0CCB8-3256 ESP-MQT: Connect failed to a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud:8883, rc -2. Retry in 10 sec	192.168.50.5	31/03 11:01:09.753	

These are the mqtt messages i presume before reboot:

INFO3 = {"Info3":{"RestartReason":{"Exception":9,"Reason":"Exception","EPC":["40252677","00000000","00000000"],"EXCVADDR":"0000083f","DEPC":"00000000","CallChain":["4025221d","40242846","4024277c","402432a8","40242846","4028a576","40242846","4028a576","4028a577","40242a30","40241fe5","40105563","40285823","40241fe5","40242028","4023a31c","4023a798","40242028","40241fe5","4024209c","40283b44","40242028","4…

INFO3 = {"Info3":{"RestartReason":{"Exception":9,"Reason":"Exception","EPC":["4026f021","00000000","00000000"],"EXCVADDR":"000008d3","DEPC":"00000000","CallChain":["4026e950","401008e8","40106111","4000050c","402272f6","4023f75d","4022a098","4022a0d6","401008e8","401010ca","402a7a74","402432ff","40245cab","402428d0","40101158","401008e8","40106111","4000050c","4025a601","4000dd11","4000066d","401008e8","4…

Answered by s-hadinger

Apr 4, 2025

It should be fixed now with #23249

View full answer

s-hadinger · 2025-03-31T16:18:09Z

s-hadinger
Mar 31, 2025
Collaborator

As per documentation, error -2 means:
MQTT_CONNECT_FAILED | the network connection failed

It's simply that Tasmota can't reach the port on the server, TCP failed.

See: https://tasmota.github.io/docs/MQTT/#return-codes-rc

0 replies

barbudor · 2025-03-31T21:39:12Z

barbudor
Mar 31, 2025

Default connection timeout is too short for cloud based broker. You may have been Lucky in the past
Increase with https://tasmota.github.io/docs/Commands/#mqttwifitimeout
Go to 500ms or even 1000ms

0 replies

ece1815868 · 2025-04-01T06:20:09Z

ece1815868
Apr 1, 2025
Author

I agree and thank you with your comments. i increased mqttwifitimeout to 1000 and seems not to correct the issue. I think the main issue is that after the connection error device reboots and doesnt retry after 20 or 30 sec, like it has encountered somekind of an exception and restarts. Is it possible to debug it ?

5 replies

barbudor Apr 1, 2025

Do you have any rule ?
Please show output of 'rule0' command

s-hadinger Apr 1, 2025
Collaborator

This line
INFO3 = {"Info3":{"RestartReason":{"Exception":9,"Reason":"Exception","EPC":["4026f021","00000000","00000000"],"EXCVADDR":"000008d3","DEPC":"00000000","CallChain":["4026e950","401008e8","40106111","4000050c","402272f6","4023f75d","4022a098","4022a0d6","401008e8","401010ca","402a7a74","402432ff","40245cab","402428d0","40101158","401008e8","40106111","4000050c","4025a601","4000dd11","4000066d","401008e8","4…
does indicate a crash. Any crash is most certainly a bug.

s-hadinger Apr 1, 2025
Collaborator

What firmware are you using? The crash logs are only useful with the associated map file. Did you self compile and have the map file as well?

barbudor Apr 1, 2025

I don't know for the exception but those 3 lines:

<134>tasmota-B0CCB8-3256 ESP-SRC: Restart	192.168.50.5	31/03 11:00:29.234	

<134>tasmota-B0CCB8-3256 ESP-SRC: Restart	192.168.50.5	31/03 11:00:52.735	

<134>tasmota-B0CCB8-3256 ESP-SRC: Restart	192.168.50.5	31/03 11:01:03.462

look likes somethings is willi,gly restarting Tasmota

It always happens rights after a ROTARY message:

<134>tasmota-B0CCB8-3256 ESP-ROT: Mode 1	192.168.50.5	31/03 11:01:03.462

So the failure to connect and the restart may not be related
The crash may be another problem too

What device is that ?
Any change you can get serial logs ?

sfromis Apr 1, 2025

Even without serial logs, setting Syslog 3 would likely provide messages about why those restarts are done.

ece1815868 · 2025-04-01T07:14:02Z

ece1815868
Apr 1, 2025
Author

it happens on nodemcu and sonoff devices, where they worked properly for some years. sometime long a go i upgraded the firmware because it didnt connect and then all went well for 2 years. devices work 24/7. I will try nodemcu and connect to serial interface and post the error.

0 replies

ece1815868 · 2025-04-01T12:00:56Z

ece1815868
Apr 1, 2025
Author

Serial DUMP:

00:00:13.339 MQT: TLS connection error: 0
00:00:13.341 MQT: Connect failed to a761567c16b44761b7cd6bce42d41313.s1.eu.hivem q.cloud:8883, rc -2. Retry in 10 sec
00:00:13.344 NTP: Sync time...
00:00:14.289 WIF: DNS resolved '2.nl.pool.ntp.org' (45.159.204.28) in 942 ms
00:00:15.296 NTP: No reply from 45.159.204.28
00:00:15.317 NTP: Sync time...
00:00:15.320 WIF: DNS resolved '192.168.1.1' (192.168.1.1) in 0 ms
00:00:16.327 NTP: No reply from 192.168.1.1
00:00:16.347 APP: Boot Count 160
00:00:16.348 NTP: Sync time...
00:00:17.279 WIF: DNS resolved '0.pool.ntp.org' (185.201.254.21) in 929 ms
00:00:17.448 RTC: UTC 2025-04-01T11:59:41Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00
12:59:41.000 RTC: Synced by NTP

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Exception (9):
epc1=0x4026f021 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000db9 depc=0x00000000

stack>>>

ctx: cont
sp: 3ffff9f0 end: 3fffffc0 offset: 0190
3ffffb80: 3fff5774 3fff5758 3fff4c74 4026e950
3ffffb90: 401029e9 3ffffe25 00000002 401025b8
3ffffba0: 3ffe9923 40105853 3ffed098 00000000
3ffffbb0: 00000001 40104a2e 3ffedb18 4025ea12
3ffffbc0: 40104e9f 3ffffcb3 0000000a 00000000
3ffffbd0: 00000000 00000000 0000000a 00000000
3ffffbe0: 40104967 00000039 00000002 00040000
3ffffbf0: 00002200 3ffffe85 3ffffc20 0000001c
3ffffc00: 4010382c 00080000 00000000 00000000
3ffffc10: 3ffffd70 00000000 3ffffd70 4025ea12
3ffffc20: 00000000 2c9f0300 4000050c 3fffc278
3ffffc30: 40103514 3fffc200 00000022 00000000
3ffffc40: 40261739 00000030 00000010 ffffffff
3ffffc50: 40261739 3fff8084 00000020 00000002
3ffffc60: 3fff80d2 0000b8cc 40284f67 00000000
3ffffc70: ffffffff 00000000 3ffe9aa1 00000000
3ffffc80: 40284fb6 3ffed0c0 3fff6864 00000001
3ffffc90: 402850c2 3ffed0c0 3fff6864 3ffed0c0
3ffffca0: 00000005 00000005 00000008 3fff800c
3ffffcb0: 3ffe9952 40284073 3ffed0c0 00000020
3ffffcc0: 00000000 40277423 3ffee578 3fff6864
3ffffcd0: 00000000 00000002 00000000 3ffed0c0
3ffffce0: 3fff8026 40105ebb 3fff2e20 3fff251c
3ffffcf0: 3fff2fac 00000000 00000020 4025e948
3ffffd00: 402697d2 402614b9 3fff2e20 3fff251c
3ffffd10: 40261bc6 3fff8048 00000037 00000000
3ffffd20: 00000000 00000000 00000011 00000000
3ffffd30: 3fff28ec 3fff28b8 3fff7fe4 40261746
3ffffd40: 3fff7fe4 3fff28b8 3fff7fe4 40261b60
3ffffd50: 3fff2798 402a8b33 3ffffe00 4025ebfc
3ffffd60: 00000000 00000013 00000000 3fff279
3ffffd70: 3fff28ec 00000000 3fff28b8 4026839c
3ffffd80: 4010382c 00080000 4000050c 3fffc278
3ffffd90: 00000000 3fff7fe4 4000050c 3fffc278
3ffffda0: 00103514 2c9f0300 4000050c 3fff8034
3ffffdb0: 3fff7fe4 402a0e1d 3fff28b8 402685e0
3ffffdc0: 3fff5470 3fff54fc 00000010 3fff5458
3ffffdd0: 000048e8 3fff4c74 3fff5480 401017df
3ffffde0: 3fff132a 00000020 3fff4c58 00000000
3ffffdf0: 3fff72a4 3fff7824 00000020 3fff5674
3ffffe00: 3fff5774 00000000 3fff4c74 4026d068
3ffffe10: 3fff5458 00000540 00000000 4026976c
3ffffe20: 3fff3078 3fff7fe4 3fff3074 00000000
3ffffe30: 00000010 000004e7 3fff4c74 4026d54d
3ffffe40: 3fff7064 00000071 00000071 402439f2
3ffffe50: 3fff5f29 00000000 3fff4c74 402456fa
3ffffe60: 00000540 3fff28bc 00000202 00000000
3ffffe70: 00000010 00000000 3fff4bc4 40245c9d
3ffffe80: 00000540 3fff7fe4 3fff3074 40265a57
3ffffe90: 00004731 5b1b471c 00000000 4024404e
3ffffea0: 40106255 0056bf0f 3fff2388 00000000
3ffffeb0: 00000017 00000000 3fff4bc4 4024605c
3ffffec0: 00000017 00000009 3fff4bc4 40245883
3ffffed0: 4025b330 00000009 3ffeffdc 4025a601
3ffffee0: 00000000 00000009 3ffeffdc 4024df7e
3ffffef0: 00000000 00000000 4bc6a7f0 00000000
3fffff00: 00000000 4bc6a7f0 401010ca 472b020c
3fffff10: 00000000 4bc6a7f0 00004731 00000000
3fffff20: 00000017 00000009 00000000 4022de7f
3fffff30: 00000017 00000009 00000001 4022a12b
3fffff40: 00000000 3fff02f4 00000032 3fff2030
3fffff50: 3fffdad0 00000000 00000009 4022c533
3fffff60: 3fffdad0 00000000 3ffef2f4 40240021
3fffff70: 3fffdad0 00000000 00004730 402400b0
3fffff80: 00000000 00000000 00000001 401008e8
3fffff90: 3fffdad0 00000000 3fff1ff0 3fff2030
3fffffa0: 3fffdad0 00000000 3fff1ff0 40254194
3fffffb0: feefeffe feefeffe 3ffe86ac 40101d5d
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

ets Jan 8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v3969889e
~ld

00:00:00.001 HDW: ESP8266EX
00:00:00.012 UFS: FlashFS mounted with 1992 kB free
00:00:00.062 CFG: Loaded from File, Count 190
00:00:00.068 CFG: CR 385/699, Busy 0
00:00:00.075 ROT: Mode 1
00:00:00.077 SRC: Restart
00:00:00.079 Project tasmota - Tasmota Version 14.5.0(TasmoCompiler-esp82664M)-2_7_8(2025-03-20T06:41:27)
00:00:00.182 WIF: Checking connection...
00:00:00.183 WIF: Attempting connection...
00:00:01.001 WIF: Connecting to AP1 Xiaomi_A8A6 Channel 1 BSSId 3C:CD:57:73:4A:38 in mode 11n as tasmota-B0CCB8-3256...
00:00:02.512 WIF: Checking connection...
00:00:02.513 WIF: Attempting connection...
00:00:03.516 WIF: Checking connection...
00:00:03.517 WIF: Connected
00:00:03.519 WIF: DNS resolved '192.168.50.91' (192.168.50.91) in 0 ms
00:00:03.768 HTP: Web server active on tasmota-B0CCB8-3256 with IP address 192.168.1.249
00:00:04.275 WIF: Sending Gratuitous ARP
00:00:04.276 NTP: Sync time...
00:00:04.282 WIF: DNS resolved '2.pool.ntp.org' (91.138.226.224) in 4 ms
00:00:04.357 RTC: UTC 2025-04-01T11:59:46Z, DST 2025-03-30T02:00:00, STD 2025-10-26T03:00:00
12:59:46.000 RTC: Synced by NTP
12:59:46.414 MQT: Attempting connection...
12:59:46.421 WIF: DNS resolved 'a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud' (46.137.47.218) in 5 ms
12:59:51.821 MQT: TLS connection error: 0
12:59:51.823 MQT: Connect failed to a761567c16b44761b7cd6bce42d41313.s1.eu.hivemq.cloud:8883, rc -2. Retry in 10 sec
12:59:54.843 APP: Boot Count 160
12:59:55.315 CFG: Saved to flash at 3FB, Count 191, Bytes 4096

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Exception (9):
epc1=0x4026f021 epc2=0x00000000 epc3=0x00000000 excvaddr=0x000008e3 depc=0x00000000

stack>>>

ctx: cont
sp: 3ffff9f0 end: 3fffffc0 offset: 0190
3ffffb80: 3fff5774 3fff5758 3fff4c74 4026e950
3ffffb90: 40277916 00000030 00000018 ffffffff
3ffffba0: 00000023 3fff2bdc 3ffec7c0 00000000
3ffffbb0: 00000001 00000000 00000008 00000002
3ffffbc0: 00000000 00000000 00000000 3ffed0e8
3ffffbd0: 3ffee578 00000000 3fff6864 00000030
3ffffbe0: 20746120 00000000 3ffffc85 4025e1ac
3ffffbf0: 3ffffc40 3ffffc30 0000000c 000d3639
3ffffc00: 3ffffc40 3ffffc10 00000008 00000037
3ffffc10: 00000000 00000000 3ffffc70 4025e220
3ffffc20: 3ffffc40 3ffffc30 0000000c 5f3b645a
3ffffc30: 3ffe8a7e 3ffffc70 3fff73c4 3fff0ac0
3ffffc40: 0000001b 00000033 00000000 3fff04c8
3ffffc50: 3fff04cc 3fff05cc 3ffffc85 40212402
3ffffc60: 3ffffc70 3fff73c4 40284f67 00000001
3ffffc70: 00000001 00000000 00000014 401008e8
3ffffc80: 40284fb6 3ffed0e8 00000001 40288aef
3ffffc90: 4028509a 3ffed0e8 401026f3 3ffed0e8
3ffffca0: 00000014 00000020 00000008 3fff74a4
3ffffcb0: 40284028 3ffed0e8 3ffed860 00000020
3ffffcc0: 00000000 40277423 3ffee578 3fff6864
3ffffcd0: 00000000 00000002 00000000 3ffed0e8
3ffffce0: 3fff74be 40105ebb 3fff2e04 3fff251c
3ffffcf0: 3fff2fac 40106c34 000003fb 4025e948
3ffffd00: 3ffffe00 402614b9 3fff2e04 3fff251c
3ffffd10: 00000013 00000000 3fff04ac 00000005
3ffffd20: 00000005 00000000 00000020 401008e8
3ffffd30: 3fff28ec 3fff28b8 00000005 401025b8
3ffffd40: 3ffe9955 4010586b 3ffed3b8 40261b60
3ffffd50: 00000000 00000000 0000001f 401008e8
3ffffd60: 00007fff 00d6e294 3fffc228 40106111
3ffffd70: 4000050c 00000000 00000020 401008e8
3ffffd80: 40245c9a 00000030 00000010 ffffffff
3ffffd90: 40245c8c 3fff4c74 00000005 e8ffcee0
3ffffda0: 3fff59e9 00000005 000011a1 00000003
3ffffdb0: 00000000 402a0e1d 00000002 3fff4bc4
3ffffdc0: 3fff5470 3fff54fc 00000000 3fff5458
3ffffdd0: 000049e8 3fff4c74 3fff5480 401017df
3ffffde0: 00007fff 00000020 3fff4c58 00000000
3ffffdf0: 3fff73a4 00000000 00000020 3fff5674
3ffffe00: 3fff5774 00000000 3fff4c74 4026d068
3ffffe10: 3fff5458 000004cf 00000000 4026976c
3ffffe20: 3ffea1f4 2c9f0300 4000050c 00000000
3ffffe30: 00000010 00000558 3fff4c74 4026d54d
3ffffe40: 3fff7064 000004cf 000004cf 402439f2
3ffffe50: 3fff5eb8 00000000 3fff4c74 402456fa
3ffffe60: 000004cf 00000000 00000000 00000000
3ffffe70: 00000010 00000000 3fff4bc4 40245c9d
3ffffe80: 00000540 00000017 00000002 00000030
3ffffe90: 00003705 a4229e93 00000000 4024404e
3ffffea0: 40106255 0042ff4a 3fff2388 00000000
3ffffeb0: 00000017 00000000 3fff4bc4 4024605c
3ffffec0: 00000017 00000009 3fff4bc4 40245883
3ffffed0: 4025b330 00000009 3ffeffdc 4025a601
3ffffee0: 00000000 00000009 3ffeffdc 4024df7e
3ffffef0: 00000000 00000000 4bc6a7f0 00000000
3fffff00: 00000000 4bc6a7f0 401010ca 5cac0831
3fffff10: 00000000 4bc6a7f0 00003705 00000000
3fffff20: 00000017 00000009 00000000 4022de7f
3fffff30: 00000017 00000009 00000001 4022a12b
3fffff40: 00000000 3fff02f4 00000032 3fff2030
3fffff50: 3fffdad0 00000000 00000009 4022c533
3fffff60: 3fffdad0 00000000 3ffef2f4 40240021
3fffff70: 3fffdad0 00000000 00003704 402400b0
3fffff80: 00000000 00000000 00000001 401008e8
3fffff90: 3fffdad0 00000000 3fff1ff0 3fff2030
3fffffa0: 3fffdad0 00000000 3fff1ff0 40254194
3fffffb0: feefeffe feefeffe 3ffe86ac 40101d5d
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

ets Jan 8 2013,rst cause:4, boot mode:(3,6)

wdt reset
load 0x4010f000, len 3584, room 16
tail 0
chksum 0xb0
csum 0xb0
v3969889e
~ld

00:00:00.001 HDW: ESP8266EX
00:00:00.013 UFS: FlashFS mounted with 1992 kB free
00:00:00.062 CFG: Loaded from File, Count 191
00:00:00.069 CFG: CR 385/699, Busy 0
00:00:00.076 ROT: Mode 1
00:00:00.078 SRC: Restart
00:00:00.079 Project tasmota - Tasmota Version 14.5.0(TasmoCompiler-esp82664M)-2_7_8(2025-03-20T06:41:27)
00:00:00.180 WIF: Checking connection...
00:00:00.181 WIF: Attempting connection...
00:00:01.001 WIF: Connecting to AP1 Xiaomi_A8A6 Channel 1 BSSId 3C:CD:57:73:4A:38 in mode 11n as tasmota-B0CCB8-3256...
0

How can i help?

1 reply

barbudor Apr 1, 2025

I think you have multiple problems
The MQTT not connecting doesn't seem to be the cause of the exception
I think you need to simplify your configuration (that you haven't exposed here)
Start with a fresh configuration without MQTT. Does the problem occurs ?
Then add mqtt
Same question

Go step by step

ece1815868 · 2025-04-01T17:59:07Z

ece1815868
Apr 1, 2025
Author

it happens on clean configuration. the problem i think is on broker

2 replies

barbudor Apr 1, 2025

And it doesn't happen until you configure MQTT ?
Are you using a free or paying hivemq account ?

ece1815868 Apr 1, 2025
Author

its a free hivemq ssl tls. it worked for years. it connects at random point after some reboots and stays connected

i compiled a vs.code binary and this is the stack trace

0x4027bffb: verify_SKE_sig at /home/earle/Arduino/hardware/esp8266com/esp8266/tools/sdk/ssl/bearssl/src/ssl/ssl_hs_client.c:202
0x4027bffb: br_ssl_hs_client_run at /home/earle/Arduino/hardware/esp8266com/esp8266/tools/sdk/ssl/bearssl/src/ssl/ssl_hs_client.c:1816
0x4027bba1: br_ssl_hs_client_run at /home/earle/Arduino/hardware/esp8266com/esp8266/tools/sdk/ssl/bearssl/src/ssl/ssl_hs_client.c:1528
0x4026bd0c: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:180
0x4026bdd6: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:233
0x4026bdd6: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:233
0x4026bdd6: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:233
0x4026bd0c: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:180
0x4026c838: _printf_i at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf_i.c:246
0x4026bdd6: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:233
0x4026bfc0: _svfprintf_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:531
0x4026b52d: _vsnprintf_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/vsnprintf.c:73
0x402763e2: ip4_output_if at /local/users/gauchard/arduino/arduino_esp8266/esp8266-lwip/tools/sdk/lwip2/builder/lwip2-src/src/core/ipv4/ip4.c:1550
0x4026b52d: _vsnprintf_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/vsnprintf.c:73
0x4026b570: vsnprintf at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/vsnprintf.c:42
0x4026b570: vsnprintf at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/vsnprintf.c:42
0x4027a320: jump_handshake at /home/earle/Arduino/hardware/esp8266com/esp8266/tools/sdk/ssl/bearssl/src/ssl/ssl_engine.c:1081
0x4027a805: br_ssl_engine_recvrec_ack at /home/earle/Arduino/hardware/esp8266com/esp8266/tools/sdk/ssl/bearssl/src/ssl/ssl_engine.c:1206
0x4026bdd6: __ssputs_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:233
0x4026bfc0: _svfprintf_r at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/nano-vfprintf.c:531
0x40275660: etharp_output_to_arp_index at /local/users/gauchard/arduino/arduino_esp8266/esp8266-lwip/tools/sdk/lwip2/builder/lwip2-src/src/core/ipv4/etharp.c:770
0x4026b570: vsnprintf at /home/earle/src/esp-quick-toolchain/repo/newlib/newlib/libc/stdio/vsnprintf.c:42
0x402758a4: etharp_output_LWIP2 at /local/users/gauchard/arduino/arduino_esp8266/esp8266-lwip/tools/sdk/lwip2/builder/lwip2-src/src/core/ipv4/etharp.c:885
0x40276378: ip4_output_if_opt_src at /local/users/gauchard/arduino/arduino_esp8266/esp8266-lwip/tools/sdk/lwip2/builder/lwip2-src/src/core/ipv4/ip4.c:1764
0x4026ef03: ip_chksum_pseudo at /local/users/gauchard/arduino/arduino_esp8266/esp8266-lwip/tools/sdk/lwip2/builder/lwip2-src/src/core/inet_chksum.c:395

ece1815868 · 2025-04-02T09:00:00Z

ece1815868
Apr 2, 2025
Author

I wiresharked tls handshake and saw that hivemq serves two certificates rsa 2048bit. Is it possible that esp8266 runs out of memory because of this? also in compilation i see that iram is almost full "Used static IRAM: 31388 bytes ( 1380 remain, 95.8 % used)". Should i upgrade to esp32 because running out of resources?

1 reply

sfromis Apr 2, 2025

Static IRAM is not "the problem", as this is not handled dynamically at runtime. Instead, certain sections of code are statically placed in IRAM (instruction RAM) due to requirements (like in interrupt handlers) that code must be served from SRAM (which IRAM is also), instead of uncached from flash.

Noschvie · 2025-04-02T09:09:26Z

Noschvie
Apr 2, 2025

MQTT TLS with HiveMQ is not working since days - nothing changed #23234

2 replies

ScanLabs Apr 2, 2025

to add a comment - and sorry for having opened a new thread ....
I'm using ESP32 Tasmota-LVGL and the same HiveMQ broker .
Worked fine on 14.5.0.2 since a while. I notice the problem on Monday 31st march .
For the sake of test I uploaded from web a fresh new 15.4.0.3 LVGL - the only config I did is about MQTT via HiveMQ broker.

I have exactly the same behavior - TLS 0 / connection failed rc=-2 / PANIC ....

I link here my logs
hive-mq-issue.txt

Paolo

s-hadinger Apr 2, 2025
Collaborator

Just looking at your logs:

5165 ms of TLS connection time is extremely high. What is your Tasmota frequency ? Are you running at 240 MHz?

Success:

07:51:02.182 MQT: Attempting connection...
07:51:02.189 WIF: DNS resolved '2e7e307496564a028583e389********.s1.eu.hivemq.cloud' (52.31.149.80) in 6 ms
07:51:07.355 MQT: TLS connected in 5165 ms, stack low mark 18544
07:51:07.356 MQT: MFLN not supported by TLS server
07:51:07.356 MQT: Connected

Now on failure, it takes the same amount of time so this seems to indicate that the handshake did happen, but connection is marked as failed - not sure why.

Also the following log shows that the crash is not immediately after the TLS handshake, so probably a memory corruption happened during handshake.

07:47:43.181 MQT: Attempting connection...
07:47:43.187 WIF: DNS resolved '2e7e307496564a028583e389********.s1.eu.hivemq.cloud' (52.31.149.80) in 5 ms
07:47:48.350 MQT: TLS connection error: 0
07:47:48.351 MQT: Connect failed to 2e7e307496564a028583e389********.s1.eu.hivemq.cloud:8883, rc -2. Retry in 10 sec
07:47:50.375 QPC: Reset
07:47:52.369 APP: Boot Count 5
07:47:52.752 CFG: Saved, Count 14, Bytes 4096
Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.

ece1815868 · 2025-04-02T09:44:59Z

ece1815868
Apr 2, 2025
Author

sometimes it connects but after many retries:
TLS connected in 3783 ms, max ThunkStack used 4500
09:10:29.235 MQT: MFLN not supported by TLS server
09:10:29.235 MQT: Server fingerprint: [deleted ]
09:10:29.242 MQT: Connected
I dont know because it takes somes seconds now to connect from my client in my phone, so i switched there to websocket-ssl

Also i noted in wireshark after sending client hello packet, server hello message takes some time to receive (sometimes takes 7-8 sec). I believe the problem lies in hivemq server taking too long to respond.

In file \lib\lib_ssl\tls_mini\src\WiFiClientSecureLightBearSSL.h there is a property at line 140 uint32_t _loopTimeout=5000; I digged and i think that tls connection routine has a hardlimited timeout of 5sec to reach SENDAPP state. I think its tls handshake timeout.
I increased to 15000 and seems to connect now. Is it correct approach? Also kernel shouldn't panic cause of timeout.

1 reply

ScanLabs Apr 2, 2025

Hi man,

I have exactly your problem - same Panic as reported above.
I tested your WA and it worked also here on ESP32 Tasmota 14.5.0.2 LVGL

I noticed very long TLS connection time.
Some logs:
11:45:51.663 MQT: TLS connected in 9477 ms, stack low mark 18544
11:48:58.152 MQT: TLS connected in 7782 ms, stack low mark 18544
11:49:45.688 MQT: TLS connected in 9461 ms, stack low mark 18544
11:50:06.340 MQT: TLS connected in 6964 ms, stack low mark 18544
11:50:38.375 MQT: TLS connected in 9169 ms, stack low mark 18544

Increasing
uint32_t _loopTimeout=5000
to
uint32_t _loopTimeout=15000
solved.

What is still there is the bug causing panic when loopTimeou expires.

Paolo

s-hadinger · 2025-04-02T14:50:33Z

s-hadinger
Apr 2, 2025
Collaborator

Is the problem easy to reproduce with HiveMQ ? If so I will open an account

0 replies

ScanLabs · 2025-04-02T15:08:58Z

ScanLabs
Apr 2, 2025

Yes - very easy.
setup a free account in HiveMq - configure tasmota.
Crash will happen at the first boot.
If needed I can setup a subscriber temporary account under my hiveMq domain .

As you wish
Paolo

1 reply

s-hadinger Apr 3, 2025
Collaborator

Thanks, I will try in the following days

s-hadinger · 2025-04-04T17:41:48Z

s-hadinger
Apr 4, 2025
Collaborator

Unfortunately I cannot reproduce. I took a stock ESP32 firmware and got the following:

18:37:54.870-146/27 MQT: Attempting connection...
18:37:56.043-144/26 MQT: TLS connected in 1164 ms, stack low mark 2160
18:37:56.044-144/26 MQT: MFLN not supported by TLS server
18:37:56.044-144/26 MQT: Connected
18:37:56.060-141/24 MQT: tele/tasmota_1C8664/LWT = Online (retained)
18:37:56.063-141/24 MQT: cmnd/tasmota_1C8664/POWER =
18:37:56.064-141/24 MQT: Subscribe to cmnd/tasmota_1C8664/#
18:37:56.077-141/24 MQT: Subscribe to cmnd/tasmotas/#
18:37:56.079-141/24 MQT: Subscribe to cmnd/DVES_1C8664_fb/#
...

My connection time is much shorter than what was seen above. I suspect that the error and the crash come from a timeout that is not well handled.

1 reply

s-hadinger Apr 4, 2025
Collaborator

I can reproduce the crash by artificially lowering the _loopTimeout value and forcing a time-out. Working on it.

ece1815868 · 2025-04-04T20:23:26Z

ece1815868
Apr 4, 2025
Author

Update: The crash happens when the _loopTimeout time expires before ServerHello Message from server in TLS exchange. Here is the backtrace:

xtensa-esp32s3-elf-addr2line -pfiaC -e firmware.elf -a 0x4019a90b:0x3ffb2050 0x401961b1:0x3ffb20d0 0x4019c12d:0x3ffb2100 0x40175aca:0x3ffb2130 0x40175c45:0x3ffb2160 0x40175965:0x3ffb2180 0x4018bb3a:0x3ffb21a0 0x4018d3bf:0x3ffb21c0 0x400f478b:0x3ffb21f0 0x4014a64e:0x3ffb2210 0x400dfa8c:0x3ffb2230 0x400dbd5e:0x3ffb2250 0x400dbdcf:0x3ffb2270 0x401959a6:0x3ffb2290

0x4019a90b: br_ssl_hs_client_run at :?
0x401961b1: jump_handshake at C:\temp\Tasmota-14.5.0/lib/lib_ssl/bearssl-esp8266/src/ssl/ssl_engine.c:1080
0x4019c12d: br_ssl_engine_recvrec_ack at C:\temp\Tasmota-14.5.0/lib/lib_ssl/bearssl-esp8266/src/ssl/ssl_engine.c:1205
0x40175aca: BearSSL::WiFiClientSecure_light::_run_until(unsigned int, bool) at C:\temp\Tasmota-14.5.0/lib/lib_ssl/tls_mini/src/WiFiClientSecureLightBearSSL.cpp:655
0x40175c45: BearSSL::WiFiClientSecure_light::available() at C:\temp\Tasmota-14.5.0/lib/lib_ssl/tls_mini/src/WiFiClientSecureLightBearSSL.cpp:508 (discriminator 2)
0x40175965: BearSSL::WiFiClientSecure_light::connected() at C:\temp\Tasmota-14.5.0/lib/lib_ssl/tls_mini/src/WiFiClientSecureLightBearSSL.cpp:377
0x4018bb3a: PubSubClient::connected() at C:\temp\Tasmota-14.5.0/lib/default/pubsubclient-2.8.13/src/PubSubClient.cpp:819
0x4018d3bf: PubSubClient::loop() at C:\temp\Tasmota-14.5.0/lib/default/pubsubclient-2.8.13/src/PubSubClient.cpp:406
0x400f478b: Xdrv02(unsigned long) at C:/temp/Tasmota-14.5.0/tasmota/tasmota_xdrv_driver/xdrv_02_9_mqtt.ino:2107
0x4014a64e: XdrvCall(unsigned long) at C:/temp/Tasmota-14.5.0/tasmota/tasmota_xx2c_global/xdrv_interface.ino:1166
0x400dfa8c: XdrvXsnsCall(unsigned long) at C:/temp/Tasmota-14.5.0/tasmota/tasmota_support/support_tasmota.ino:226
0x400dbd5e: Scheduler() at C:/temp/Tasmota-14.5.0/tasmota/tasmota.ino:790
0x400dbdcf: loop() at C:/temp/Tasmota-14.5.0/tasmota/tasmota.ino:834
0x401959a6: loopTask(void*) at C:/Users/John-NUC/.platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:80

0 replies

s-hadinger · 2025-04-04T21:49:22Z

s-hadinger
Apr 4, 2025
Collaborator

It should be fixed now with #23249

0 replies

MQTT TLS reboot error #23217

Replies: 14 comments · 14 replies

s-hadinger Mar 31, 2025 Collaborator

ece1815868 Apr 1, 2025 Author

s-hadinger Apr 1, 2025 Collaborator

s-hadinger Apr 1, 2025 Collaborator

ece1815868 Apr 1, 2025 Author

ece1815868 Apr 1, 2025 Author

ece1815868 Apr 1, 2025 Author

ece1815868 Apr 1, 2025 Author

ece1815868 Apr 2, 2025 Author

s-hadinger Apr 2, 2025 Collaborator

ece1815868 Apr 2, 2025 Author

s-hadinger Apr 2, 2025 Collaborator

s-hadinger Apr 3, 2025 Collaborator

s-hadinger Apr 4, 2025 Collaborator

s-hadinger Apr 4, 2025 Collaborator

ece1815868 Apr 4, 2025 Author

s-hadinger Apr 4, 2025 Collaborator

Replies: 14 comments 14 replies

s-hadinger
Mar 31, 2025
Collaborator

ece1815868
Apr 1, 2025
Author

s-hadinger Apr 1, 2025
Collaborator

s-hadinger Apr 1, 2025
Collaborator

ece1815868
Apr 1, 2025
Author

ece1815868
Apr 1, 2025
Author

ece1815868
Apr 1, 2025
Author

ece1815868 Apr 1, 2025
Author

ece1815868
Apr 2, 2025
Author

s-hadinger Apr 2, 2025
Collaborator

ece1815868
Apr 2, 2025
Author

s-hadinger
Apr 2, 2025
Collaborator

s-hadinger Apr 3, 2025
Collaborator

s-hadinger
Apr 4, 2025
Collaborator

s-hadinger Apr 4, 2025
Collaborator

ece1815868
Apr 4, 2025
Author

s-hadinger
Apr 4, 2025
Collaborator