MG8725 2.4Ghz WiFi dropouts, and other things

Really thankful that my last post magically didn't post to the forum so I'll try again. 

I am having a problem with my MG8725 modem/router. This is an approved modem from Xfinity and I bought this in May after dealing with months of issues, tech visits, and no solutions on a DHCPv6 issue within my XB7 modem. The last tech I had out just straight up told me to get my own as the Xfinity-provided modems can not only be refurbished, but also just do not allow anyone to change core administrative properties of the modem. For example, if I could've just adjusted the DHCPv6 lease time, I wouldn't have to deal with internet dropouts every hour when the DHCPv6 lease renewed. Within those months of tech appointments and trouble shooting, I had the entire pipeline replaced from the line coming to the house from the street, the lines within the box on the side of my house, the line running from the box on the side of my house into a hole in the side of my first floor, and the modem is and was connected to a port on the adjacent side of the wall from where the Xfinity line enters the house (so no splitters, unnecessary runs...). After changing the XB7 for the MG8725, I have been able to properly set my admin panel to only allow IPv4 (which seems to have eliminated any DHCPv6 errors that plagued me in the past), and port forward on command (another flaw of the crappy Xfinity app). 

I have been having 2 problems with my MG8725, but one I am unsure of the severity or consequence.

The first problem is the connectivity of just the 2.4Ghz band of the wifi. It seems to just drop all devices after hours or a day, while remaining up and active on scanners, the Motorola app, etc. This has been a real pain, as the only remedy for this seems to be a reboot of the modem, which means I am rebooting my modem every day, sometimes twice a day. Normally, I wouldn't care too much if only one band was acting up, however my Ring doorbell can only connect via 2.4Ghz, so this means my doorbell is not recording or accessible during this downtime. This is a real issue because I am missing key events that are happening at my house (package drop off, snooping kids, etc.). I have posted my connection stats and logs below for any reference, as someone here may be able to spot something before I go through the rigmarole of getting a tech out here for the millionth time this year. The 5Ghz band, as well as ethernet, seem to be unaffected, and with only a few 2.4-dependent devices on that band, it hard to know a) when the 2.4ghz band drops and b) if there is a correlation with some kind of other event I am noticing or in the system logs.
The second issue is a blinking blue downstream light on the modem. Per Motorola, this indicates that the downstream is negotiating multiple channels. This light will start blinking randomly sometime after a reboot and never stop. It is unclear if it is linked to the wifi issue, however I have seen it be blinking and both wifi networks are online and fine. If anyone has any info on this or if it is just a normal thing to do, let me know.

My connection stats are below:

Startup Sequence

Startup Step Status Comment       Acquire Downstream Channel 579000000 Hz Locked       Upstream Connection OK Operational       Boot State OK Operational       Configuration File OK       Security Enabled BPI+

Connection Status

System Up Time 1 days 0h: 37m: 12s         Network Access Allowed

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected    1 Locked 256 QAM 17 579.0 -4.0 41.4 0 0    2 Locked 256 QAM 2 483.0 -2.8 42.2 0 0    3 Locked 256 QAM 3 489.0 -3.3 42.0 0 0    4 Locked 256 QAM 4 495.0 -3.0 42.0 0 0    5 Locked 256 QAM 5 507.0 -3.8 41.8 0 0    6 Locked 256 QAM 6 513.0 -3.9 41.7 0 0    7 Locked 256 QAM 7 519.0 -4.7 41.3 0 0    8 Locked 256 QAM 8 525.0 -5.3 40.9 0 0    9 Locked 256 QAM 9 531.0 -5.3 40.8 0 0    10 Locked 256 QAM 10 537.0 -5.2 40.8 0 0    11 Locked 256 QAM 11 543.0 -5.8 40.5 0 0    12 Locked 256 QAM 12 549.0 -5.3 40.7 0 0    13 Locked 256 QAM 13 555.0 -4.7 41.0 0 0    14 Locked 256 QAM 14 561.0 -4.5 41.2 0 0    15 Locked 256 QAM 15 567.0 -3.6 41.6 0 0    16 Locked 256 QAM 16 573.0 -3.7 41.6 0 0    17 Locked 256 QAM 18 585.0 -4.1 41.5 0 0    18 Locked 256 QAM 19 591.0 -5.3 40.8 0 0    19 Locked 256 QAM 20 597.0 -6.5 39.8 0 0    20 Locked 256 QAM 21 603.0 -6.8 39.8 0 0    21 Locked 256 QAM 22 609.0 -6.5 40.0 0 0    22 Locked 256 QAM 23 615.0 -7.1 39.4 0 0    23 Locked 256 QAM 24 621.0 -6.5 39.9 21 0    24 Locked 256 QAM 25 627.0 -6.3 40.0 20628292 12042302    25 Locked 256 QAM 26 633.0 -5.8 40.3 3063189 130427    26 Locked 256 QAM 27 639.0 -5.4 40.6 2002463 388137    27 Locked 256 QAM 28 645.0 -3.7 41.9 0 0    28 Locked 256 QAM 29 651.0 -3.4 41.9 0 0    29 Locked 256 QAM 30 657.0 -3.7 41.9 0 0    30 Locked 256 QAM 31 663.0 -3.1 42.0 0 0    31 Locked 256 QAM 32 669.0 -4.0 41.6 0 0    32 Locked OFDM 33 690.0 -6.4 0.0 875115097 5199301

Upstream Bonded Channels

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)    1 Locked SC-QAM 1 5120 35.6 55.3    2 Locked SC-QAM 2 5120 29.2 55.3    3 Locked SC-QAM 3 5120 22.8 56.0    4 Locked SC-QAM 4 5120 16.4 57.0    5 Locked SC-QAM 5 1280 39.6 52.8

Downstream Frequency Setting

Downstream Frequency Select

Network WAN Connection

IPv4 Address xxxxxxxxxxxx         Lease Time Remaining D: 00 H: 22 M: 08 S: 33         Lease Expiration Time Sat Jul 15 07:01:19 2023       MAC Address xxxxxxxxxxx       WAN Connection Type DHCP

The logs most recently:

  Event Log    
  

    Time    Priority    Description 
    11:25:30
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:25:56
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:28:56
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:29:18
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:29:18
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:29:21
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:29:28
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:29:55
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:48:52
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    11:49:03
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:14:57
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:15:07
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:23:42
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:24:08
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:51:35
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:51:56
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:52:11
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:52:29
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:54:00
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:54:19
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:57:10
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    12:57:26
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    13:47:56
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    13:48:10
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    14:03:15
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    14:03:30
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    14:04:48
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    14:05:16
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    17:46:50
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    17:46:53
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    18:31:37
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    18:31:53
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    20:14:44
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    20:15:08
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    22:02:22
Thu Jul 13 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    22:02:49
Thu Jul 13 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    05:52:53
Fri Jul 14 2023   Warning(5)   MDD message timeout;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    05:53:14
Fri Jul 14 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;
    07:16:58
Fri Jul 14 2023   Notice(6)   CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxx;CMTS-MAC=xxxxxxx;CM-QOS=1.1;CM-VER=3.1;