Menu
Reply
Z92
  • 2.28K
  • 190
  • 357
Problem sorter
216 Views
Message 21 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

I think half the problem on WiFi is simply because VM routers have the aerials internal and against other noisy electronics, where as "proper" access points normally have external aerials and thus are isolated more from other electronics. 

As a case in point, I tried a Ring doorbell with the VM hub and the doorbell was sporadic - it would miss movement and sometimes even doorbell pushes, looking into the diagnostics said it had a signal strength of -85 to -90, now with an external router in the same position it gets -60 which is far better and is no longer intermittent. 

So if you just WiFi for emails and web browsing the included router is fine - but if you depend on WiFi for anything more than that you should invest in a better router and put the VM box into modem mode. 

0 Kudos
Reply
Adduxi
  • 2.92K
  • 221
  • 623
Trouble shooter
215 Views
Message 22 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa


@LindaRuth wrote:

Thank you for responding again. 

I have tried posting broadband quality monitoring graphs. They haven't appeared despite removing personal details. 

How do I get the logs you mention?

Thanks


Pictures have to be approved by the VM Mods, so they take a while to appear.

For the logs etc,  log onto the Hub at 192.168.0.1 and for the Hub 4 I think it's under the Advanced tab somewhere. I don't have one, so not sure. Just copy and paste into the message and don't worry about invalid HTML messages, just continue and the Board software will remove the problems and post anyway.

LindaRuth
  • 35
  • 0
  • 2
On our wavelength
201 Views
Message 23 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

Here is the network log:

Network LogTime Priority Description
Fri 25/09/2020 18:33:543Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:33:543No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:33:553Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:33:553No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:34:044Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:35:373No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:36:035MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 18:58:273No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 19:00:535MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 19:00:583No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 19:54:466CM-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 25/09/2020 19:55:023SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 19:55:106CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 19:59:143SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 19:59:466CM-STATUS message sent. Event Type Code: 5; Chan ID: 22; 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 25/09/2020 20:05:553SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 20:05:593No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/09/2020 20:06:096CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 26/09/2020 00:48:273No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 28/09/2020 20:44:005MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 29/09/2020 05:15:486CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 181439; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 30/09/2020 17:23:144DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 30/09/2020 17:23:146DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/10/2020 10:23:323No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 12:17:126CM-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;
Sat 03/10/2020 12:27:394DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 12:27:396DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 17:21:375MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 03/10/2020 17:22:016CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: 138515; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 04/10/2020 04:35:173No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 07/10/2020 02:54:314DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 07/10/2020 02:54:316DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 09/10/2020 07:39:205MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 09/10/2020 16:16:056CM-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;
Sun 11/10/2020 16:33:234DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 11/10/2020 16:33:236DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 14/10/2020 16:13:574DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 14/10/2020 16:13:576DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 14/10/2020 23:17:053No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:49:025Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:49:033SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:49:035Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

Also the graph I posted has appeared on an earlier post now.

I ran a diagnostic test and got the message that there were WiFi problems but did not tell me what they were or what to do next.

Also notice that this thread is headed up as SOLVED. How do I change that as very much not solved. Is that why anyone from Virgin has stopped responding?

Thanks for all your help

0 Kudos
Reply
Z92
  • 2.28K
  • 190
  • 357
Problem sorter
184 Views
Message 24 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

Can you also post the download and upload pages? 

0 Kudos
Reply
LindaRuth
  • 35
  • 0
  • 2
On our wavelength
177 Views
Message 25 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

Hello

Thanks for your response. 

Where will I find those figures in the network log? 

0 Kudos
Reply
Adduxi
  • 2.92K
  • 221
  • 623
Trouble shooter
168 Views
Message 26 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

They should be separate tabs, Downstream and Upstream?  Just reading the logs and you are getting T3 timeouts and Loss of Sync, so something is amiss with the circuit.  If we can see the Downstream and Upstream power levels we can comment further. 

0 Kudos
Reply
LindaRuth
  • 35
  • 0
  • 2
On our wavelength
154 Views
Message 27 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

Hello

This is the first of the downstream logs:

3.0 Downstream channels

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

51707500007.09999840.946209QAM2565
11387500007.50000040.946209QAM2561
21467500007.69999740.366287QAM2562
31547500007.69999740.366287QAM2563
41627500007.59999840.366287QAM2564
61787500007.09999840.366287QAM2566
71867500007.00000040.946209QAM2567
81947500007.00000040.366287QAM2568
92027500007.30000340.366287QAM2569
102107500007.40000240.946209QAM25610
112187500007.40000240.366287QAM25611
122267500007.30000340.946209QAM25612
132347500007.40000240.946209QAM25613
142427500007.30000340.946209QAM25614
152507500007.30000340.366287QAM25615
162587500007.50000040.946209QAM25616
172667500007.69999740.946209QAM25617
182747500007.90000240.946209QAM25618
192827500007.90000240.366287QAM25619
202907500007.80000340.946209QAM25620
212987500007.19999740.946209QAM25621
223067500006.69999740.946209QAM25622
233147500006.69999740.366287QAM25623
243227500007.09999840.946209QAM25624
253307500007.30000340.946209QAM25625
263707500007.19999740.366287QAM25626
273787500007.00000040.366287QAM25627
283867500006.59999840.946209QAM25628
293947500006.90000240.366287QAM25629
304027500007.09999840.366287QAM25630
314107500007.19999740.946209QAM25631

 

0 Kudos
Reply
LindaRuth
  • 35
  • 0
  • 2
On our wavelength
153 Views
Message 28 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

This is the second:

.0 Downstream channelsChannel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
5Locked000
1Locked6631288400
2Locked6588875200
3Locked6321126100
4Locked6652293000
6Locked6637743100
7Locked6333033500
8Locked6164937800
9Locked6468949100
10Locked6391307700
11Locked6112519000
12Locked6124336800
13Locked6474193700
14Locked6649291700
15Locked1885087300
16Locked1912311200
17Locked1941450200
18Locked1916572800
19Locked1879488000
20Locked1458802600
21Locked1859193500
22Locked1834326900
23Locked1968837700
24Locked2966409300
25Locked3144309500
26Locked3164911000
27Locked3387876600
28Locked3275620900
29Locked3303966600
30Locked3396266500
31Locked172408596600


3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159964K1880QAM4096759


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked 8.636024650470



0 Kudos
Reply
LindaRuth
  • 35
  • 0
  • 2
On our wavelength
150 Views
Message 29 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

And the upstream:

3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14620000042.5205995120 KSym/sec64QAM11
23260000042.5205995120 KSym/sec64QAM13
33940000042.5205995120 KSym/sec64QAM12
45370000043.0205995120 KSym/sec64QAM10


3.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_STDMA0040
2US_TYPE_STDMA0040
3US_TYPE_STDMA0040
4US_TYPE_STDMA0040

Everything has run very slowly today.
0 Kudos
Reply
LindaRuth
  • 35
  • 0
  • 2
On our wavelength
149 Views
Message 30 of 32
Flag for a moderator

Re: Intermittent connection with Amazon Alexa

And link for today's graph

https://www.thinkbroadband.com/broadband/monitoring/quality/share/e3d57531b3ecf19ea453e27314619da850c9c627-19-10-2020

 

0 Kudos
Reply