18-10-2021 13:11 - edited 18-10-2021 13:12
I'm desperately trying to find a solution to the poor wifi coverage I get from the superhub. If I put my laptop next to the router I get 150Mbps (as opposed to >200 wired). if I move 2 rooms away to where I have to work from I get 10-20Mbps and can't even do a zoom call.
I bought Google Nest Wifi (mesh) to solve this. It does a great job of coverage, but when the Nest wifi is connected to VM I get constant disconnects/restarts (seems to sometimes be that the nest system loses internet connection, other times the superhub does). I know the nest kit is fine, as I used it in on a non virgin set-up elsewhere, but i can't get VM and Nest to play nicely. (Google have put the blame squarely on VM btw)
Much as I disagree with paying subscription for hardware, I was hoping to get VM wifi pods to resolve this as this is causing serious issues with my job. Unfortunately you now can't order them for some reason.
Has anyone had (and hopefully resolved) similar issues with VM and Google wifi / Nest wifi ? Unfortunately I cannot work closer to the router and I cannot run a cable. I really need to get this resolved as it is causing problems with my job, but don't know what to do next.
I have done several factory resets of both sets of equipment, am using modem mode and have tried with all other devices disconnected. I feel like VM just doesn't work with Google/nest wifi but can see that others have used it.
I'm currently back to just trying to use the built in wifi. Spent my entire 1:1 quarterly review with our CEO apologising and asking them to repeat stuff.
I'd happily sign up for wifi pods at this point just to break the deadlock of Google blaming virgin blaming google.
on 18-10-2021 15:58
on 18-10-2021 16:01
I've gone through the process exactly like that multiple times (I've tried to get this working multiple times since I bought it over a year ago). Last time was a week or so agao and I did a factory reset on both nest devices before hand. Wonder if it is worth trying that agian, but isn't there some old saying about repeating things and expecting a different outcome?
on 18-10-2021 16:13
Along with many others I've had no problems with a mesh system and a VM hub, albeit I'm not using a Google Nest. Are you sure that your hub has a robust and reliable broadband connection? If it doesn't that could be the cause of your problems.
Connect to the hub log in page. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time.
You may also want to setup a Broadband Quality Monitor. But you'll need the hub in router mode to do this, because AFAIK the Nest mesh has no facility for responding to the ping requests that generate a BQM, and you need to make sure the BQM is tracking your current IP address (changes when switching mode on the hub). When setup, post a LINK to a LIVE, SHARED graph here and we'll see what's happening. Usually needs to run for 24 hours before we can draw reasonable conclusions, but the live graph will continuously update so you can post the link immediately.
on 18-10-2021 16:13
on 18-10-2021 18:10
Thanks @andrew-g
"Are you sure that your hub has a robust and reliable broadband connection?"
Hell no. I use Virgin. That said, it has been better than usual of late. We get a few days where things are not good, but generally if I test it from the hub or plug a cable in we are close to the 200 Mbps advertised. Past experience has sapped my confidence in it though. I've set up a broadband monitor though and we shall see.
Here's the log (this is currently in router mode - no Google gismo attached):
Downstream
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 202750000 | 6.5 | 40 | 256 qam | 9 |
2 | 210750000 | 6.1 | 40 | 256 qam | 10 |
3 | 218750000 | 6 | 40 | 256 qam | 11 |
4 | 226750000 | 5.5 | 40 | 256 qam | 12 |
5 | 234750000 | 4.5 | 38 | 256 qam | 13 |
6 | 242750000 | 5 | 40 | 256 qam | 14 |
7 | 250750000 | 5.9 | 40 | 256 qam | 15 |
8 | 258750000 | 6 | 40 | 256 qam | 16 |
9 | 266750000 | 6.1 | 40 | 256 qam | 17 |
10 | 274750000 | 6.4 | 40 | 256 qam | 18 |
11 | 282750000 | 6.6 | 40 | 256 qam | 19 |
12 | 290750000 | 6.6 | 40 | 256 qam | 20 |
13 | 298750000 | 6.8 | 40 | 256 qam | 21 |
14 | 306750000 | 6.9 | 40 | 256 qam | 22 |
15 | 314750000 | 6.9 | 40 | 256 qam | 23 |
16 | 322750000 | 7 | 40 | 256 qam | 24 |
17 | 330750000 | 7.1 | 40 | 256 qam | 25 |
18 | 338750000 | 7.5 | 40 | 256 qam | 26 |
19 | 346750000 | 7.5 | 40 | 256 qam | 27 |
20 | 354750000 | 7 | 40 | 256 qam | 28 |
21 | 362750000 | 6.4 | 40 | 256 qam | 29 |
22 | 370750000 | 6 | 40 | 256 qam | 30 |
23 | 378750000 | 6.3 | 40 | 256 qam | 31 |
24 | 386750000 | 6.5 | 40 | 256 qam | 32 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 19 | 0 |
2 | Locked | 40.3 | 46 | 0 |
3 | Locked | 40.9 | 38 | 0 |
4 | Locked | 40.3 | 23 | 0 |
5 | Locked | 38.9 | 33 | 0 |
6 | Locked | 40.3 | 35 | 0 |
7 | Locked | 40.3 | 12 | 0 |
8 | Locked | 40.3 | 9 | 0 |
9 | Locked | 40.3 | 10 | 0 |
10 | Locked | 40.3 | 15 | 0 |
11 | Locked | 40.3 | 19 | 0 |
12 | Locked | 40.3 | 19 | 0 |
13 | Locked | 40.9 | 12 | 0 |
14 | Locked | 40.3 | 16 | 0 |
15 | Locked | 40.3 | 23 | 0 |
16 | Locked | 40.3 | 36 | 0 |
17 | Locked | 40.3 | 20 | 0 |
18 | Locked | 40.3 | 25 | 0 |
19 | Locked | 40.9 | 94 | 0 |
20 | Locked | 40.3 | 22 | 0 |
21 | Locked | 40.3 | 14 | 0 |
22 | Locked | 40.3 | 20 | 0 |
23 | Locked | 40.3 | 12 | 0 |
24 | Locked | 40.3 | 11 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 43 | 5120 | 64 qam | 2 |
2 | 60300000 | 43.5 | 5120 | 64 qam | 1 |
3 | 39400000 | 42.8 | 5120 | 64 qam | 4 |
4 | 46200000 | 42.5 | 5120 | 64 qam | 3 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
Network log to follow - hit the character limi
on 18-10-2021 18:10
Network Log
Time Priority Description
18/10/2021 16:40:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/10/2021 12:47:44 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2021 16:38:45 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/10/2021 23:24:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/10/2021 20:56:58 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/10/2021 18:25:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/10/2021 07:40:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 12:23:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 03:07:35 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 03:07:35 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:47:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:47:55 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:47:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:43:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:43:49 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:43:48 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:43:45 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:33:58 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:33:57 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/10/2021 02:33:57 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19-10-2021 16:45 - edited 19-10-2021 16:57
and here is the broadband monitor for today so far.
Interesting that the worst time I noticed issues today was 3pm (really oddly I get significant issues around 3pm most days... although I may just notice that more as I have a daily zoom call at that time). 3pm doesn't look awful above.
20-10-2021 07:17 - edited 20-10-2021 07:19
There's nothing obviously wrong to my eye with the power, SNR, modulation and such like of your connection (in the snapshot that the data represents) but the BQM is poor, and the Network log has rather too many serious errors that exist between your hub and VM's network gear, although not consistently so - this has nothing to do with wifi.
I'll mark your post for forum staff to take a look, hopefully they'll see the nature of the network log and can offer some helpful advice. I suspect a technician is needed, but if VM can't see a problem with easily identified power or noise issues you might need to be persistent.
on 20-10-2021 07:50
Thanks Andrew.
Just for clarity for the staff: despite the thread title, all above are from when using VM only kit. The best kit is currently In a drawer