Nest thermostat high ping time

[fluffylittlemarshmallow]

Hi,

I'm struggling to get my nest thermostat to talk to the cloud, it is reporting ping time of 2500MS

I've followed the nest guide to improving WiFi. First I had to change the SSID so that it only picks up the 2.4ghz band. But I am still seeing nest report stupid high ping times. 

I've restarted everything, and checked on service status. I've moved it away from any potential interference

Signal strength 71 (out of 100), ping 2346ms (over 1500 is apparently a problem) 

So I put it on a hotspot to my phone, over 4g and I get ping times reported between 800ms and 1200ms (which is apparently good for nest) 

My broadband is 70mb, normally 36ms (Amsterdam) pings. 

Any ideas on how to fix this? 

[Michelle-TalkTalk]

Morning,

Thanks for the update 🙂

Thanks

[fluffylittlemarshmallow]

10hrs after posting this, my thermostat is working and I can play games again 😄 yay! 

(I assume that someone unblocked something or fixed a routing table somewhere, thanks!)

[fluffylittlemarshmallow]

So I dug a little deeper (raspberry pi, bridged network, wireshark) and found that the thermostat talks to a few different up addresses. All TCP.

35.190.54.210

35.169.85.41

103.99.150.43

54.81.179.208

On WiFi that last one (54.81.179.208) is unreachable. On 4g Vodafone it's excellent ping times. 

And on WiFi I get connection refused for 103.99.150.43, but it works on 4g

     

 

traceroute to 103.99.150.43 (103.99.150.43), 30 hops max
Hop 1:    From ttrouter (192.168.1.1), 25 ms
Hop 2:    From 78.144.1.7, 35 ms
Hop 3:    From 78.144.1.6, 34 ms
Hop 4:    From 195.66.224.177, 49 ms
Hop 5:    From 202.84.178.70, 179 ms
Hop 6:    From 202.84.141.229, 181 ms
Hop 7:    From 202.40.148.97, 177 ms
Hop 8:    From 202.84.136.1, 361 ms
Hop 9:    From 202.84.136.1, 289 ms
Hop 10:    From 202.84.224.197, 280 ms
Hop 11:    From 202.127.73.102, 269 ms
Hop 12:    From 116.119.36.242, 330 ms
Hop 13:    From 182.79.20.74, 411 ms
Hop 14:    From 103.99.150.43, 354 ms
Traceroute complete: 14 hops, time: 25593 ms

traceroute to 35.169.85.41 (35.169.85.41), 30 hops max
Hop 1:    From ttrouter (192.168.1.1), 32 ms
Hop 2:    From 78.144.1.7, 34 ms
Hop 3:    From 78.144.1.6, 47 ms
Hop 4:    From 94.31.30.189, 38 ms
Hop 5:    *
Hop 6:    *
Hop 7:    From 64.125.25.57, 106 ms
Hop 8:    From 99.82.183.64, 118 ms
Hop 9:    *
Hop 10:    *
Hop 11:    *
Hop 12:    *
Hop 13:    *
Hop 14:    *
Hop 15:    *
Hop 16:    From 52.93.28.246, 206 ms
Hop 17:    *
Hop 18:    *
Hop 19:    *
Hop 20:    *
Hop 21:    *
Hop 22:    *
Hop 23:    *
Hop 24:    *
Hop 25:    *
Hop 26:    *
Hop 27:    *
Hop 28:    *
Hop 29:    *
Hop 30:    *
Traceroute complete: 30 hops, time: 151234 ms

[fluffylittlemarshmallow]

I would be happy to do that and see if it helps. Before I try a new router, perhaps I should do a factory reset on my current one, can I just do that? 

(And apparently this might also force a new IPADDRESS) 

[Michelle-TalkTalk]

Morning,

Ok, would you like us to send a replacement router for testing purposes to rule this out?

Thanks

[fluffylittlemarshmallow]

Just checked the attic, and I haven't got any old routers anymore 😞 

[Chris-TalkTalk]

Hi fluffylittlemarshmallow,

Do you have access to another router that you can test with?

Chris

[KeithFrench]

I'll ask TalkTalk to get their networks team involved, but they may also request to see a traceroute as well.

[fluffylittlemarshmallow]

so i am still struggling to figure out what the thermostat talks to, and what I should traceroute to. 

however my problems have expanded. 

• google stadia (wired ethernet connection to router) fails to connect to games, but works fine on 4g vodafone network
• this speed test fails to complete on talktalk, but fine on 4g -  https://projectstream.google.com/speedtest  

m=p8L0ob,qtq9Td,i5dxUd,m9oV,RAnnUd,Ru0Pgb,uu7UOe,ygtL7b,soHxf:385 WebSocket connection to 'wss://ndt-iupui-mlab3-dub01.mlab-oti.measurement-lab.org:3010/ndt_protocol' failed: WebSocket is closed before the connection is established.​

• (ping and traceroute are fine to ndt-iupui-mlab3-dub01.mlab-oti.measurement-lab.org)
• this speed test is fine. https://speed.measurementlab.net/#/

[fluffylittlemarshmallow]

good idea, traceroute seems like the best next step, I just need to find out what server the next is trying to talk to. 

router info : 
- TalkTalk Sagemcom FAST 5364 
- Hardware Version FAST5364 3.00
- Software Version SG4K100130
- GUI Version 5.6.1

[KeithFrench]

Before I can answer that I would need to know which make/model of router that you have. I cannot see that changing the Beacon Interval will have any effect on this.

If you are getting a poor ping into the cloud, a traceroute would be much more useful as it would show where th problem was.

[fluffylittlemarshmallow]

I'd like to experiment with some of these settings if possible - is there a way to do this?

• DTIM: 3
  Beacon Interval: 211
  Enable WMM APSD: Enable
  
  https://web.archive.org/web/20181121074752/http://blog.waldrondigital.com/2014/10/23/fixing-nest-the...

[KeithFrench]

Thanks, what about a traceroute to the address in the cloud?

[fluffylittlemarshmallow]

Hi, 

i'm pretty sure it's not that 😞  3ms ping. 

VERINT+mjohnston@VSPF1X01VG /usr/bin
$ ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 6ms, Average = 3ms

[KeithFrench]

HI @fluffylittlemarshmallow 

@Michelle-TalkTalk has asked me to help you. What are the ping responses like if you ping the router?

[Michelle-TalkTalk]

Morning,

@KeithFrench - Is this something that you would be able to provide advice on please?

Thanks