Ignition Event and Duplicate Message Problems in Traccar 5.9 and 5.8

Hello Traccar Community,

I am encountering some issues with Traccar versions 5.9 and 5.8. I hope someone can help me troubleshoot and resolve these problems.

1. Ignition Event:

   • Traccar continues to create events for "ignition On" when the ignition is indeed On, but it stops creating events for "ignition Off" when the ignition is Off.
   • Furthermore, the "ignition Off" events are not being stored in the report.
   • Oddly, when the ignition is On, it displays "ignition Off" in the states.

2. Duplicate Messages:

   • On certain events, Traccar generates two messages for the same event.

I would greatly appreciate any guidance, suggestions, or solutions from the community to help me address these problems and ensure the accurate recording of ignition events and prevent duplicate messages.

Thank you in advance for your assistance.

Best regards,

Do you think it would help if you actually tell which device, protocol you use and the hex examples from traccar log for anyone to give you good advice?

Oddly, when the ignition is On, it displays "ignition Off" in the states. what happens if you refresh the page?

Have you checked timestamps for locations? Maybe there's some issue with ordering data.

CHECK REPORT: https://docs.google.com/spreadsheets/d/1Cw2q_IaEvYfXJEF35AD4VQXlJ64ZpweM/edit?usp=sharing&ouid=105274510182965672674&rtpof=true&sd=true

I'm facing this issue with two different protocols, H02 and GT06, and I don't believe it's a protocol error.

Traccar does not send any notifications for the continuous 'ignition on' events shown in the report.

Log

2023-10-07 08:38:37  INFO: [T3ef0db9b: gt06 < 223.123.111.230] 78780a130506040002000691b80d0a
2023-10-07 08:38:37  INFO: [T3ef0db9b] id: 358735077704913, time: 2023-10-07 08:12:35, lat: 24.90893, lon: 67.07779, course: 332.0
2023-10-07 08:38:37  INFO: [T3ef0db9b: gt06 > 223.123.111.230] 7878051300069d4e0d0a
2023-10-07 08:43:25  INFO: [T3ef0db9b: gt06 < 223.123.111.230] 78780a130506040002000780310d0a
2023-10-07 08:43:25  INFO: [T3ef0db9b] id: 358735077704913, time: 2023-10-07 08:12:35, lat: 24.90893, lon: 67.07779, course: 332.0
2023-10-07 08:43:25  INFO: [T3ef0db9b: gt06 > 223.123.111.230] 7878051300078cc70d0a

I have seen similar behavior when there is an issue with the notificationToken of the user/account.

Check if there any error in the log each time this ignitionOn event is generated.

This behavior was noticed when a external application other than official Traccr web was managing the user object, and did not follow the format for storing notificationTokens. So everytime Traccar tried to send a notification this would happen. (this maybe not your case, but no harm in ruling it out)

Maybe you can share additional information such as.

1. Are you using official version of Traccar and its Web APP
2. Are you manually editing any thing within the database,
3. Are there any errors in the log the same time these events are generated

I'm using the official 5.9 version of Traccar, and I haven't made any custom changes. In the logs, they don't show any errors

So then that is ruled out.

I hope someone else in the community is able to help you then.

I would suggest perform some basic troubleshooting and provide that and any relevant information to the community such that it enables them to guide you.

Note: Your log snapshot is 5 minutes apart heartbeat packets.

I do have the same issue and i notice that it appears randomly with some devices that are shared with multiple accounts and the moment i remove the share it start working again
Please let me know if you find a solution
Thank you

Just like that I am also experiencing this issue randomly with some devices. No, no solution yet.

Hello Traccar Community,

I wanted to bring to your attention an issue I've encountered with the Traccar system. After a complete server reinstallation and the addition of vehicles, I've noticed that the ignition status update seems to be inconsistent for some devices. This problem occurs randomly, affecting certain devices while others continue to function properly.

I've carefully checked the configurations, conducted compatibility testing, and ensured that the devices are correctly set up and updated. Despite these efforts, the issue persists, leading me to believe that there might be a bug within the Traccar system.

It's worth noting that my server currently supports over 300 active vehicles, and this issue is impacting the efficiency of our operations.

I would greatly appreciate any insights, suggestions, or experiences you might have had with a similar issue. Your expertise and guidance would be immensely helpful in resolving this matter.

Thank you in advance for any assistance you can provide.

Best regards,

@Graham, you are right. When I remove this device from another account, it works fine. I can't understand why it only happens with some users in my server, where there are almost 300+ vehicles and over 200 users. This issue occurs randomly with certain users and devices. In this account that I tested, there are two devices linked to the user account - one is functioning properly, while the other does not work. However, when I remove it from the user account, it works fine.

@Hamza, yes that is exactly my experience
when some devices are shared with multiple accounts whenever a vehicle is moving i receive the ignition on event every second
per my experience this happened with teltonika fmb920 and the devices in tracccar have the same name as "vito" + vin number so that could be what is causing it
the problem is pretty random and after some days its start working normaly again