Arlo Pro 5 Ping latency

[GG4ever]

I have noticed my Arlo Pro 5 drop connection frequently and caused battery drained , I have tried doing a ping test and found that its latenency will continue to have serveral ms constantly increasing to nearly 1000 then it will reset.

I can reproduce it even I put the Arlo Pro 5 next to my router.

Version : 1.040.28.17_15_ac8359b

[jguerdat]

Use the app to go to Settings, Support and select your camera. Scroll down to Contacts to see what official support may offer, including an RMA.

[StephenB]

---

@GG4ever  wrote:

I have tried doing a ping test and found that its latency will continue to have serveral ms constantly increasing to nearly 1000 then it will reset.

---

The camera is usually in a low-power state - and when that is the case, it does not respond quickly to ping. 

I see this on my first set of pings:

Pinging 10.0.0.112 with 32 bytes of data:
Reply from 10.0.0.112: bytes=32 time=724ms TTL=64
Reply from 10.0.0.112: bytes=32 time=709ms TTL=64
Reply from 10.0.0.112: bytes=32 time=689ms TTL=64
Reply from 10.0.0.112: bytes=32 time=681ms TTL=64

That first set of pings will wake the camera up, and the ping times will go down. This is what I see a few seconds after the first test:

Pinging 10.0.0.112 with 32 bytes of data:
Reply from 10.0.0.112: bytes=32 time=93ms TTL=64
Reply from 10.0.0.112: bytes=32 time=77ms TTL=64
Reply from 10.0.0.112: bytes=32 time=68ms TTL=64
Reply from 10.0.0.112: bytes=32 time=49ms TTL=64

If your ping times are similar, then that behavior is normal (although obviously the disconnects are not).

[GG4ever]

回覆自 192.168.1.253: 位元組=32 時間=718ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=741ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=750ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=768ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=787ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=807ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=818ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=837ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=851ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=860ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=880ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=897ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=904ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=916ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=932ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=952ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=959ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=980ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=988ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=1002ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=11ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=22ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=39ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=50ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=63ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=76ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=94ms TTL=64
回覆自 192.168.1.253: 位元組=32 時間=114ms TTL=64

My ping test differs from yours, the latency fluctuates between 10ms and 1000ms repeatedly

[StephenB]

---

@GG4ever wrote:

My ping test differs from yours, the latency fluctuates between 10ms and 1000ms repeatedly

---

I just re-ran mine with a longer count, and got different results.  There are short bursts (sometimes 20 packets or so) when the camera responds quickly, but then it lags again. 

I am not seeing a gradual ramp up like your sample.  Here's a sample from the end of the test I just did:

Reply from 10.0.0.112: bytes=32 time=1207ms TTL=64
Reply from 10.0.0.112: bytes=32 time=2ms TTL=64
Reply from 10.0.0.112: bytes=32 time=972ms TTL=64
Reply from 10.0.0.112: bytes=32 time=958ms TTL=64
Reply from 10.0.0.112: bytes=32 time=940ms TTL=64
Reply from 10.0.0.112: bytes=32 time=931ms TTL=64
Reply from 10.0.0.112: bytes=32 time=916ms TTL=64
Reply from 10.0.0.112: bytes=32 time=907ms TTL=64
Reply from 10.0.0.112: bytes=32 time=893ms TTL=64
Reply from 10.0.0.112: bytes=32 time=868ms TTL=64
Reply from 10.0.0.112: bytes=32 time=855ms TTL=64
Reply from 10.0.0.112: bytes=32 time=844ms TTL=64
Reply from 10.0.0.112: bytes=32 time=831ms TTL=64
Reply from 10.0.0.112: bytes=32 time=820ms TTL=64
Reply from 10.0.0.112: bytes=32 time=804ms TTL=64
Reply from 10.0.0.112: bytes=32 time=792ms TTL=64
Reply from 10.0.0.112: bytes=32 time=782ms TTL=64
Reply from 10.0.0.112: bytes=32 time=771ms TTL=64
Reply from 10.0.0.112: bytes=32 time=756ms TTL=64
Reply from 10.0.0.112: bytes=32 time=743ms TTL=64
Reply from 10.0.0.112: bytes=32 time=730ms TTL=64
Reply from 10.0.0.112: bytes=32 time=717ms TTL=64
Reply from 10.0.0.112: bytes=32 time=708ms TTL=64
Reply from 10.0.0.112: bytes=32 time=706ms TTL=64
Reply from 10.0.0.112: bytes=32 time=685ms TTL=64
Reply from 10.0.0.112: bytes=32 time=668ms TTL=64
Reply from 10.0.0.112: bytes=32 time=655ms TTL=64
Reply from 10.0.0.112: bytes=32 time=636ms TTL=64
Reply from 10.0.0.112: bytes=32 time=620ms TTL=64
Reply from 10.0.0.112: bytes=32 time=599ms TTL=64
Reply from 10.0.0.112: bytes=32 time=586ms TTL=64
Reply from 10.0.0.112: bytes=32 time=575ms TTL=64
Reply from 10.0.0.112: bytes=32 time=563ms TTL=64
Reply from 10.0.0.112: bytes=32 time=550ms TTL=64
Reply from 10.0.0.112: bytes=32 time=537ms TTL=64
Reply from 10.0.0.112: bytes=32 time=525ms TTL=64
Reply from 10.0.0.112: bytes=32 time=510ms TTL=64
Reply from 10.0.0.112: bytes=32 time=499ms TTL=64
Reply from 10.0.0.112: bytes=32 time=481ms TTL=64
Reply from 10.0.0.112: bytes=32 time=463ms TTL=64
Reply from 10.0.0.112: bytes=32 time=444ms TTL=64
Reply from 10.0.0.112: bytes=32 time=434ms TTL=64
Reply from 10.0.0.112: bytes=32 time=421ms TTL=64

Ping statistics for 10.0.0.112:
    Packets: Sent = 200, Received = 200, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 1207ms, Average = 541ms

Do you always see a gradual ramp?  Have you tried testing with a different PC?

I am still not convinced that the ping response is giving useful info on what is wrong.  I don't have have your disconnect issue, and my ping times are also long.  So I still think the ping response is sluggish due to the power management being done by the camera.

Have you measured the wifi speed at the camera location with your phone?  I suggest using the Ookla speedtest app for that - turning off mobile data, in order to make sure you are testing the wifi speed.