13-09-2020 08:05 - edited 13-09-2020 08:05
Hi all
We’re on the Gig1 service just outside of Bracknell. Status says no issues in the area.
Woke up to an inbox full of messages from nest telling me our cameras had gone offline around 6 times through the night.
Logging into the hub 4 I see ‘DS scanning’ with the following network log.
Does anyone have any ideas what’s wrong? I’m pretty clueless about this side of things.
Thank you!
Sun 13/09/2020 06:32:46 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:32:47 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:33:32 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:33:32 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:34:17 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:34:17 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:35:00 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:35:00 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:35:42 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:35:42 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:36:25 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:36:26 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:37:12 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 13/09/2020 06:37:12 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Answered! Go to Answer
on 18-09-2020 10:33
Hi subsy,
Thanks for posting here.
I'm sorry you've had some problems with the connection dropping our over night.
I've had a look at your services from here, and I'm not able to see any issues. Your power levels are all looking within specification.
Have you continued to have problems since posting?
Have you made sure all connections are tight and secure? Have you noticed any other devices dropping the connection?
Thanks
Melissa
on 18-09-2020 19:03
Hi Melissa
Thank you in the end it turned out to be a service issue. It was restored later in the day. Been good since. Thanks!
on 18-09-2020 10:33
Hi subsy,
Thanks for posting here.
I'm sorry you've had some problems with the connection dropping our over night.
I've had a look at your services from here, and I'm not able to see any issues. Your power levels are all looking within specification.
Have you continued to have problems since posting?
Have you made sure all connections are tight and secure? Have you noticed any other devices dropping the connection?
Thanks
Melissa
on 18-09-2020 19:03
Hi Melissa
Thank you in the end it turned out to be a service issue. It was restored later in the day. Been good since. Thanks!
on 23-09-2020 19:50
Glad to hear it's all sorted now.
Please do let us know if you have any further concerns
Thanks.