Virgin Media Community

[Yellow4life]

Smart devices are dropping out each night, these all seem to be on the 2.4Ghz network. I have the hub running in modem mode connected to a Tenda MW12 mesh system. This was put in place in the hope that the issue would resolve since the problem occured when using the Virgin Hub 3 in standalone router mode.

The smart lights will work throughout the day/after sunset but by the morning they appear offline meaning that the smart sensors (smartthings cannot reach them) to turn them on. If I switch the devices off/on then they come back online until the next day.

I have tried the usual hub reboot, hub reset. I even bought a new lighting system (Wiz) to see if this would resolve it.

Any ideas please?

15/02/2023 08:41:37 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/02/2023 08:41:33 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:47 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2023 10:52:9 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:47 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/02/2023 08:42:6 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2023 18:42:59 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2023 20:42:6 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2023 11:02:20 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2023 08:42:6 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2023 22:23:12 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/01/2023 20:42:6 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2023 12:23:7 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/01/2023 08:42:6 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:46 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 17:01:35 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 17:01:20 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 17:01:16 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 17:01:16 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 17:01:16 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 539000000 8.4 37 256 qam 17
2 547000000 8.4 37 256 qam 18
3 555000000 8.4 37 256 qam 19
4 563000000 8.3 37 256 qam 20
5 571000000 7.9 37 256 qam 21
6 579000000 7.1 37 256 qam 22
7 587000000 6.8 37 256 qam 23
8 595000000 5.6 37 256 qam 24
9 603000000 5.8 36 256 qam 25
10 611000000 7 36 256 qam 26
11 619000000 7.3 37 256 qam 27
12 627000000 7.3 37 256 qam 28
13 635000000 7.1 36 256 qam 29
14 643000000 7.3 37 256 qam 30
15 651000000 7.6 37 256 qam 31
16 659000000 7.1 37 256 qam 32
17 667000000 7.4 37 256 qam 33
18 675000000 7.5 37 256 qam 34
19 683000000 7 37 256 qam 35
20 691000000 7 37 256 qam 36
21 699000000 7 37 256 qam 37
22 707000000 7 37 256 qam 38
23 715000000 6.8 36 256 qam 39
24 723000000 6.5 36 256 qam 40

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.6 0 0
2 Locked 37.3 11 0
3 Locked 37.3 6 0
4 Locked 37.3 5 0
5 Locked 37.3 3 0
6 Locked 37.3 0 0
7 Locked 37.3 11 0
8 Locked 37.3 0 0
9 Locked 36.6 1 0
10 Locked 36.6 7 0
11 Locked 37.3 5 0
12 Locked 37.3 5 0
13 Locked 36.6 5 0
14 Locked 37.3 5 0
15 Locked 37.3 5 0
16 Locked 37.3 0 0
17 Locked 37.6 5 0
18 Locked 37.3 3 0
19 Locked 37.6 0 0
20 Locked 37.3 4 0
21 Locked 37.3 5 0
22 Locked 37.3 6 0
23 Locked 36.6 6 0
24 Locked 36.6 6 0

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 30100000 37 5120 64 qam 4
2 49600000 38.3 5120 64 qam 1
3 43100000 37.5 5120 64 qam 2
4 23600000 36.3 5120 64 qam 5
5 36600000 37.3 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 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
5 ATDMA 0 0 0 0

[Client62]

The Hub's log has three entries dated  01/01/1970  which suggest the Hub3 has been rebooted perhaps even powered off.

Look at the date / time just after each 1970 entry to see when that happened.

[Yellow4life]

Thanks for replying. I have restart the Hub a few times in the last couple of days - so there is nothing obvious here that could show what the problem is?

[David_Bn]

Thanks for your post on our Community Forums, and a very warm welcome to you @Yellow4life.

Sorry to hear of issues you've been experiencing with the connection, how have things been performing since your most recent post?

Have you set up a broadband quality monitor on the connection to keep tabs on this?

Kindest regards,

David_Bn

[Yellow4life]

Hello, thanks for the welcome. Sadly there has not been any progress really. The Yeelight and Wiz connected systems both seem to disconnect each night. They are definitely both on the 2.4 network

[Yellow4life]

Here’s my graph

https://www.thinkbroadband.com/broadband/monitoring/quality/share/031711bd5794b0bbc2ea842f9105badc72...

[Yellow4life]

Any replies please? Overnight graph

https://www.thinkbroadband.com/broadband/monitoring/quality/share/10df33622d62358e7d76dd1cb6175033cb26462e-23-02-2023

[Client62]

Using 2 quite different WiFi systems the devices become disconnected and remain disconnected.

If a mobile phone did that we would soon conclude the phone was faulty.

[Adri_G]

Hey Yellowlife, thanks for your posts and updates on our help forums and this thread.

A warm welcome to our community too!

We're sorry to hear of the connection issues being repeated, we'd love to best help with this.

Based on our latest checks there doesn't seem to be an issue with our network affecting your service, at the minute.

Can you please tell us how things look with your connection since you last posted here on Thursday and have you had any improvements?

Also, could you please let us know if the issue happens only on wireless or over wired connections too and have you noticed this with different devices as well?

Lastly, when did you last reboot the hub and has this helped at all restoring the connection problems, if so?

Let us know how you get on and if you need more help, here to assist further.