@bobpullen I agree, as DFS is not suitable for everyone...
Yes, 10 minutes mandatory observation before it's allowed to be used it's quite long. As well as we talking about 250ms back and forward when device need to check if replacement channel it's available, what is not problem for Netlfix, or Web, but definitely wil be problem for xBox or VOIP, while introduce some lag/jitter which you can prevent with no using DFS at all.
My personal setup is, as I have available one non-DFS channel on separate AP, which is in fact limited to 40 Mhz wide, and main channels are on DFS where 160 Mhz, resp. 80 Mhz is set as standard. This way, devices first go for what it's available first, and then, utilising "k" roaming, switch for better. 99% of time, they have 80 resp. 160 Mhz depends what they are capable.
All my 2.4 Ghz channels are 20 Mhz (how they should be anyways) even I seen crazy neighbours setting them up to max what they router could do (and many simple to 40 Mhz wide), and messing interference even more... Plus, I have locked my demanding devices to 5 Ghz channels, and only IOT and Google Nest, and rPis are on 2.4 where no UTP is practicable.
Again, forcing devices to use best available, or forcing them to limit self to purpose.
This unfortunately is not possible on EE supplied routers, but certianly, new PRO (Wifi 7) one should be abla to handle better speeds, with combination of OP devices.
