Only Heartbeat without Position

After a days or weeks sometimes some of devices stop sending the gps signal and sends only hearybeat. Trying to restart the devices but not helped, only restart the traccar server resolve the issue and devices showing the position again.

While no position received, at logs i receive only this for the specific devices which has stuck (other devices of same protocol usually sends position ok, i mean its not generally at all devices) :

09:51:07  *HQ,867232055405949,HTBT#
09:53:06  *HQ,867232055405949,HTBT#
09:55:07  *HQ,867232055405949,HTBT#
09:57:07  *HQ,867232055405949,HTBT#

Any thoughts what maybe is the problem?

Traccar Version its the latest, the same issue was and to previous 3 versions by the way as i remember it

Seems like a device issue to me. Do you have proper full log fragment with before and after restart?

But its not only to this device, it happens randomly and to other devices. Also if restart the device the issue not fixed, only traccar service restart fixs the issue and starts to appear position in logs again.

What exactly logs needs?

Log fragment showing it's stuck first and then recovers after Traccar restart.

Hi Anton,

I found more details in the logs for IMEI 867232055405949, and there is an important point that may help.

Before the restart, the device was stuck sending only heartbeat messages:

2026-08-13 10:07:06 INFO: [T239134db: h02 < 18.198.73.229] *HQ,867232055405949,HTBT#
2026-08-13 10:09:07 INFO: [T239134db: h02 < 18.198.73.229] *HQ,867232055405949,HTBT#
2026-08-13 10:11:07 INFO: [T239134db: h02 < 18.198.73.229] *HQ,867232055405949,HTBT#
...
2026-08-13 10:19:07 INFO: [T239134db: h02 < 18.198.73.229] *HQ,867232055405949,HTBT#

At around 10:21 I restarted the GPS device itself. The device then established a new connection and its IP changed from 18.198.73.229 to 3.72.206.109:

2026-08-13 10:21:07 INFO: [Te5a988a0: h02 < 3.72.206.109] *HQ,867232055405949,HTBT#
2026-08-13 10:21:17 INFO: [Te5a988a0: h02 < 3.72.206.109] *HQ,867232055405949,HTBT#
2026-08-13 10:21:36 INFO: [Te5a988a0: h02 < 3.72.206.109] *HQ,867232055405949,HTBT#

So restarting the GPS device and getting a completely new connection/IP did NOT make it send a position. It continued sending only HTBT.

I then restarted the Traccar server. The system journal confirms:

Aug 13 10:21:39 traccar systemd[1]: Stopping traccar ...
Aug 13 10:23:09 traccar systemd[1]: Stopped traccar.
Aug 13 10:23:09 traccar systemd[1]: Started traccar.

After the Traccar restart, the device still sent heartbeats for some time. The first position message I can find afterwards is at 11:01:54:

2026-08-13 11:01:54 INFO: [T8f18f76a: h02 < 3.72.206.109] *HQ,867232055405949,V1,080153,V,3805.499,N,02343.2117,E,000.00,000,130826,FFFFFFFF#
2026-08-13 11:01:54 INFO: [T8f18f76a: h02 > 3.72.206.109] *HQ,867232055405949,V4,V1,20260813110154#
2026-08-13 11:01:58 INFO: [T8f18f76a] id: 867232055405949, time: 2026-08-13 11:01:54, lat: 38.09158, lon: 23.72018, course: 0.0

After that, normal position messages continued:

2026-08-13 11:07:56 ... V1 ...
2026-08-13 11:08:25 ... V1 ...
2026-08-13 11:08:55 ... V1 ...
2026-08-13 11:09:25 ... V1 ...

So the sequence appears to be:

1. Device sends only HTBT.
2. I restart the GPS device itself → new IP/new H02 connection, but it still sends only HTBT.
3. I restart Traccar.
4. Some time later, the device starts sending V1 position messages again.

This makes me think the problem is not simply the GPS device or its cellular connection, because restarting the device and establishing a new connection did not immediately restore position reporting.

I hope this log fragment helps.

No, I want to see the whole continuous fragment.

For this IMEI you want or to send whole log file for the specific day?

I don't need the whole day, but I need a continuous fragment without editing in between.

ok, sended raw data via email for safety. thank you

I checked your logs and I am 99% sure it's just a device issue because:

1. Other devices are sending data just fine.
2. This device continues sending only heartbeats for almost 40 minutes after restart, which I think invalidates your point about restart fixing the issue.

It sends after 40 minutes because after 40 minutes moved.
But already tried previous times only to restart device and when moved not sending anything.
Im 100% sure that resolved only with traccar service restart, can this trigger something to the device to start sending again?

Also to mention, this happens suddenly to different devices, different every time.

It sends after 40 minutes because after 40 minutes moved.

Then why are you expecting it to be sending before restart? This test makes absolutely no sense to me. I think the next steps are obvious - you keep the device in motion the whole time and show us that it doesn't send before restart and starts sending immediately after restart.

Because was with no sending from previous day while the car already moves....because of that i waiting to send before traccar restart but never happens until next day restart traccar and device sends when moves again.

So far you have not provided any clear evidence that would show that server restart did anything.