Router WiFi Problems
Well, this tends to be common issue with BT and Plusnet routers. Why the default is to merge them from factory is, imho, 'stoopid'.
It would save all this hassle if they were split, right from the get-go
What happens is 5GHz device bounce from 5GHz to 2.4GHz most of the time. More so if you're just on the limit of the 5GHz.
(5GHz is better close to the router, but 2.4GHz reaches further)
(5GHz connects faster to the router, not necessarily to the www)
HTH
@DS wrote:
Well, this tends to be common issue with BT and Plusnet routers. Why the default is to merge them from factory is, imho, 'stoopid'.
There are arguably pro's and con's to both approaches. Yes, in this instance splitting the frequencies helps, but we're seemingly looking at a problem that shouldn't exist in the first place?
By splitting the SSIDs out of the box, you're adding complexity that some of our non-technically inclined customers may not have any desire to understand e.g. if you choose to connect solely to the 2.4GHz radio without understanding the implications, then you could be limiting the potential of your connection and introducing unnecessary congestion from competing access points.
Not entirely relevant to the Hub One, but you'll see the merged approach more and more as mesh Wi-Fi becomes more prevalent and Wi-Fi technologies mature (most mesh solutions require the 2.4GHz and 5GHz SSIDs to be aligned).
I was hoping to 'do the rounds' and dig a bit deeper into some of these complaints this weekend, however it's unfortunately going to have to wait as I'm without my laptop PSU and I've no other mechanism of getting onto the corporate VPN at the moment 
Hopefully make some progress next week...
There are arguably pro's and con's to both approaches. Yes, in this instance splitting the frequencies helps
I guess one could argue it's more pro's. It would appear that (my guesstimate) 95%+ are advised to split and voila it's fixed.
but we're seemingly looking at a problem that shouldn't exist in the first place?
Totally agree. Though if the routers were split at the 'factory', with yous lot, busy ironing this out, for the update to then merge them back, could avoid this sort of issue in the first place. This was an issue on the HH5, so plenty of time (you'd have thought) to suss it out...?
By splitting the SSIDs out of the box, you're adding complexity that some of our non-technically inclined customers may not have any desire to understand
Get that too Bob:). Though my thoughts above might be a better approach, perhaps? Let's say, for ease of use, WPS oly connected to 2.4GHz only, then users make a choice to manually connect to either?
if you choose to connect solely to the 2.4GHz radio without understanding the implications,
From my own experience, thus far, 2.4GHz is the better option, as 5GHz at roughly 6 metres is problematic. Understand the limits this causes, but can't see the majority of users sitting near the hub for most of the time. IDK, just guessing.
but you'll see the merged approach more and more as mesh Wi-Fi becomes more prevalent and Wi-Fi technologies mature
And I can see the positives to this too, but for me, the cost implications would be my limiting factor. If you're planning on releasing one, stick my name on a trialists list!!;)
I was hoping to 'do the rounds' and dig a bit deeper into some of these complaints this weekend, however it's unfortunately going to have to wait as I'm without my laptop PSU and I've no other mechanism of getting onto the corporate VPN at the moment
There's no rush. BT had long enough and I'm grateful you'll be seeing this one through to a positive conclusion 
won't you?
If you need a 'victim' for testing, although I'm about done (can see you posted over there, but not read it yet) with my testing, give me a shout. I'd love to finally crack the HH5/H1 issue, once and for all.
Just very frustrating.
Hi @Bones1959,
I'm sorry that you've been experiencing problems with the performance of your connection and for the inconvenience that this has caused. I can see that the last advisor that you spoke to treated this as a wireless issue, despite you mentioning that this is also affecting wired connections. I'm sorry for this oversight and I'll pass feedback on.
Testing your line isn't picking up the problem from here and indicates that your line is currently syncing at 36.3mbps:
If you've not done so recently, please can you run through our troubleshooting guides here. If these checks don't resolve the problem, please report it here and let us know when you've completed it.
