@HelpFixDecoApp , thank you.  Email and info sent.

  @HelpFixDecoApp , appreciate the clarification. Thanks again 

I am reporting ongoing stability issues with my Deco BE63 system. This system replaced older 2.4 hardware a few months ago, and I have had these issues since the swap. I specifically moved to the 1.3.0 Build 26021212 Beta as a last resort after exhausting all standard configuration changes, but the stability problems persist.

​Troubleshooting Already Performed:

I have already manually implemented the following configurations to rule out common conflicts:

​* Wireless Settings: Disabled Fast Roaming, Beamforming, and SIP ALG.

​* 2.4GHz Optimization: Forced the 2.4GHz band to 20MHz and set security strictly to WPA2.

​* Per-Device Config: Disabled Mesh Technology for stationary devices and assigned Static/Reserved IP addresses for all problematic hardware.

* ​Network Segmentation: Utilized the IoT network, though it has shown little to no improvement in stability.

​Primary Issues Observed:

​Legacy Device "Driver Crashes". Many older 2.4GHz devices (Chromecast dongles, Google Mini speakers, printers, and certain Windows machines) frequently drop off. What is odd is that the Wi-Fi on the client side appears to shut off entirely, as if the driver is crashing. This requires a device reboot to recover.

​Garmin DriveSmart 61 Timeout. These units fail to connect half the time. Even when they do successfully connect, map updates consistently time out and fail during the download. I have verified these units work perfectly on a local mobile hotspot, and they worked fine on my previous router hardware before the BE63.

Something to note is hardwired the work computer, printer, etc seems to work fine. Also sometime with chromecast when turning off the wifi and back on even if it is already connected seems to make it work again if there was issues. 

​

A major one is, work-issued computers are failing to stay connected to the Wi-Fi, which is a critical issue for my daily usage. Same with printers. 

​Due to the overall network instability, Home Assistant frequently loses track of smart devices, suggesting issues with how the mesh handles local device  visibility. Like it often loses the ability to see given devices. This was actually a major reason why I tried this beta firmware. There was a device I was making and every so often the network stopped telling home assistant about a device and then withing a few seconds or less it would be back. I moved on to other projects but I was figuring it was likely an mDNS (Multicast DNS) or ARP table failure within the Deco's firmware. Essentially, the device stayed connected to the Wi-Fi radio, but the Deco "forgot" where to route the data for a split second, or it stopped broadcasting the device's presence to the rest of the network. I think I fixed it by massively boosting the power which I shouldn't had to do. But ya the firmware itself didn't fix anything but it also did not break anything more. 

I think one of the problems is the device goes into a zombie state. Like for example I have a dockstream 2

(per water bowl hooked to the wifi). Wifi sees it, but it isn't talking to the internet. I seen a few devices do this. I'm not sure what the cause or fix to this is. 

____________________

A few things I sent support the logs. IDK if someone can look into that. I think I forgot to mention the routers are the newer version of the BE63. 

Also something I forgot to add in there is one way to prevent a device which shows up on the network but doesn't interact is label it as priority. Like it isn't a 100% fix, but it massively helps. I ended up having to do it today with the dockstream 2 because once again today it pulled this stunt and the only way to get it to actually use the network it was connected to is by turning the dockstream 2 all the way off and back on. If this was happening to 1 or 2 devices then I would say it is likely them. But it is happening to a number of them while others are just fine. And as indicated above, I think I did all I can in trying to troubleshooting. 

My next step if I can't figure it out is just jumping to a new system all together. I don't want to do that since this cost a bit of money.