Update: I am getting nowhere by swapping 2.4 and 5GHz channels. I am still seeing a fairly regular dropping out of the wifi, and then within 30 seconds or so my laptop shows it has auto logged on to the wifi channel again. I contacted BT and they also can see a log of drops in wifi once a day - although I am experiencing it more frequently when browsing.
I did a full factory rest of the Smart Hub 2. That doesn't seem to have improved things. It has also flagged (when logging on to the wifi in Settings on an iPhone) that "this network is blocking encrypted DNS traffic". I have not seen this alert on my own WiFi network before. Can anyone help me and explain what this means and if I should tweak my router settings back to how they were? (I assume the reset lost my optimal settings)
The log error that sticks out is repeated often:
5G Client disassociate from 56:7b:a7:cf:8c:99 (IP=192.168.1.98) RSSI=0, Rate=0Mbps
Try giving the laptop a static IP address. I believe the DHCP range for the Smart Hub 2 starts at 192.168.1.64, so any address below this will take DHCP out of the equation.
Update:
I swapped out the Smart Hub 2 for a new one sent by BT. That sorted out the issue for a short while, but overnight the firmware autoupdated to v0.31.00.10253-BT and from then on it seems the issues continue - the regular loss of wifi for 3 seconds or so.
My woes continue. I have done a complete swap out of the Smart Hub 2, and taken the BT Disc out of the network. Both 2.4GHz and 5GHz are on. Smart setup is off, and smart channels are off.
My regular 3 - 5 second loss of wifi continues... even to the point of posting on this forum stalled and required a refresh. The log for that event is here repeating 7 times:
@rbz5416 I put the macbook onto a manual IPv4 IP address. However the drop outs continue.
As the Smart Hub 2 can't split the bands I tried working with just 5GHz (switching off 2.4GHz) but unfortunately some of my devices need 2.4GHz band.
I'm having the exact same issues. I've been talking with BT for 3 weeks now. They've swapped my Smart Hub, they've checked the line and now i have a tech guru coming on Saturday. Its also affecting my wired conections too.
@NicolasS I'd be most interested to hear the result of your investigations.
BT phone help was sympathetic but didn't have much in the way of insight nor knowledge base on the fault... but clearly many people are having the same issue... mine is so regular that I have to refresh pages often. Like when I post here!
18:44:10, 08 Mar. admin timeout from 192.168.1.22
18:43:59, 08 Mar. DHCP device Connected: 192.168.1.69, 02:9b:36:ae:4c:ae, unknown
18:43:59, 08 Mar.5G Client disassociate from 02:9b:36:ae:4c:ae (IP=192.168.1.69) RSSI=0, Rate=0Mbps
18:43:59, 08 Mar.LAN [ADD] ARP 192.168.1.69 with 02:9b:36:ae:4c:ae from br0(wl1)
18:43:57, 08 Mar.WHW INFO A station (SmartHub2)IF[2.4G](60:8D:26:34:4B:51):STA(02:9B:36:AE:4C:AE)(Legacy Device) join WHW infrastructure
18:43:56, 08 Mar.5G client Mac: 02:9B:36:AE:4C:AE Deauthentications (Reason:Deauthenticated because sending station is leaving (or has left) IBSS or ESS)
18:43:56, 08 Mar.Self roaming might be occurring... Deauth original one...
18:43:41, 08 Mar. DHCP device Connected: 192.168.1.69, 02:9b:36:ae:4c:ae, unknown
18:43:41, 08 Mar. LAN [ADD] ARP 192.168.1.69 with 02:9b:36:ae:4c:ae from br0(wl0)
@pmosb no problem, I will post back on Saturday.
Same here. I can't fault them for their help, but what is causing it is a mystery.
If you have an old Hub kicking around it might be worth trying that for a few days. Although it's highly unlikely that two SH2s would have the same fault. But having said that, I had two HH5s that randomly dropped 5GHz in the same way, so it's not impossible. But if you try a different variation of Hub & still get the same issue, it's almost certainly going to be down to your environment.
If you have DV & are tied to the SH2, you could turn off it's WiFi & DHCP server & connect the other Hub by ethernet to serve the internal network. You'll need to change the IP address of the second router away from 192.168.1.254 or it will clash with the SH2.
You could also change the WiFi SSID & password to match the SH2 so you don't have to reconnect all your clients.