Wifi is terrible and constantly dropping even after boosters

[LS95]

CONSTANT problems with the WiFi i swear it has been throughout the entire of my contract, at first i thought it was just the 360 tv box however it is now all devices connected via WiFi, the hub has been replaced 3 times and am honestly coming to my wits end. here is the broadband monitor : 

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

Downstream bonded channels

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

1	330750000	1.4	40	256 qam	25
2	202750000	2.2	40	256 qam	9
3	210750000	2.2	40	256 qam	10
4	218750000	2.2	40	256 qam	11
5	226750000	2	40	256 qam	12
6	234750000	2	40	256 qam	13
7	242750000	1.7	40	256 qam	14
8	250750000	1.5	40	256 qam	15
9	258750000	1.4	40	256 qam	16
10	266750000	1.2	40	256 qam	17
11	274750000	1	40	256 qam	18
12	282750000	0.9	40	256 qam	19
13	290750000	0.7	40	256 qam	20
14	298750000	1	38	256 qam	21
15	306750000	1	40	256 qam	22
16	314750000	1.2	40	256 qam	23
17	322750000	1.2	40	256 qam	24
18	338750000	1.7	40	256 qam	26
19	346750000	1.5	40	256 qam	27
20	354750000	1.5	40	256 qam	28
21	362750000	1.7	40	256 qam	29
22	370750000	1.7	40	256 qam	30
23	378750000	1.9	40	256 qam	31
24	386750000	1.7	40	256 qam	32

Downstream bonded channels

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

1	Locked	40.9	213	0
2	Locked	40.9	247	0
3	Locked	40.3	218	0
4	Locked	40.3	230	0
5	Locked	40.3	213	0
6	Locked	40.3	229	0
7	Locked	40.3	204	0
8	Locked	40.3	216	0
9	Locked	40.3	207	0
10	Locked	40.3	205	0
11	Locked	40.3	212	0
12	Locked	40.3	205	0
13	Locked	40.3	241	0
14	Locked	38.6	227	0
15	Locked	40.3	216	0
16	Locked	40.3	226	0
17	Locked	40.3	218	0
18	Locked	40.3	201	0
19	Locked	40.3	222	0
20	Locked	40.3	232	0
21	Locked	40.3	230	0
22	Locked	40.9	192	0
23	Locked	40.3	184	0
24	Locked	40.3	181	0

[LS95]

Upstream bonded channels

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

1	23600000	32	5120	64 qam	6
2	32600000	32	5120	64 qam	5
3	39400000	32	5120	64 qam	4
4	46200000	32	5120	64 qam	3

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	7	0
2	ATDMA	0	0	3	0
3	ATDMA	0	0	4	0
4	ATDMA	0	0	1	0

[LS95]

Network Log

Time Priority Description

19/12/2023 01:37:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2023 13:05:0	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/12/2023 13:05:0	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/12/2023 03:25:6	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/12/2023 01:05:0	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/12/2023 01:05:0	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 19:54:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:59:5	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:59:5	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:58:57	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:58:57	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:30	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:30	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:29	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:29	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:28	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:13	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:9	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:9	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/12/2023 11:57:9	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[jbrennand]

Your upstream power levels are on the low side - may be contributing to the T3 errors.

A VM person needs to comment

[legacy1]

---

@jbrennand wrote:

Your upstream power levels are on the low side - may be contributing to the T3 errors.

---

Not really the BQM shows ok we don't know how long the hub has been on when T3 happened unlike SH1 where the counter reset every 24hr making it easy.😋

I would suggest using the hub in modem mode and get your own better router with 1Gb ports

[jbrennand]

---

@legacy1 wrote:

---

@jbrennand wrote:

Your upstream power levels are on the low side - may be contributing to the T3 errors.

---

Not really the BQM shows ok we don't know how long the hub has been on when T3 happened

unlike SH1 where the counter reset every 24hr making it easy.😋

---

Agree re. the BQM not showing the drops, but the Up powers are on the low side - so worth a VM check.

This is from a VM comment on an old post ...

Upstream we try to maintain between 35 dBmV and 51 dBmV. Again, we have seen perfectly normal connections working outside of this range, probably between 30-56, so again these should be treated as an indication rather than a definitive indication of a fault.

[Gareth_L]

Hello LS95

Thank you very much for your post 
Can I just apologise for the T3 errors
We can run a few tests from here and check on your equipment.
Sadly it's not showing anything wrong, So I will need to send you a private message to gain account access and run further tests.

In the meantime can you reboot our hub as its been online for quite a while
If you can check the logo top right of your screen that would be great. 
Regards     
Gareth_L
 

[Gareth_L]

Hello LS95.

Thanks for your time today.

Now that we have had to arrange a service technician to attend.

Can you please let us know how the visit goes.

Gareth_L

[LS95]

Hi Gareth just letting you know its been almost a week and so far all issues seem resolved, thanks again so much for the help

[Beth_G]

Hi LS95

Happy New Year!

Thanks very much for the update - we're pleased to hear the issues seem to have cleared for you.

Just double checked our end and all seems OK from here too.

If you have any further trouble, just let us know  😊