Hi Support Team,

I am using a Deco BE65 (V2) setup with a high-demand network (60+ Wi-Fi clients, Home Assistant with 32 Zigbee devices). While the hardware performance is great, the software logic in Firmware 1.2.0 (Build 20250718) is deeply flawed and restricts professional use.

I want to highlight three major issues that need to be addressed in the upcoming official release:

1. IoT Network & 2.4GHz Dependency:

If I disable the 2.4GHz band in the Main Wi-Fi (to keep it clean for high-speed devices), I lose all ability to manage the 2.4GHz environment. Since the IoT Network lacks manual channel and MHz settings, I am stuck with "Auto-settings." For a power user with 32 Zigbee devices, this is unacceptable as I cannot prevent frequency interference between Wi-Fi and Zigbee. Why is there no independent channel control for the IoT network?

2. Illogical MLO Band Selection:

In the MLO settings, I cannot choose which bands to use. It is hard-coded to "5GHz/6GHz." I should be able to decide which bands are aggregated. Furthermore, there is a weird dependency: If I disable 6GHz in the Main Wi-Fi settings, it completely disappears from the MLO options as well. These bands should be treated as independent resources.

3. Performance vs. Gaming Stability:

I found that MLO (5GHz/6GHz combined) causes significant jitter and ping spikes in competitive mobile games (like Wild Rift on a RedMagic device). To get a "snappy" and stable connection, I have to disable MLO entirely. While the internal Backhaul luckily stays on 5GHz/6GHz, the user-facing MLO implementation feels unoptimized and "beta."

Conclusion:

We are approaching May 2026, and the last stable firmware is nearly a year old (July 2025). We need a firmware that finally decouples these settings and gives us manual control over channels and bands. We bought Wi-Fi 7 flagships, but the software feels like an "Autopilot" for beginners that limits the hardware's potential.

I hope the upcoming 1.3.0/1.4.0 official release finally fixes these logic traps.