Boot loop after power outage

Had a power outage earlier today. 3 ESPhome setups on battery backups so they did not reboot and should not have noticed the power outage.

But went to set the alarm this evening, and all 3 ESPs are in 15 second boot loops.
I tried a hard boot, no change.
I pulled 2 of the boards and ran a firmware update from 3.14 to 3.15 and no change. one did manage to stay online for about 5 minutes and then started the boot loop again. 2nd board started boot loop right after flash.

I have been able to resync the cloud settings after reconnecting to wifi, so config looks good after the reflash, but just in constant boot loops now.

Logs look good until the gibberish starts at 15 secs.
I do see the notes about mqtt being offline. Is that why the reboots?
My internet connection looks solid and the status page for Konnected says no issues.

Not sure what the issue is here

[01:49:52]Konnected firmware 3.0.0
[01:49:52]NodeMCU 3.0.0.0 build 2023-03-22 14:22 powered by Lua 5.1.4 on SDK 3.0.1-dev(fce080e)
[01:49:52]Heap: 41096 Initializing Konnected (2c3ae835d3c9)
[01:49:52]Heap: 39920 Application Version: 3.1.5
[01:49:52]Heap: 39640 Connecting to Wifi..
[01:49:55]> Heap: 39440 Wifi connected with IP: 192.168.2.21 Gateway: 192.168.2.1
[01:49:58]Heap: 39936 Current Date/Time: 2025-06-18 05:49:57 UTC
[01:49:58]Heap: 39832 Booting Konnected application
[01:49:58]Heap: 39304 UPnP: Listening for UPnP discovery
[01:49:58]Heap: 38720 HTTP: Starting server at http://192.168.2.21:11527
[01:49:58]Heap: 38496 Loaded: server
[01:49:58]Heap: 33880 Initializing sensor zone: 1
[01:49:58]Heap: 33840 Initializing sensor zone: 2
[01:49:58]Heap: 33840 Initializing sensor zone: 3
[01:49:58]Heap: 33840 Initializing sensor zone: 4
[01:49:58]Heap: 33840 Initializing sensor zone: 5
[01:49:58]Heap: 33840 Initializing sensor zone: 6
[01:49:58]Heap: 29400 Connecting to AWS IoT Endpoint: wss://a1tb9iwdx5to6h-ats.iot.us-east-1.amazonaws.com/mqtt
[01:49:58]Heap: 29280 Loaded: application
[01:50:00]Heap: 10520 websocket connected
[01:50:00]Heap: 29600 websocket closed, status: -99
[01:50:00]Heap: 29568 mqtt: offline failures: 1
[01:50:00]E:M 544
[01:50:00]E:M 1592
[01:50:00]E:M 1592
[01:50:00]Heap: 29544 websocket closed, status: -54
[01:50:00]Heap: 29504 mqtt: offline failures: 2
[01:50:00]E:M 544
[01:50:00]E:M 1592
[01:50:00]E:M 1592
[01:50:00]Heap: 29728 websocket closed, status: -54
[01:50:00]Heap: 29688 mqtt: offline failures: 3
[01:50:01]E:M 544
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29584 websocket closed, status: -54
[01:50:01]Heap: 29544 mqtt: offline failures: 4
[01:50:01]E:M 544
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29480 websocket closed, status: -54
[01:50:01]Heap: 29440 mqtt: offline failures: 5
[01:50:01]E:M 544
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29728 websocket closed, status: -54
[01:50:01]Heap: 29688 mqtt: offline failures: 6
[01:50:01]E:M 544
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29472 websocket closed, status: -54
[01:50:01]Heap: 29432 mqtt: offline failures: 7
[01:50:01]E:M 544
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29440 websocket closed, status: -54
[01:50:01]Heap: 29440 mqtt: offline failures: 8
[01:50:01]E:M 280
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29432 websocket closed, status: -54
[01:50:01]Heap: 29432 mqtt: offline failures: 9
[01:50:01]E:M 280
[01:50:01]E:M 1592
[01:50:01]E:M 1592
[01:50:01]Heap: 29328 websocket closed, status: -54
[01:50:01]Heap: 29328 mqtt: offline failures: 10
[01:50:04]
[01:50:05] ets Jan 8 2013,rst cause:2, boot mode:(3,2)
[01:50:05]
[01:50:05]load 0x40100000, len 28252, room 16
[01:50:05]tail 12
[01:50:05]chksum 0xe8
[01:50:05]ho 0 tail 12 room 4
[01:50:05]load 0x3ffe8000, len 2696, room 12
[01:50:05]tail 12
[01:50:05]chksum 0x8e
[01:50:05]ho 0 tail 12 room 4
[01:50:05]load 0x3ffe8a88, len 8, room 12
[01:50:05]tail 8
[01:50:05]chksum 0x2c
[01:50:05]csum 0x2c
[01:50:05]�es���o�e�$�؄�o~ec �c��g��g�’ec �8� ���$ �’o��g’�웂�?� �ng�쓃� �eb�go��ۃ����e�n�{��o|�l�l#�e�|{�$�n��o�l��s�l�le�  l��{�d�l� d��r�l ��� dl sd��sl���c�c�#8{ ��c�p l�d��o�eg’�dcl���llld���� $�l�n�����c l$ �{�c����c d�b{ls
[01:50:05]Konnected firmware 3.0.0

Wondering of there is a cloud issue as I just pulled a new 6 zone panel board out of the bag and setup. Wireless was stable until I configured a zone in the cloud and it started doing the boot loop issue

Same issue with 2 Arduino boards running 3.1.4. Has anyone contacted support?

I’m checking into this. I deployed a fairly large infrastructure update last night. The log posted here in the OP looks like it’s indicating a cloud/MQTT authorization issue. Will report back here.

This should be resolved now. No action required on your side – the devices should automatically retry and re-connect.

Can anyone confirm that they’re back online?

Up for 36 minutes! Thanks Nate!