on 22-06-2023 20:44
The hub 3 has a constant orange light, paired with extremely poor internet, and it also cuts out intermittently (quite frequently too).
I've looked at previous posts with the same issues and have tried to solve it with all methods suggested to no avail.
I'm guessing the box has an OS or power problem
on 23-06-2023 15:51
Hi @olafssonl thanks for your post here in the Community, although we're sorry to hear of your concerns raised here.
So with the orange light, this doesn't identify a problem as it is merely just an issue with the LED light on the Hub which is ordinarily white. There'd only be a cause for concern if the light is red, which it doesn't appear to be from your message.
Are there any area issues identified here for you as this may provide some answers as to why you're experiencing the issues you are?
Please let us know.
Many thanks
on 24-06-2023 20:00
Hi Tom, thanks for the reply, I've looked at that link and there's been no problems there. I've looked at lots and lots of previous posts here about the same orange light paired with intermittent connection so there is clearly a correlation (My guess is there is a problem with the Operating system or the power in the router), and in all cases, it turned out that the router was broken and the only solution was a replacement router.
on 24-06-2023 22:47
Ignore the duff LED lets look elsewhere... are the issues only evident on wifi connections or do you see them at the same times on devices connected on ethernet cables? If you don't know, can you check to help diagnose whether it is just a wifi issue or it could be network connection/Hub related?
Then lets look at the Hub data - do this..
In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.
Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts
Also, If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK
https://www.thinkbroadband.com/broadband/monitoring/quality
on 25-06-2023 13:50
Firstly thanks for all that you sent, I've set up a broadband monitor now. Yes I do see issues with ethernet connection at the same time.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 330750000 | -0.5 | 38 | 256 qam | 25 |
2 | 202750000 | 0.7 | 40 | 256 qam | 9 |
3 | 210750000 | 0.4 | 40 | 256 qam | 10 |
4 | 218750000 | 0.4 | 40 | 256 qam | 11 |
5 | 226750000 | 0.2 | 40 | 256 qam | 12 |
6 | 234750000 | 0 | 40 | 256 qam | 13 |
7 | 242750000 | 0 | 38 | 256 qam | 14 |
8 | 250750000 | 0 | 40 | 256 qam | 15 |
9 | 258750000 | -0.2 | 40 | 256 qam | 16 |
10 | 266750000 | 0 | 40 | 256 qam | 17 |
11 | 274750000 | -0.4 | 40 | 256 qam | 18 |
12 | 282750000 | -0.4 | 38 | 256 qam | 19 |
13 | 290750000 | -0.5 | 38 | 256 qam | 20 |
14 | 298750000 | -0.4 | 38 | 256 qam | 21 |
15 | 306750000 | -0.5 | 40 | 256 qam | 22 |
16 | 314750000 | -0.4 | 38 | 256 qam | 23 |
17 | 322750000 | -0.5 | 38 | 256 qam | 24 |
18 | 338750000 | -0.4 | 38 | 256 qam | 26 |
19 | 346750000 | -0.5 | 38 | 256 qam | 27 |
20 | 354750000 | -0.7 | 38 | 256 qam | 28 |
21 | 362750000 | -0.7 | 38 | 256 qam | 29 |
22 | 370750000 | -0.9 | 38 | 256 qam | 30 |
23 | 378750000 | -0.9 | 38 | 256 qam | 31 |
24 | 386750000 | -1 | 38 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 26 | 0 |
2 | Locked | 40.3 | 13 | 0 |
3 | Locked | 40.3 | 21 | 0 |
4 | Locked | 40.3 | 13 | 0 |
5 | Locked | 40.3 | 15 | 0 |
6 | Locked | 40.3 | 22 | 0 |
7 | Locked | 38.9 | 31 | 0 |
8 | Locked | 40.3 | 25 | 0 |
9 | Locked | 40.3 | 20 | 0 |
10 | Locked | 40.3 | 15 | 0 |
11 | Locked | 40.9 | 13 | 0 |
12 | Locked | 38.9 | 21 | 0 |
13 | Locked | 38.9 | 23 | 0 |
14 | Locked | 38.9 | 28 | 0 |
15 | Locked | 40.3 | 15 | 0 |
16 | Locked | 38.9 | 20 | 0 |
17 | Locked | 38.9 | 29 | 0 |
18 | Locked | 38.9 | 24 | 0 |
19 | Locked | 38.6 | 25 | 0 |
20 | Locked | 38.9 | 24 | 0 |
21 | Locked | 38.9 | 32 | 0 |
22 | Locked | 38.9 | 21 | 0 |
23 | Locked | 38.6 | 17 | 0 |
24 | Locked | 38.9 | 26 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36600000 | 41.8 | 5120 | 64 qam | 9 |
2 | 49600000 | 42.5 | 5120 | 64 qam | 7 |
3 | 23600000 | 40.8 | 5120 | 64 qam | 11 |
4 | 43100000 | 42 | 5120 | 64 qam | 8 |
5 | 30100000 | 41.3 | 5120 | 64 qam | 10 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
on 25-06-2023 13:51
Time Priority Description
25/06/2023 13:26:33 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/06/2023 03:43:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/06/2023 02:30:43 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2023 15:50:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/06/2023 14:30:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/06/2023 01:34:54 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2023 02:30:40 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/06/2023 20:57:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/06/2023 14:30:39 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/05/2023 19:49:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/05/2023 02:30:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/05/2023 06:23:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/05/2023 14:30:37 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/05/2023 15:18:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/05/2023 14:27:36 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/05/2023 02:30:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/05/2023 05:30:16 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/05/2023 15:27:20 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/05/2023 15:27:20 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/05/2023 15:27:8 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 26-06-2023 15:55
Thanks for the response on this olafssoni,
Just regarding this matter I can't currently see any readings that would attribute to this, once the BQM has a reading also post that and we'll investigate further.
Regards,