CAX80 Randomly Loosing Downstream Lock - MDD message timeout?

Hey guys, I appreciate the feedback! So to pick up where I left off earlier, not soon after my last post I had an RCN tech come out and he basically confirmed everything looked great signal-wise. The one small modification he made was to recrimp some outside connectors between the splitter box for my residence and the neighbors in the front yard (it's like a green cylinder that sticks up from the ground between the houses), and also recrimped the connector where that same feed comes into the house. He claimed the tech that put it in did not make the copper signal wire lead long enough and explansion/contraction due to temperature could be triggering the disconnects. My thoughts, yeah sure maybe. Can't hurt i guess! He also removed a moca filter from the outside box on the house which I guess isn't needed anymore.

So after the tech left the issue occued again within a day. At this point I thought bad device, so I returned that CAX80 and got a new one. New one seemed to work slightly better, but still ran into the same exact problem. By this point I was personally contacted by Netgear about the issue (from this forum post actually) and they walked me through collecting full diagnostic logs from my CAX80. Netgear responded that they saw a lot of errors in the logs, but never really clairified to me what exactly the problem was despite my asking. At this time the downstream "unlock" / MDD messgae timeout was occuring daily or every other day. So s few days later I get a response from NG asking me to test out a new beta firmware (v2.1.0.5). The recommendation was to install this firmware, do a complete factory reset of the device and then set it up again using the app. Okay, fine. About 2 hours after installing the firmware and having everything setup, issue happens again. However! That was 10/22, since that first incident I have not experienced the issue again.

Now, as someone who works professinally in system testing/validation, I'm well aware of flukes and strange behavior of computer electronics. I'm really not yet conviced this beta firmware has actually fixed the issue. I'm still giving it until this weekend before making any more final opinions. The only other thing i'll say here is I do see MDD message timeouts in the web UI event viewer, but so far these have not caused a noticable impact on connection. Maybe there is some better recovery code now in the beta firmware for when these events occur? Not sure. I would expect for a regular household residence the signal isn't always going to be perfect and some minor dips and peaks in signal would occur every now and again, but nothing the CAX80 shouldn't be properly able to handle and recover from.

Last point i want to bring up is that the beta firmware i received was only for the router, not the modem. Now, I'm not an expert on how cablem modem/router gateways work, but I don't understand how when i'm having issues with the cablem modem portion of the device, why an update to the router firmware would correct this problem. Clearly the issue lies in the downstream communication at the modem iit would seem, not the router portion of the device. But who knows, maybe there's more interconnection to it than I'm aware of...

Anyways, I'll follow up again soon with any updates.