Firmware, Lost WiFi or MQTT Connection, Rev 0.47

[ForrestErickson]

Describe the bug
A clear and concise description of what the bug is.

Short Summary of the expected behavior:

I was using the PMD_Processing_MQTT sketch to publish to many Krakes.
I expected all powered Krake operating as STA to announce.

Short Summary of the buggy behavior:

I was using the PMD_Processing_MQTT sketch to publish to many Krakes
Although I had three Krakes powered up, there were only two Krakes publishing on line

20260221_054226 Msg_recd: KRAKE_LB0004 -  online, RSSI:-62.00
20260221_054227 Msg_recd: KRAKE_US0002 -  online, RSSI:-52.00

Krake US0007 running Rev 0.47 but not publishing on line.
Krake US0007 running Rev 0.47 was powered and responding to Serial Monitor commands. See below.

I published the message that I was on line: "a2 Lee is back in Discord"
KRAKE_LB0004 and KRAKE_US0002 announced the message, but KRAKE_US0007 did not.

This Krake has responded in the past.

I pinged it's IP address.
*wm:STA IP Address: 192.168.1.245 and found it unreachable

C:\Users\Admin>ping 192.168.1.245

Pinging 192.168.1.245 with 32 bytes of data:
Reply from 192.168.1.103: Destination host unreachable.
Reply from 192.168.1.103: Destination host unreachable.
Reply from 192.168.1.103: Destination host unreachable.
Reply from 192.168.1.103: Destination host unreachable.

Ping statistics for 192.168.1.245:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\Admin>

To Reproduce
Steps to reproduce the behavior:

1. Load into a Krake the GPAD_API firmware 0.47
2. Set SSID and PW for STA operation.
3. Verify it is subscribing to ALM events. Also PING on the LAN.
4. Let it run for some time and retest ALM events.
5. Retest with ALM events. Retest with PIN on LAN.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Hardware description
Model: Krake Rev 2 hardware
Serial Number: US0007
Other: KRAKE_LB0004 and KRAKE_US0002 are REV 1 hardare and running older GPAD API
20260221_055704 Msg_recd: KRAKE_US0002 - Firmware Version: 0.44
20260221_055704 Msg_recd: KRAKE_LB0004 - Firmware Version: 0.46_Regression

Test Equipment
Model: Lee's office computer to run the PMD_Processing_MQTT sketch

Additional context
Add any other context about the problem here.

Here is the result on the Serial Monitor of the "i" command

I received: 1i
Command: i
Firmware Version: 0.47
GPAD API Version: 0.1.0
System up time (mills): 282061729
Mute Status: NOT MUTED
Current alarm Level: 5
Current alarm message: a5
IP Address: (0,0,0,0)
currentlyMuted : 0
interpret Done
a5
dfPlayer.play
5
PlayNotBusyLevel
HIGH .next called! =================
Number:6 Play Finished!
Muted: NO
LVL: 5
Msg: a5

CC: @nk25719

[ForrestErickson]

Notes on Loss of WiFi, US0006, 20260224 0554

DUT: US0006.
Firmware Version 0.47 with bugfix/226-wifi-status-visibility
Morning of 20260224 0554 EST the DUT was found not to respond to the PMD_Processing_MQTT commands.
The DUT was not publishing on line messages (MAC_ACK) to the broker.

This device was reset the day before during the Discord work mid day and so has lost MQTT connection in less than 24 hrs.

LAN Connection, YES

Ping IP Address: 192.168.1.243

C:\Users\Admin>ping 192.168.1.243

Pinging 192.168.1.243 with 32 bytes of data:
Reply from 192.168.1.243: bytes=32 time=84ms TTL=64
Reply from 192.168.1.243: bytes=32 time=212ms TTL=64
Reply from 192.168.1.243: bytes=32 time=197ms TTL=64
Reply from 192.168.1.243: bytes=32 time=213ms TTL=64

Ping statistics for 192.168.1.243:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 84ms, Maximum = 213ms, Average = 176ms

Serial Monitor "i"

I received: 1i
Command: i    
Firmware Version: 0.47
GPAD API Version: 0.1.0
System up time (mills): 57597420
Mute Status: NOT MUTED
Current alarm Level: 2
Current alarm message: a2
IP Address: (0,0,0,0)
currentlyMuted : 0
interpret Done
a2
dfPlayer.play
2
PlayNotBusyLevel
HIGH .next called! =================
Number:3 Play Finished!
Muted: NO
LVL: 2
Msg: a2

Time since Reset.

if at 20240224 554 AM I had a count of 57597420 mills when was zero mills?
This is 15.99 hours so reset was about 2:00 PM on 23 Feb.

Interrupt WiFi Router Experiment

0613 AM In an attempt to get the Krake WiFi and therefore possibly the MQTT client to reconnect Lee removed power from the VRX WiFi Access Point.
Confirmed that LAN/WiFi connecting was lost by pinging and getting no response

C:\Users\Admin>ping 192.168.1.243

Pinging 192.168.1.243 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.1.103: Destination host unreachable.
Reply from 192.168.1.103: Destination host unreachable.

Ping statistics for 192.168.1.243:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Power on VRX AP at 0616 AM
The LCD displayed a splash like message and then returned to showing the LVL 2 message "a2" it last displayed.

The PMD_PROCESSING_MQTT console shows US0006 is publishing on line!

I published a message and US0006 got it ! Cycling the WiFi recovered the MQTT connection.
Note none of the other Krakes came back to the broker. and probably not WiFi.

Other Versions when WiFi powere cycled

Krake US0002 running Rev 0.44 did not reacquire the WiFi thought it had not lost WiFi connection.