Best Mesh for Hub 4 and 1Gb

[guilbert]

I have a Hub 4 on 1Gb. 

Would like to get a Mesh system as the wi fi gives us problems (dropping out etc)

We are not massive users of wi fi, just phones, tablets etc and also Sky Q. But my son in his attic bedroom has a PS4 and a computer (and streams TV a lot to his PC, often Sky AND BT Sports at the same time).

Don't mind spending a bit of money to get a good system. 

I am fairly technical (work in computers) but never set up a Mesh system before or put the Virgin router in modem mode so something "easy" to set up would be good..

[Andrew-G]

Almost all mesh systems are consumer oriented, so reasonably easy to setup.  From there on, depends on the budget.  

An Asus Zen Wifi Ax system is pricey, but very competent indeed, and supports the superior Wifi 6 standard (only helps if the devices do).  A Netgear Orbi RBK353 is a somewhat cheaper Wifi 6 option and comes with three nodes. 

If you're not fussed about Wifi 6, then there's a range of cheaper mesh options.  The TP-Link Deco M4 or S4 are a good solid choice for only a hundred quid, but you'll see slower maximum speeds as it only supports 802.11ac wifi (around 450-500 Mbps tops over wifi), and without an ethernet link to the satellites the speed you'll get through those satellites will be considerably lower, in the 150-300 Mbps range.   If you can connect them back to the master unit by ethernet and a switch that's a budget way of getting faster wifi from the satellites.  Tri-band mesh systems minimise the degradation of speed via satellites, but tend to be priced uncomfortably close to a Wifi 6 mesh in my view.

Edit: Before spending money, how sure are you that the dropouts are wireless only?  You wouldn't want to splash out on a top notch mesh system, and then find the problem is in fact ropey broadband.  Might be worth posting the hub's status data in a few replies here, and setting up a Broadband Quality Monitor - boiler plate advice on both below:

Connect to the hub by clicking on this link http://192.168.0.1/  That should pull up the log in page for the hub.  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.

Setup a BQM over at https://www.thinkbroadband.com/broadband/monitoring/quality that'll show what's going on with your VM connection.  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.

[Adduxi]

Good solid advice from Andrew, as always.

However, if you are competent with IT, I would consider the PoE Access Point route for your WiFi.  Some of the Forum members here use Ubiquity kit, but there are others not as expensive.  Neat, unobtrusive and can be ceiling mounted similar to smoke alarms, with power being supplied via the ethernet cables.

Just my tuppence worth of food for thought. 

[Andrew-G]

Indeed that's a good idea that I hadn't considered.   If going down this route then budget for a decent PoE ethernet switch (the hub doesn't support PoE) and for premium quality Cat 6a cables warrantied for PoE.  You may need to configure the PoE APs in a particular way to achieve the seamless coverage that a good mesh system offers, but it can be done.  Personally, if going with PoE I'd also put in a decent router to replace the Hub 4's router, rather than letting the AP's be managed by the hub.  General wisdom here is that the routers built in to all VM hubs are a bit shonky.

As @Adduxi says, done properly this can be really well hidden, and offer a business grade of performance, but you'll need to roll your sleeves up to get it setup, and have good DIY skills to install invisibly.  In turn that may require some domestic negotiation because you'll probably be doing a fair bit of carpet and floor lifting, and you'll almost certainly need to run ethernet cables between floors.  By comparison, a mesh system uses a mains power socket at each node, and won't normally be practical for ceiling mount, and running ethernet between the mesh nodes if needed may be more obtrusive than a well installed ceiling mounted PoE installation.

[guilbert]

Thanks for all the answers. I set up ThinkBroadband ages ago (maybe a year ago) when I was having Virgin Broadband problems (this was on Hub 3).

Looking at my graph I am getting LOADS of high yellow spikes (maximum latency)

Here is my graph  (not sure what "link" to post to show the graph)

Direct Link

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d9602410b7e027fb2d0c1e2766d849c40a78bdb9

Text Link

<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/d9602410b7e027fb2d0c1e2766d849c40a78bdb9">My Broadband Ping</a>

Small graph

<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/d9602410b7e027fb2d0c1e2766d849c40a78bdb9"><img alt="My Broadband Ping - Virgin Cable 200mbps" src="https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/d9602410b7e027fb2d0c1e2766d849c40a78bdb9.png" /></a>

[guilbert]

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

5	171000000	6.500000	38.605377	QAM256	5
1	139000000	7.000000	38.605377	QAM256	1
2	147000000	6.900002	38.605377	QAM256	2
3	155000000	6.900002	38.605377	QAM256	3
4	163000000	6.699997	38.605377	QAM256	4
6	179000000	6.000000	38.605377	QAM256	6
7	187000000	6.000000	38.983261	QAM256	7
8	195000000	5.900002	38.605377	QAM256	8
9	203000000	5.900002	38.983261	QAM256	9
10	211000000	5.500000	38.983261	QAM256	10
11	219000000	5.500000	38.605377	QAM256	11
12	227000000	4.800003	38.605377	QAM256	12
13	235000000	4.400002	38.605377	QAM256	13
14	243000000	3.700001	38.983261	QAM256	14
15	251000000	3.400002	37.355988	QAM256	15
16	259000000	2.500000	37.355988	QAM256	16
17	267000000	3.400002	38.605377	QAM256	17
18	275000000	3.900002	38.605377	QAM256	18
19	283000000	4.500000	38.605377	QAM256	19
20	291000000	4.199997	38.605377	QAM256	20
21	299000000	4.000000	38.983261	QAM256	21
22	307000000	3.599998	38.983261	QAM256	22
23	315000000	3.799999	38.983261	QAM256	23
24	323000000	4.000000	38.605377	QAM256	24
25	347000000	4.300003	38.605377	QAM256	25
26	355000000	4.699997	38.983261	QAM256	26
27	363000000	4.099998	38.605377	QAM256	27
28	371000000	5.000000	38.983261	QAM256	28
29	379000000	4.500000	38.983261	QAM256	29
30	387000000	4.400002	38.983261	QAM256	30
31	395000000	3.299999	38.605377	QAM256	31

3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

5	Locked	38.605377	0	0
1	Locked	38.605377	0	0
2	Locked	38.605377	0	0
3	Locked	38.605377	321	0
4	Locked	38.605377	6	0
6	Locked	38.605377	7	0
7	Locked	38.983261	5	0
8	Locked	38.605377	6692	0
9	Locked	38.983261	1534	0
10	Locked	38.983261	2021	0
11	Locked	38.605377	610339	0
12	Locked	38.605377	0	0
13	Locked	38.605377	0	0
14	Locked	38.983261	0	0
15	Locked	37.355988	0	0
16	Locked	37.355988	0	0
17	Locked	38.605377	0	0
18	Locked	38.605377	0	0
19	Locked	38.605377	0	0
20	Locked	38.605377	0	0
21	Locked	38.983261	0	0
22	Locked	38.983261	0	0
23	Locked	38.983261	0	0
24	Locked	38.605377	0	0
25	Locked	38.605377	0	0
26	Locked	38.983261	0	0
27	Locked	38.605377	0	0
28	Locked	38.983261	0	0
29	Locked	38.983261	0	0
30	Locked	38.983261	0	0
31	Locked	38.605377	0	0

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

96

4K

1880

QAM4096

759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

40

-2.7

526117793

34

[guilbert]

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	32600000	40.020599	5120 KSym/sec	64QAM	5
2	25800000	38.770599	5120 KSym/sec	64QAM	6
3	39400000	40.520599	5120 KSym/sec	64QAM	4
4	46200000	41.020599	5120 KSym/sec	64QAM	3

3.0 Upstream channels

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

[guilbert]

For some reason latest entries in Network Log are for 8th and 9th October. Tried refresh data.

Network Log

Time Priority Description

Fri Oct 8 13:22:45 2021	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:22:45 2021	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; 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;
Fri Oct 8 13:22:46 2021	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:22:52 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:04 2021	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; 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;
Fri Oct 8 13:23:05 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:05 2021	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 11; 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;
Fri Oct 8 13:23:06 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:11 2021	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:12 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:13 2021	6	CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; 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;
Fri Oct 8 13:23:14 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:49 2021	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:23:49 2021	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:24:09 2021	3	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:24:09 2021	3	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:25:09 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:29:11 2021	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:29:12 2021	6	CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; 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;
Fri Oct 8 13:29:39 2021	5	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:29:48 2021	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:29:48 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:29:52 2021	6	CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; 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;
Fri Oct 8 13:29:52 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:29:56 2021	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 24; 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;
Fri Oct 8 13:29:57 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:30:03 2021	6	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:30:03 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:30:04 2021	6	CM-STATUS message sent. Event Type Code: 4; Chan ID: 11; 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;
Fri Oct 8 13:30:05 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:32:03 2021	3	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:33:17 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:36:31 2021	6	CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; 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;
Fri Oct 8 13:45:30 2021	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 13:47:05 2021	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 14:38:48 2021	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 14:40:00 2021	6	DS profile assignment change. DS Chan ID: 159; Previous Profile: ; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 8 14:51:03 2021	5	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 9 05:21:20 2021	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat Oct 9 10:59:30 2021	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Andrew-G]

Can you check that your BQM applies to your current IP address?

Reason I ask is that it looks worryingly consistent with high level over-utilisation.  If that's correct then I'd expect a poor gaming experience with erratic ping, and unreliable video conferencing.  No mesh or router change will solve that.

[guilbert]

Thanks for the reply.

I have deleted the old graph and created a new one with the name Oct 16th 2021 - New 1G with Hub 4"

Link here 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/fcd3b4de668b9fdd938d9234c794175aed1603d8