on 18-01-2022 15:20
So I have a hub 3, and when first installed 18 months ago had dropouts when using Wi-Fi calling on my mobile. I solved this by adding two wireless access points, one upstairs and one downstairs, then turning Wi-Fi off on the hub 3.
My home network has now grown and I now have over 100 connected devices.
All my computers, cctv and AV equipment are connected with Ethernet, so my two access points connect with Wi-Fi to 3 mobiles, 3 tablets, and all my smart switches, plugs, lamps, bulbs.
Recently I’ve had to power cycle my hub as my BroadLink stuff all stopped working, a week or so later all my Tapo plugs lost connection, and yesterday I had problems with my CALEX bulbs, some stopped working but not all, and they would not reprogram to my network without another hub 3 power cycle. My two TP link access points are set to power cycle monthly and seem to be fine, so could it be there are just too many signals for the hub to handle?
Would a better Virgin hub and dedicated repeaters or mesh system work better?
Answered! Go to Answer
on 23-01-2022 15:05
Hi johndm,
Thanks for your post and apologies to hear you were having networking issues.
I can see the Community have done a great job at jumping in to help.
It's great to see from your latest post that things are all resolved for you now.
If you do have any further issues, don't hesitate to pop back and let us know.
Take care,
on 18-01-2022 15:26
on 18-01-2022 15:31
I have fast speed wireless access points upstairs and downstairs to get a strong signal all around the house and to share the Wi-Fi load, and Wi-Fi on the hub is turned off so it is receiving everything via Ethernet
on 18-01-2022 15:37
18-01-2022 15:55 - edited 18-01-2022 15:59
I have a 500 connection which usually reads 550 with Speedtest
I do stream 4k but for instance when my smart bulbs started misbehaving yesterday everything was running 100%, and no AV equipment was in use, just computer mobiles and tablets connected along with all the smart plugs etc, no heavy demands on network.
I spent 2 hours trying to reconnect the misbehaving bulbs but they were having none of it despite everything else working just fine.
After a hub 3 power cycle they reconnected first time.
I did not power cycle the access points only the hub
on 18-01-2022 16:00
on 18-01-2022 16:05
1 | 203000000 | 2.2 | 38 | 256 qam | 9 |
2 | 139000000 | 4.1 | 38 | 256 qam | 1 |
3 | 147000000 | 3.7 | 40 | 256 qam | 2 |
4 | 155000000 | 3.4 | 38 | 256 qam | 3 |
5 | 163000000 | 3.2 | 38 | 256 qam | 4 |
6 | 171000000 | 3 | 38 | 256 qam | 5 |
7 | 179000000 | 3 | 38 | 256 qam | 6 |
8 | 187000000 | 2.7 | 38 | 256 qam | 7 |
9 | 195000000 | 2.5 | 40 | 256 qam | 8 |
10 | 211000000 | 2.2 | 38 | 256 qam | 10 |
11 | 219000000 | 2.2 | 38 | 256 qam | 11 |
12 | 227000000 | 2 | 38 | 256 qam | 12 |
13 | 235000000 | 1.9 | 38 | 256 qam | 13 |
14 | 243000000 | 1.2 | 38 | 256 qam | 14 |
15 | 251000000 | 0.2 | 38 | 256 qam | 15 |
16 | 259000000 | 0 | 38 | 256 qam | 16 |
17 | 267000000 | 0.7 | 38 | 256 qam | 17 |
18 | 275000000 | 1 | 38 | 256 qam | 18 |
19 | 283000000 | 1.4 | 38 | 256 qam | 19 |
20 | 291000000 | 1.7 | 40 | 256 qam | 20 |
21 | 299000000 | 2 | 38 | 256 qam | 21 |
22 | 307000000 | 2.4 | 38 | 256 qam | 22 |
23 | 315000000 | 2.5 | 38 | 256 qam | 23 |
24 | 323000000 | 2.7 | 38 | 256 qam | 24 |
1 | Locked | 38.6 | 41 | 0 |
2 | Locked | 38.6 | 15 | 0 |
3 | Locked | 40.3 | 46 | 0 |
4 | Locked | 38.9 | 38 | 0 |
5 | Locked | 38.9 | 42 | 0 |
6 | Locked | 38.9 | 40 | 0 |
7 | Locked | 38.9 | 51 | 0 |
8 | Locked | 38.9 | 35 | 0 |
9 | Locked | 40.3 | 32 | 0 |
10 | Locked | 38.6 | 31 | 0 |
11 | Locked | 38.9 | 24 | 0 |
12 | Locked | 38.9 | 38 | 0 |
13 | Locked | 38.9 | 32 | 0 |
14 | Locked | 38.9 | 30 | 0 |
15 | Locked | 38.9 | 76 | 0 |
16 | Locked | 38.6 | 72 | 0 |
17 | Locked | 38.9 | 57 | 0 |
18 | Locked | 38.9 | 44 | 0 |
19 | Locked | 38.9 | 46 | 0 |
20 | Locked | 40.3 | 36 | 0 |
21 | Locked | 38.9 | 53 | 0 |
22 | Locked | 38.9 | 55 | 0 |
23 | Locked | 38.9 | 85 | 0 |
24 | Locked | 38.9 | 67 | 0 |
on 18-01-2022 16:06
1 | 60300107 | 47.3 | 5120 | 64 qam | 1 |
2 | 39400000 | 44.8 | 5120 | 64 qam | 4 |
3 | 53700000 | 46.5 | 5120 | 64 qam | 2 |
4 | 46200000 | 45.8 | 5120 | 64 qam | 3 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 18-01-2022 16:07
Time Priority Description
18/01/2022 14:34:46 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/01/2022 22:34:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/01/2022 02:54:50 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/01/2022 17:45:13 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:32:14 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:31:53 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:31:52 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:30:39 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:30:37 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:30:35 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:29:27 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 23:29:24 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/01/2022 12:42:18 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/01/2022 02:43:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/01/2022 21:47:51 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/01/2022 13:27:59 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/01/2022 13:14:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/01/2022 09:47:51 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/01/2022 21:10:6 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/01/2022 21:09:59 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 18-01-2022 16:25