Cantrack TK100 online/offline and unknown status

Hello,
I add 3 devices tk100 from Cantrack and i have same issue for all of them.

• First day add devices works ok
• After some hours of no moving devices goes auto sleep and not communicate with server as i saw from logs, their imei not appearing at all
• then devices at traccar showed Grey with reason unknown status

Next day when the 3 cars start moving, then randomly devices goes offline/online every 2-3 seconds, stuck offline with ignition on, shows wrong gps position, all together wrong

When i remove devices and add them again from beginning then works ok for the first day, after the unknown status the next day when starting moving, again we start the same strange things....

Cantrack says me port 5013 and it works on this port, least the first day

Also, when devices added to Cantrack portal there works ok, ignition gps, online always and not going offline or unknown...

What's happening any clue? What i can test?

Sounds like a device issue. I'm not sure why it's under server.

Because to other platform works ok.
because of that im thinking maybe server / protocol issue with this model.

If you think it's a server issue, you have to provide some evidence of it. If you don't see anything in the logs, but you're convinced that device is sending something, then use Wireshark or something similar to capture the data.

Ok ill check what Wireshark is and how works , to try something else now, can i set somehow after how much time without sending something to mark devices unknown status and after how much time to mark them offline?

Check the configuration documentation.

I can't understand how to write it at xml, can you help me please?

i check the logs and i mention this happened often maybe,. device seems to disconnect after firebase failed. what is firebase notification? i dont add anything of this. the user tolds me he use also the chrome application. the imei: 867232055409099

2024-04-16 10:05:12  INFO: Event id: 867232055409099, time: 2024-04-16 10:05:10, type: geofenceEnter, notifications: 2
2024-04-16 10:05:12  INFO: [T9bfcced7] error - Failed to get notificator firebase - RuntimeException (NotificatorManager:75 < NotificationManager:127 < ... < *:124 < ... < *:123 < *:163 < BaseEventHandler:40 < ...)
2024-04-16 10:05:12  INFO: [T9bfcced7] disconnected
2024-04-16 10:05:12  INFO: Event id: 867232055409099, time: 2024-04-16 10:05:12, type: deviceOffline, notifications: 1
2024-04-16 10:05:14  INFO: [T6606b76a: h02 < 18.184.88.141] 2a48512c3836353230353033323730353232392c56312c3037303531332c412c333830312e31313030312c4e2c30323334332e35323634312c452c302e30302c33362c3136303432342c4646464646424646230d0a
2024-04-16 10:05:14  INFO: [T6606b76a] id: 865205032705229, time: 2024-04-16 10:05:13, lat: 38.01850, lon: 23.72544, course: 36.0
2024-04-16 10:05:14  INFO: [T6606b76a: h02 > 18.184.88.141] 2a48512c3836353230353033323730353232392c56342c56312c323032343034313630373035313423
2024-04-16 10:05:18  INFO: [T812c183e] connected
2024-04-16 10:05:18  INFO: [T812c183e: h02 < 18.184.88.141] 2a48512c3836373233323035353430393039392c4854425423
2024-04-16 10:05:18  INFO: [T812c183e: h02 > 18.184.88.141] 2a48512c3836373233323035353430393039392c4854425423
2024-04-16 10:05:23  INFO: [Tc3e91d09: h02 < 18.184.88.141] 2a48512c3836353230353033333130323731352c56312c3037303531342c412c343033352e34353730362c4e2c30323235382e33313438362c452c302e30302c3334392c3136303432342c4646464646424646230d0a
2024-04-16 10:05:23  INFO: [Tc3e91d09] id: 865205033102715, time: 2024-04-16 10:05:14, lat: 40.59095, lon: 22.97191, course: 349.0
2024-04-16 10:05:23  INFO: [Tc3e91d09: h02 > 18.184.88.141] 2a48512c3836353230353033333130323731352c56342c56312c323032343034313630373035323323
2024-04-16 10:05:24  INFO: [T83bb33e0: h02 < 18.158.164.113] 2a48512c3836353230353033313430383831372c56312c3037303832332c412c343033342e393834332c4e2c30323235382e393732302c452c302e30302c302c3136303432342c4646464646424646230d0a
2024-04-16 10:05:24  INFO: [T83bb33e0] id: 865205031408817, time: 2024-04-16 10:08:23, lat: 40.58307, lon: 22.98287, course: 0.0
2024-04-16 10:05:24  INFO: [T83bb33e0: h02 > 18.158.164.113] 2a48512c3836353230353033313430383831372c56342c56312c323032343034313630373035323423
2024-04-16 10:05:24  INFO: [T812c183e: h02 < 18.184.88.141] 2a48512c3836373233323035353430393039392c56312c3037303532342c412c333830342e36303238312c4e2c30323333362e37333136342c452c3030332e32342c3333302c3136303432342c464646464646464623
2024-04-16 10:05:24  INFO: Event id: 867232055409099, time: 2024-04-16 10:05:24, type: deviceOnline, notifications: 1
2024-04-16 10:05:25  INFO: Event id: 867232055409099, time: 2024-04-16 10:05:24, type: geofenceEnter, notifications: 2
2024-04-16 10:05:25  INFO: [T812c183e] error - Failed to get notificator firebase - RuntimeException (NotificatorManager:75 < NotificationManager:127 < ... < *:124 < ... < *:123 < *:163 < BaseEventHandler:40 < ...)
2024-04-16 10:05:25  INFO: [T812c183e] disconnected
2024-04-16 10:05:25  INFO: Event id: 867232055409099, time: 2024-04-16 10:05:25, type: deviceOffline, notifications: 1
2024-04-16 10:05:31  INFO: [T1ce3ca5f] connected

also i saw misc devices all day connected, its not mine. they trying to hack me something?

2024-04-16 09:27:47  INFO: [T01c85db4] connected
2024-04-16 09:27:50  INFO: [T01c85db4: pricol < 87.236.176.100] 300c020101600702010304008000
2024-04-16 09:27:53  INFO: [T01c85db4] disconnected
2024-04-16 09:27:57  INFO: [Tc3e91d09: h02 < 18.184.88.141] 2a48512c3836353230353033333130323731352c56312c3036323734382c412c343033352e34353730362c4e2c30323235382e33313438362c452c302e30302c3334392c3136303432342c4646464646424646230d0a
2024-04-16 09:27:58  INFO: [Tc3e91d09] id: 865205033102715, time: 2024-04-16 09:27:48, lat: 40.59095, lon: 22.97191, course: 349.0
2024-04-16 09:27:58  INFO: [Tc3e91d09: h02 > 18.184.88.141] 2a48512c3836353230353033333130323731352c56342c56312c323032343034313630363237353723
2024-04-16 09:28:04  INFO: [T83bb33e0: h02 < 18.158.164.113] 2a48512c3836353230353033313430383831372c56312c3036333130332c412c343033342e393738392c4e2c30323235382e393733352c452c302e30302c302c3136303432342c4646464646424646230d0a
2024-04-16 09:28:04  INFO: [T83bb33e0] id: 865205031408817, time: 2024-04-16 09:31:03, lat: 40.58298, lon: 22.98289, course: 0.0
2024-04-16 09:28:04  INFO: [T83bb33e0: h02 > 18.158.164.113] 2a48512c3836353230353033313430383831372c56342c56312c323032343034313630363238303423
2024-04-16 09:28:05  INFO: [Te4f5ce76] connected
2024-04-16 09:28:08  INFO: [Te4f5ce76: pricol < 87.236.176.82] 73746174730d0a
2024-04-16 09:28:11  INFO: [Te4f5ce76] disconnected
2024-04-16 09:28:18  INFO: [Tc3e91d09: h02 < 18.184.88.141] 2a48512c3836353230353033333130323731352c56312c3036323830382c412c343033352e34353730362c4e2c30323235382e33313438362c452c302e30302c3334392c3136303432342c4646464646424646230d0a
2024-04-16 09:28:18  INFO: [Tc3e91d09] id: 865205033102715, time: 2024-04-16 09:28:08, lat: 40.59095, lon: 22.97191, course: 349.0
2024-04-16 09:28:18  INFO: [Tc3e91d09: h02 > 18.184.88.141] 2a48512c3836353230353033333130323731352c56342c56312c323032343034313630363238313823
2024-04-16 09:28:23  INFO: [Tca7da5f8] connected
2024-04-16 09:28:24  INFO: [T83bb33e0: h02 < 18.158.164.113] 2a48512c3836353230353033313430383831372c56312c3036333132332c412c343033342e393738392c4e2c30323235382e393733352c452c302e30302c302c3136303432342c4646464646424646230d0a
2024-04-16 09:28:24  INFO: [T83bb33e0] id: 865205031408817, time: 2024-04-16 09:31:23, lat: 40.58298, lon: 22.98289, course: 0.0
2024-04-16 09:28:24  INFO: [T83bb33e0: h02 > 18.158.164.113] 2a48512c3836353230353033313430383831372c56342c56312c323032343034313630363238323423
2024-04-16 09:28:26  INFO: [Tca7da5f8: pricol < 87.236.176.91] 10c00b004c494f523c020000ffffffff00000200d1587355509195954997b6e611ea26c60789cd434c39118f44459078909ea0fc4ecade1d100300005a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5>
2024-04-16 09:28:26  WARN: Unknown device - À^K^@LIOR (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:26  WARN: Unknown device - ZZZZZZZ (87.236.176.91)
2024-04-16 09:28:29  INFO: [Tca7da5f8] disconnected\

and last, i saw at users list, created some users i didnt create. for example i have user name "alex" device name "ddd" with email "xxx@gmail.com" and imei "555"
and i suddenly just saw other user with user name "the device name" and email "xxx@gmail.com:imei of the device"

and i found and this for same device disconnection reason socket error

2024-04-16 09:43:02  INFO: [Tf39f380e] error - Connection reset - SocketException (...)
2024-04-16 09:43:02  INFO: [Tf39f380e] disconnected
2024-04-16 09:43:02  INFO: Event id: 867232055409099, time: 2024-04-16 09:43:02, type: deviceOffline, notifications: 1

firebase channel to notifications how can add it without configured at config file? i believe this cause all the situation and their devices disconnected after firebase error. but who add it to the notifications channel of the user the firebase option together with web and traccar? :/

You must have had it enabled in the past or maybe someone enabled it using the API directly without checking what's enabled.

the uknown devices are someone trying to hack or something?
with pricol portocol and some else, which not from my devices for sure.
they can do something harmfull? can secure the traccar server somehow?

This has been discussed several times previously. I recommend searching for more details.

I cant find anything, posts appeared for unknown devices spoke about legal devices of users which not registered.

About status timeout i understand that is about the unknown status which is by default 10 minutes and i can change it if i need from status.timeout at config file.

About server.timeout it's the Offline status? What is the default time for status offline?

And the web.timeout what is about? About websocket timeout? What is websocket practical?

Thanks in advance