The device is not handling the server responses correctly and seems to ignore the 4 second message (it does arrive [2020-05-18 14:39:18] Response: Interval: 4), it then starts the binary search and sends an interval for 2 and 3 at the same time:
[2020-05-18 14:39:18] "interval": 2
[2020-05-18 14:39:18] "interval": 3
It then settles for 4 seconds result [2020-05-18 14:39:21] Keep-alive time set at: 4 seconds
Server logs
[e4441a67-11f4-4e20-874e-8c9d6303bc09] UDP Message received from 193.181.245.211:51210: interval 1
[e4441a67-11f4-4e20-874e-8c9d6303bc09] UDP Packet sent to 193.181.245.211:51210. Interval: 1.
[f3baf466-e68d-4960-9e72-1d420b9ca1b7] UDP Message received from 193.181.245.211:51210: interval 4
[f3baf466-e68d-4960-9e72-1d420b9ca1b7] UDP Packet sent to 193.181.245.211:51210. Interval: 4.
[d8618508-978b-4c2c-bdd0-2f04ec5c9383] UDP Message received from 193.181.245.211:51210: interval 2
[85d3c5f1-7656-463c-a1ae-8661927502af] UDP Message received from 193.181.245.211:51210: interval 3
[d8618508-978b-4c2c-bdd0-2f04ec5c9383] UDP Packet sent to 193.181.245.211:51210. Interval: 2.
[85d3c5f1-7656-463c-a1ae-8661927502af] UDP Packet sent to 193.181.245.211:51210. Interval: 3.
[85d3c5f1-7656-463c-a1ae-8661927502af] UDP connection to 193.181.245.211:51210 timed out. Connection terminated. Interval: 3.
The device is not handling the server responses correctly and seems to ignore the 4 second message (it does arrive
[2020-05-18 14:39:18] Response: Interval: 4
), it then starts the binary search and sends an interval for 2 and 3 at the same time:[2020-05-18 14:39:18] "interval": 2
[2020-05-18 14:39:18] "interval": 3
It then settles for 4 seconds result
[2020-05-18 14:39:21] Keep-alive time set at: 4 seconds
Server logs
Device logs