Traccar Logs - Not recognizing TK119 Trackers anymore

I am running 4.0 as a Docker (https://hub.docker.com/r/traccar/traccar/) on a Synology NAS and have been getting strange messages in the logs, whose HEX messages can't be decoded (There are also a large number of connected/disconnected messages):

2018-10-30 15:16:42  INFO: [f55f3e4a] connected
2018-10-30 15:16:42 DEBUG: [f55f3e4a: 5064 < 172.17.0.1] HEX: 676701000c02c40352544073223654012c
2018-10-30 15:16:42 DEBUG: [f55f3e4a: 5064 > 172.17.0.1] HEX: 676701000202c4
2018-10-30 15:16:42  WARN: Unknown device - 352544073223654 (172.17.0.1)
2018-10-30 15:16:44 DEBUG: [f55f3e4a: 5064 < 172.17.0.1] HEX: 676712002d02c55bd7db1403fc0178bb0f8ee4f20101006100310901f90002825b0909b9650b006f11da05b9000000645d7f
2018-10-30 15:16:44 DEBUG: [f55f3e4a: 5064 > 172.17.0.1] HEX: 676712000202c5
2018-10-30 15:20:58  INFO: [28a54dbe] disconnected
2018-10-30 15:23:30  INFO: [124923d5] connected
2018-10-30 15:23:31 DEBUG: [124923d5: 5064 < 172.17.0.1] HEX: 676701000c02cf0352544073223654012c
2018-10-30 15:23:31 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676701000202cf
2018-10-30 15:23:31  WARN: Unknown device - 352544073223654 (172.17.0.1)
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 < 172.17.0.1] HEX: 676712002d02d05bd7dbe603fc022f990f8fe96a00d30038004f0901f90002825b0909b9650b006f11da05b1000000646ebe676712002d02d15bd7dc0403fc02301c0f900f9b00d2002e00580901f90002825b0909b9650b006f11d605860000006470a1676712002d02d25bd7dc1403fc022fa80f90164100d5001900940901f90002825b0909b9650b006f11da05a50000006470fd676712002d02d35bd7dc2203fc02259d0f901e9700d9003a00900901f90002825b0909b9650b006f11d205960000006471b5676712002d02d45bd7dc3a03fc0217050f9035f000e1003800660901f90002825b0909b9650b006f11d105ab000000647336676712002d02d55bd7dc4003fc0216c70f903da200e3003900580901f90002825b0909b9650b006f11d505a9000000647397676712002d02d65bd7dc5e03fc0216cb0f906beb00eb004c005a0901f90002825b0909b9650b006f11da05a80000006475db676712002202d75bd7dc7c01fc0216d20f90a22800e8005a005a09006f11d605a4000000647885676712002d02d85bd7dc9a03fc020ab50f90d58400f20051007f0901f90001d850013c804214006f11d9059c000000647b46676712002202d95bd7dcb801fc01fd4f0f910303010e0045007309006f11d5059d000000647db4
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d0
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d1
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d2
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d3
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d4
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d5
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d6
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d7
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d8
2018-10-30 15:23:32 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202d9
2018-10-30 15:23:51 DEBUG: [124923d5: 5064 < 172.17.0.1] HEX: 676712002d02da5bd7dcd603fc01e5d10f912c8f013d004e00620801f90002825b0909b9650c006f11b8059a00000064803d
2018-10-30 15:23:51 DEBUG: [124923d5: 5064 > 172.17.0.1] HEX: 676712000202da
2018-10-30 15:26:28  INFO: [06ea2f21] disconnected

I know port 5064 is correct (TK119-3G) which has worked for a long time.

I will try 4.1 tonight.

Regards,

Alby

Which messages are strange and what's strange about them?

You can ignore this post. I wasn't able to decode any of the messages and with 4.1 it simply started working. Sorry about that