on 15-06-2022 15:31
Hi all, another WiFi dropping post, seems there are many on here. This has been getting gradually worse over the last 2 weeks.
My WiFi is cutting out every few minutes, so I have to disconnect wifi on my device, then reconnect, and its fine for a few minutes, before dropping out again. Mainly happening on my MacBook Pro (as I'm using it the most), but also happens on my iPhone, iPad, my girlfriends MacBook Air, her iPhone, her iPad and her works Samsung phone. So it's clearly not an issue with an individual device.
I work from home, and this basically means I cannot do my job (I'm also in a signal blackspot with my phone network (Three), so I cannot rely on my phone signal). I get disconnected from work calls all the time, which is infuriating.
I have a Hub 4 with two Powerline Boosters (both connected via Ethernet) to serve a small 2 bedroom flat (the Hub 4 on its own can't even reach the bedroom).
Additionally, when I try to monitor what devices are connected to my Wifi network, there are two 'unknown' devices (with MAC addresses that I cannot determine the source of), and the list only shows a small proportion of the number of devices that should be connected (cannot see 2 iPads or 1 iPhone), leaving me to wonder what else is connected that shouldn't be.
I have reset my Hub 4 router countless times
Here's my BQM for the last 24hrs.
Here are my Network Status statistics from the Settings page (192.168.0.1):
Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
I keep getting upload errors so I'll post the remaining stats in subsequent thread
on 15-06-2022 15:53
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | -2.5 | 39 | QAM256 | 25 |
6 | 178750000 | -2.5 | 38.6 | QAM256 | 6 |
7 | 186750000 | -2.3 | 39 | QAM256 | 7 |
8 | 194750000 | -3.2 | 38.6 | QAM256 | 8 |
9 | 202750000 | -3.6 | 38.6 | QAM256 | 9 |
10 | 210750000 | -3.4 | 38.6 | QAM256 | 10 |
11 | 218750000 | -3.5 | 36.4 | QAM256 | 11 |
12 | 226750000 | -4 | 37.4 | QAM256 | 12 |
13 | 234750000 | -3 | 38.6 | QAM256 | 13 |
14 | 242750000 | -3.4 | 39 | QAM256 | 14 |
15 | 250750000 | -3 | 39 | QAM256 | 15 |
16 | 258750000 | -2 | 38.6 | QAM256 | 16 |
17 | 266750000 | -1.1 | 38.6 | QAM256 | 17 |
18 | 274750000 | -1.5 | 39 | QAM256 | 18 |
19 | 282750000 | -1.1 | 39 | QAM256 | 19 |
20 | 290750000 | -0.6 | 38.6 | QAM256 | 20 |
21 | 298750000 | -1.7 | 39 | QAM256 | 21 |
22 | 306750000 | -2.1 | 38.6 | QAM256 | 22 |
23 | 314750000 | -1.8 | 39 | QAM256 | 23 |
24 | 322750000 | -2 | 38.6 | QAM256 | 24 |
26 | 338750000 | -2 | 38.6 | QAM256 | 26 |
27 | 346750000 | -2.6 | 39 | QAM256 | 27 |
28 | 354750000 | -3 | 38.6 | QAM256 | 28 |
29 | 362750000 | -3.5 | 38.6 | QAM256 | 29 |
30 | 370750000 | -2.9 | 38.6 | QAM256 | 30 |
31 | 378750000 | -3.5 | 38.6 | QAM256 | 31 |
32 | 386750000 | -3 | 39 | QAM256 | 32 |
34 | 394750000 | -3.1 | 38.6 | QAM256 | 34 |
35 | 402750000 | -3.1 | 38.6 | QAM256 | 35 |
36 | 410750000 | -3.4 | 38.6 | QAM256 | 36 |
37 | 418750000 | -2.8 | 39 | QAM256 | 37 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.605377 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.605377 | 0 | 0 |
9 | Locked | 38.605377 | 0 | 0 |
10 | Locked | 38.605377 | 0 | 0 |
11 | Locked | 36.386890 | 0 | 0 |
12 | Locked | 37.355988 | 0 | 0 |
13 | Locked | 38.605377 | 0 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 38.605377 | 0 | 0 |
17 | Locked | 38.605377 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 38.605377 | 0 | 0 |
21 | Locked | 38.983261 | 0 | 0 |
22 | Locked | 38.605377 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 38.605377 | 0 | 0 |
26 | Locked | 38.605377 | 0 | 0 |
27 | Locked | 38.983261 | 0 | 0 |
28 | Locked | 38.605377 | 0 | 0 |
29 | Locked | 38.605377 | 0 | 0 |
30 | Locked | 38.605377 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
32 | Locked | 38.983261 | 0 | 0 |
34 | Locked | 38.605377 | 0 | 0 |
35 | Locked | 38.605377 | 0 | 0 |
36 | Locked | 38.605377 | 0 | 0 |
37 | Locked | 38.983261 | 0 | 0 |
33 | 94 | 4K | 1840 | QAM4096 | 424 |
33 | Locked | 40 | -2.8 | 193509154 | 4624 |
on 15-06-2022 15:54
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 47.8 | 5120 KSym/sec | 64QAM | 10 |
2 | 46200000 | 47.8 | 5120 KSym/sec | 64QAM | 9 |
3 | 60300000 | 47.5 | 5120 KSym/sec | 64QAM | 7 |
4 | 53700000 | 48 | 5120 KSym/sec | 64QAM | 8 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
on 15-06-2022 15:55
And here's the Network Log...
Time Priority Description
Thu 01/01/1970 00:01:26 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 12/06/2022 23:53:42 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/06/2022 00:40:21 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:26 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/06/2022 14:59:44 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/06/2022 15:41:37 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/06/2022 17:22:31 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/06/2022 20:27:28 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 13/06/2022 22:29:43 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:23 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/06/2022 16:39:44 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/06/2022 16:52:23 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/06/2022 18:38:07 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/06/2022 21:14:26 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:27 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 14/06/2022 23:23:32 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:23 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/06/2022 01:33:48 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/06/2022 02:26:11 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/06/2022 10:36:14 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 15/06/2022 12:43:46 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 15-06-2022 16:02
on 15-06-2022 16:07
One more thing to note, when I do a Network Diagnostics I keep getting WiFi Connection errors, although no actual information on what the error is or how to fix:
This is despite the Home Page showing that my WiFi is working:
For most of the other threads on here with similar problems, the solution is either put the Hub in modem mode and get a 3rd party router, or move to BT. Given that we're already paying a fortune for a VM service (that already includes VM hacks to get the hub working, such as the Powerline Boosters), the latter is looking most attractive at the moment.
on 15-06-2022 16:14
Thanks for the reply John. Yep I think wifi only, as I don't have ethernet connection between devices and Hub 4 (and I'm not sure how to monitor the ethernet connection between the Hub 4 and the Powerline Booster).
What I might do tonight is move the Powerline Booster and Hub 4 to a different part of the lounge, so its connected to different plugs.
on 15-06-2022 18:06
on 15-06-2022 20:00
Hey @BK_76,
Welcome back to the community and thanks for taking the time to post.
I have looked into our live system and can see that your downstream power levels are too low and this will need a technician visit to resolve.
I can arrange the appointment from here but would need to confirm a few details via a private message, that I will drop over in a moment.
Please look out for the private message and we can get started.
Regards,
Steven_L
on 15-06-2022 22:17