Can TRACCAR become "dizzy"?

I have pet trackers (port 5015) that after some 3 minutes of no motion, they enter a semi sleep state, and only send GPS coordinates to server again if it senses motion. If that happens, it goes back to state 1. If it does not, after 1 hour it turns off.
The issue I am having is that after many stops with no motion (4 or more; with first stops it keeps working ok), all well below the 1 hour limit, traccar stops showing its coordinates. Log shows a change in that situation. Is it anyhow possible that TRACCAR gets "dizzy" with too many disconnections and reconnections?
Here are below the logs with the device working ok (first log), and then (second log) when it dissapears from Traccar:

Following are some logs when trackers were working perfectly..

2025-05-12 10:17:28  INFO: [Tcb9a2389: huabao > 201.219.236.154] 7e8001000501917536202400000077020000267e
2025-05-12 10:17:31  INFO: [T285d7f5e] disconnected
2025-05-12 10:18:11  INFO: [T82d40912] disconnected
2025-05-12 10:18:11  INFO: Event id: 019175362528, time: 2025-05-12 10:18:11, type: deviceOffline, notifications: 0
2025-05-12 10:18:13  INFO: [Tcb9a2389: huabao < 201.219.236.154] 7e0200002b0191753620240078000000000000000e01fcc8aa04347f0a03590000010325051217181101040000000030011c310110e10158967e
2025-05-12 10:18:13  INFO: [Tcb9a2389] id: 019175362024, time: 2025-05-12 02:18:11, lat: -33.34366, lon: -70.54926, course: 259.0
2025-05-12 10:18:13  INFO: [Tcb9a2389: huabao > 201.219.236.154] 7e8001000501917536202400000078020000297e
2025-05-12 10:18:17  INFO: [T7daf8e2d] connected
2025-05-12 10:18:17  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0102000c0191753625280075303139313735333632353238a77e
2025-05-12 10:18:17  INFO: Event id: 019175362528, time: 2025-05-12 10:18:17, type: deviceOnline, notifications: 0
2025-05-12 10:18:17  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e80010005019175362528000000750102002c7e
2025-05-12 10:18:21  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0200002b0191753625280072000000000000000e01fcc88f04347f20035b0000010525051301172401040000000030011731010ee10154aa7e
2025-05-12 10:18:21  INFO: [T7daf8e2d] id: 019175362528, time: 2025-05-12 10:17:24, lat: -33.34363, lon: -70.54928, course: 261.0
2025-05-12 10:18:21  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e80010005019175362528000000720200002a7e
2025-05-12 10:18:23  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0200002b0191753625280073000000000000000e01fcc88f04347f20035b0000010525051301174401040000000030011731010fe10154ca7e
2025-05-12 10:18:23  INFO: [T7daf8e2d] id: 019175362528, time: 2025-05-12 10:17:44, lat: -33.34363, lon: -70.54928, course: 261.0
2025-05-12 10:18:23  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e80010005019175362528000000730200002b7e
2025-05-12 10:18:25  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0200002b0191753625280074000000000000000e01fcc88f04347f20035b0000010525051301180401040000000030011731010fe10154827e
2025-05-12 10:18:25  INFO: [T7daf8e2d] id: 019175362528, time: 2025-05-12 10:18:04, lat: -33.34363, lon: -70.54928, course: 261.0
2025-05-12 10:18:25  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e80010005019175362528000000740200002c7e
2025-05-12 10:18:27  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0200002b0191753625280076000000000000000e01fcc88f04347f20035b0000010525051301182501040000000030011631010fe10154a07e
2025-05-12 10:18:27  INFO: [T7daf8e2d] id: 019175362528, time: 2025-05-12 10:18:25, lat: -33.34363, lon: -70.54928, course: 261.0
2025-05-12 10:18:27  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e80010005019175362528000000760200002e7e
2025-05-12 10:18:47  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0200002b0191753625280077000000000000000e01fcc88f04347f20035b0000010525051301184501040000000030011631010ee10154c07e
2025-05-12 10:18:47  INFO: [T7daf8e2d] id: 019175362528, time: 2025-05-12 10:18:45, lat: -33.34363, lon: -70.54928, course: 261.0
2025-05-12 10:18:47  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e80010005019175362528000000770200002f7e
2025-05-12 10:18:57  INFO: [Tcb9a2389: huabao < 201.219.236.154] 7e0200002b0191753620240079000000000000000e01fcc8aa04347f0a035900000103250512171857010400000000300113310110e10158de7e
2025-05-12 10:18:57  INFO: [Tcb9a2389] id: 019175362024, time: 2025-05-12 02:18:57, lat: -33.34366, lon: -70.54926, course: 259.0
2025-05-12 10:18:57  INFO: [Tcb9a2389: huabao > 201.219.236.154] 7e8001000501917536202400000079020000287e
2025-05-12 10:19:07  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0200002b0191753625280078000000000000000e01fcc88f04347f20035b0000010525051301190501040000000030011631010fe101548f7e
2025-05-12 10:19:07  INFO: [T7daf8e2d] id: 019175362528, time: 2025-05-12 10:19:05, lat: -33.34363, lon: -70.54928, course: 261.0
2025-05-12 10:19:07  INFO: [T7daf8e2d: huabao > 3.123.77.132] 7e8001000501917536252800000078020000207e
2025-05-12 10:19:22  INFO: [T8f07f2b7] connected


2025-05-12 10:19:26  INFO: [T8f07f2b7] disconnected
2025-05-12 10:19:51  INFO: [Tcb9a2389: huabao < 201.219.236.154] 7e0fa00008019175362024007a00000000076f5500377e
2025-05-12 10:20:29  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0fa00008019175362528007900000000061d51004a7e
2025-05-12 10:23:50  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0fa0000801917536252800950000000006f25100497e
2025-05-12 10:24:52  INFO: [Tcb9a2389: huabao < 201.219.236.154] 7e0fa00008019175362024009b00000000079555002c7e
2025-05-12 10:27:11  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0fa00008019175362528009d0000000006f25100417e
2025-05-12 10:29:52  INFO: [Tcb9a2389: huabao < 201.219.236.154] 7e0fa0000801917536202400a10000000007955400177e
2025-05-12 10:30:32  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0fa0000801917536252800a70000000006f251007b7e
2025-05-12 10:33:53  INFO: [T7daf8e2d: huabao < 3.123.77.132] 7e0fa0000801917536252800c20000000006f250001f7e
2025-05-12 10:34:52  INFO: [Tcb9a2389: huabao < 201.219.236.154] 7e0fa0000801917536202400c50000000008035400ea7e

Seems like your device stops sending coordinates. That's why server stops showing them.

OK, thanks. Knowing this I think I guess where I should point now. Thanks again.