Cannot get Freematic one+ Trackers to work with Traccar 6.10.0

Bernhard17 days ago

I recently decided to reinstall Traccar on a new Server (Raspberry Pi 5 with SSD Hat).
Server worked with with osmand Protokoll (Traccar client on Apple-Device) but I do not get any GPS coordinated from my freematics.
For a while, the old traccar server (Raspberry Pi 3) was running and I can confirm that the freematic devices sent GPS coordinates to that server.

NAT is configured correctly. I double and triple checked because I read that is is the issue most of the time.
I do not run a docker. I installed Version 6.10.0 using this instructions: https://www.traccar.org/linux/
I also installed a lot of other versions back to 6.4 none seem to work.

This is what my log file looks like when the freematics device is active:

[U6c92cf9d: freematics < 213.147.167.19] E591GZG5#EV=1,TS=228881,ID=E591GZG5*71
[U6c92cf9d: freematics > 213.147.167.19] 1#EV=1,RX=1,TS=228881*EE

or, when I am connected via WIFI:

[U6c92cf9d: freematics < 192.168.1.1] E591GZG5#EV=1,TS=31519,ID=E591GZG5*37
[U6c92cf9d: freematics > 192.168.1.1] 1#EV=1,RX=1,TS=31519*B4

I have another one connected to a car right now and GPS signal should be good enough. At least I get the VIN in that case:

[U6c92cf9d: freematics < XXX.147.166.102] A0HN8EJS#EV=1,TS=356510,ID=A0HN8EJS,VIN=NHAHA51BLAH556666*1B
[U6c92cf9d: freematics > XXX.147.166.102] 1#EV=1,RX=1,TS=356510*E5

As long as the old traccar server was running I could switch between them altering the Port Forward ... I instantly got GPS data on the old server. What changed? Do I need to set up something on the new versions of Traccar?

I am all out of ideas.

traccar.xml file has not been altered

Bernhard17 days ago

I forgot to mention: I also built an up to date version of freematics on the E591GZG5 device. But on A0HN8EJS there is still the older version which definitely worked on the old server.

Anton Tananaev17 days ago

It doesn't seem like your device is sending any location data.

Bernhard16 days ago

Unfortunately not.
I did another test to proof that the device is sending location data and what I found is kinda weird:

I resurrected the old server which is running traccar 5.9:
This is what I get when I supply my freematics with power (USB and 12Vold but it is not plugged into the car, therefore no OBD Data):

2025-10-02 17:10:50  INFO: [Uace63473: freematics < 192.168.1.1] 45353931475a473523303a33313235342c38313a2d36342c32343a3336332c32303a303b2d302e30313b302c38323a34332a3143
2025-10-02 17:10:51  INFO: [Uace63473] id: E591GZG5, time: 2025-10-02 17:10:50, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0
2025-10-02 17:10:53  INFO: [Uace63473: freematics < 192.168.1.1] 45353931475a473523303a33343133372c32343a3335372c32303a303b303b302c38323a34342a31
2025-10-02 17:10:53  INFO: [Uace63473] id: E591GZG5, time: 2025-10-02 17:10:53, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0
2025-10-02 17:10:56  INFO: [Uace63473: freematics < 192.168.1.1] 45353931475a473523303a33373032302c32343a3335382c32303a303b303b302c38323a34342a4643
2025-10-02 17:10:56  INFO: [Uace63473] id: E591GZG5, time: 2025-10-02 17:10:56, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0

I then switched my NAT to the news Server and got these messages on my 6.10 Server:

2025-10-02 18:13:36  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:94509,24:362,20:0.08;-0.24;0.10,82:44*EC
2025-10-02 18:13:39  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2025-10-02 18:13:41  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:99510,81:-54,24:361,20:0.07;-0.24;0.11,82:44*4D
2025-10-02 18:13:44  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2025-10-02 18:13:46  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:104511,24:359,20:0.08;-0.25;0.11,82:44*15
2025-10-02 18:13:49  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2025-10-02 18:13:51  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:109511,24:369,20:0.08;-0.24;0.11,82:45*1B
2025-10-02 18:13:54  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0

this did not look like the entries in the last few days, so I disconnected the Freematic from power and restarted it which resulted in the logentries I shared yesterday:

2025-10-02 18:14:11  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#EV=1,TS=17596,ID=E591GZG5*40
2025-10-02 18:14:11  INFO: [U3500e9bc: freematics > 192.168.1.1] 1#EV=1,RX=1,TS=17596*BD
2025-10-02 18:14:11  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#EV=1,TS=17596,ID=E591GZG5*40
2025-10-02 18:14:11  INFO: [U3500e9bc: freematics > 192.168.1.1] 1#EV=1,RX=1,TS=17596*BD
2025-10-02 18:14:11  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#EV=1,TS=17596,ID=E591GZG5*40
2025-10-02 18:14:11  INFO: [U3500e9bc: freematics > 192.168.1.1] 1#EV=1,RX=1,TS=17596*BD

I did not change my GPS coordinates, if anyone sees this and finds out where I live, please come and wants to help me .. there will be beer

Anton Tananaev16 days ago

Are you sure device is not indoors, has had clear sky visibility for at least 30 minutes? No issues with GPS antenna?

Bernhard16 days ago

It's hanging out of the window ... clear skies today.
The timestamps in the first log is incorrect due to timezone settings. I did all 3 logs in a matter of ~5 Minutes. It could not have lost GPS connection the way it is positioned

Bernhard16 days ago

he are some more logs with correct timestamps:
Traccar 5.9:

2025-10-02 18:35:01  INFO: [Ua8acb02a: freematics < 192.168.1.1] 45353931475a473523303a32353531302c32343a3335342c32303a2d302e30313b303b302c38323a33352a4235
2025-10-02 18:35:01  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-02 18:35:01, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0
2025-10-02 18:35:04  INFO: [Ua8acb02a: freematics < 192.168.1.1] 45353931475a473523303a32383339332c38313a2d35322c32343a3336372c32303a303b303b302c38323a33362a3644
2025-10-02 18:35:04  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-02 18:35:04, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0
2025-10-02 18:35:07  INFO: [Ua8acb02a: freematics < 192.168.1.1] 45353931475a473523303a33313237362c32343a3335312c32303a303b303b302c38323a33362a4644
2025-10-02 18:35:07  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-02 18:35:07, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0
2025-10-02 18:35:09  INFO: [Ua8acb02a: freematics < 192.168.1.1] 45353931475a473523303a33343135392c32343a3335382c32303a2d302e30313b303b302c38323a33372a4334
2025-10-02 18:35:10  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-02 18:35:10, lat: 48.10999, lon: 16.28621, speed: 0.2, course: 271.0

Traccar 6.10:

2025-10-02 18:35:33  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:57222,24:368,20:0;-0.01;0,82:39*C3
2025-10-02 18:35:33  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2025-10-02 18:35:35  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:60105,81:-53,24:359,20:0;0;0,82:39*65
2025-10-02 18:35:36  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2025-10-02 18:35:38  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:62988,24:358,20:0;-0.01;0,82:39*D1
2025-10-02 18:35:38  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
2025-10-02 18:35:41  INFO: [U3500e9bc: freematics < 192.168.1.1] E591GZG5#0:65871,24:368,20:-0.01;-0.01;0,82:39*88
2025-10-02 18:35:41  INFO: [U3500e9bc] id: E591GZG5, time: 1980-01-06 01:00:00, lat: 0.00000, lon: 0.00000, course: 0.0
Anton Tananaev16 days ago

In both cases your device is not reporting any location. In the first one it just had some last known location that it keeps reusing.

Bernhard16 days ago

where is the last known location stored? I guess writing a new freematics version to the tracker would overwrite that stored location?

Anton Tananaev16 days ago

It is stored in the database, same as all data.

Bernhard16 days ago

ah on the traccar-side .. ok

Bernhard15 days ago

OK, I got the external GPS Antenna to work with the newest Freematics source code.

But the communication problem with Traccar persists:
Server 5.9:

2025-10-03 16:59:37  INFO: [Ua8acb02a: freematics < 213.147.164.208] 45353931475a473523303a32383936302c38313a2d36332c32343a3334312c32303a302e32323b302e35313b302e33372c38323a35362a3237
2025-10-03 16:59:37  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-03 16:59:37, lat: 48.11015, lon: 16.28632, speed: 0.1, course: 0.0
2025-10-03 16:59:40  INFO: [Ua8acb02a: freematics < 213.147.164.208] 45353931475a473523303a33313834332c32343a3334332c32303a302e32323b302e35313b302e33372c38323a35362a4245
2025-10-03 16:59:40  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-03 16:59:40, lat: 48.11015, lon: 16.28632, speed: 0.1, course: 0.0
2025-10-03 16:59:43  INFO: [Ua8acb02a: freematics < 213.147.164.208] 45353931475a473523303a33343732372c32343a3333352c32303a302e32323b302e35303b302e33372c38323a35362a4332
2025-10-03 16:59:43  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-03 16:59:43, lat: 48.11015, lon: 16.28632, speed: 0.1, course: 0.0
2025-10-03 16:59:46  INFO: [Ua8acb02a: freematics < 213.147.164.208] 45353931475a473523303a33373631312c32343a3334372c32303a302e32323b302e35303b302e33372c38323a35362a4330
2025-10-03 16:59:46  INFO: [Ua8acb02a] id: E591GZG5, time: 2025-10-03 16:59:46, lat: 48.11015, lon: 16.28632, speed: 0.1, course: 0.0

Then I switched the port forward to the 6.10 server:

2025-10-03 17:00:06  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:57802,24:348,20:0.22;0.50;0.37,10:15000430,A:48.109982,B:16.286345,C:0,D:0.2,E:0,12:255,82:56*63
2025-10-03 17:00:09  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:60685,24:346,20:0.22;0.51;0.37,82:56*C7
2025-10-03 17:00:09  INFO: Event id: E591GZG5, time: 2025-10-03 16:49:38, type: deviceMoving, notifications: 0
2025-10-03 17:00:09  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:00:04, lat: 48.10998, lon: 16.28635, speed: 0.1, course: 0.0
2025-10-03 17:00:12  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:63570,24:336,20:0.21;0.51;0.37,10:15001090,A:48.109970,B:16.286343,C:0,D:0.1,E:0,12:255,82:56*5C
2025-10-03 17:00:12  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:00:04, lat: 48.10998, lon: 16.28635, speed: 0.1, course: 0.0
2025-10-03 17:00:14  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:66455,24:348,20:0.22;0.50;0.37,10:15001400,A:48.109970,B:16.286343,C:254,D:0.2,E:8,F:6,12:25,82:56*80
2025-10-03 17:00:15  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:00:10, lat: 48.10997, lon: 16.28634, speed: 0.1, course: 0.0
2025-10-03 17:00:17  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:69339,24:346,20:0.22;0.50;0.37,82:56*CB
2025-10-03 17:00:17  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:00:14, lat: 48.10997, lon: 16.28634, speed: 0.1, course: 8.0
2025-10-03 17:00:20  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:72223,24:339,20:0.22;0.50;0.36,10:15001980,A:48.109978,B:16.286346,C:254,D:0.1,E:8,F:6,12:25,82:56*8C
2025-10-03 17:00:20  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:00:14, lat: 48.10997, lon: 16.28634, speed: 0.1, course: 8.0
2025-10-03 17:00:23  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:00:19, lat: 48.10998, lon: 16.28635, speed: 0.1, course: 8.0
2025-10-03 17:00:25  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:77224,24:351,20:0.21;0.50;0.37,10:15002260,A:48.109982,B:16.286348,C:252.5,D:0,E:8,F:6,12:25,82:56*83
... this goes on for a while then the freematics builder will say "poor connection"
2025-10-03 17:01:30  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#0:142225,24:346,20:0.36;0.78;-0.36,10:15012900,A:48.110077,B:16.286362,C:242.5,D:0.1,E:0,F:8,12:17,82:57*38
2025-10-03 17:01:31  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#EV=4,TS=142700,ID=E591GZG5,SSI=-63*53
2025-10-03 17:01:31  INFO: [U3500e9bc: freematics > 213.147.164.208] 1#EV=4,RX=1,TS=142700*E2
2025-10-03 17:01:33  INFO: [U3500e9bc] id: E591GZG5, time: 2025-10-03 17:01:29, lat: 48.11008, lon: 16.28636, speed: 0.1, course: 0.0
2025-10-03 17:01:36  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#EV=4,TS=142700,ID=E591GZG5,SSI=-63*53
2025-10-03 17:01:36  INFO: [U3500e9bc: freematics > 213.147.164.208] 1#EV=4,RX=1,TS=142700*E2
2025-10-03 17:01:41  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#EV=4,TS=142700,ID=E591GZG5,SSI=-63*53
2025-10-03 17:01:41  INFO: [U3500e9bc: freematics > 213.147.164.208] 1#EV=4,RX=1,TS=142700*E2
2025-10-03 17:01:46  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#EV=4,TS=158145,ID=E591GZG5,SSI=-63*5D
2025-10-03 17:01:46  INFO: [U3500e9bc: freematics > 213.147.164.208] 1#EV=4,RX=1,TS=158145*EC
2025-10-03 17:01:51  INFO: [U3500e9bc: freematics < 213.147.164.208] E591GZG5#EV=4,TS=158145,ID=E591GZG5,SSI=-63*5D
2025-10-03 17:01:51  INFO: [U3500e9bc: freematics > 213.147.164.208] 1#EV=4,RX=1,TS=158145*EC

and then it will say "server timeout"

I mean, the problem could very much be in the freematics code. I don't know. Considering that a vital part of the code for a freematics supplied GNSS Antenna was missing is a good indicator that the problem could very much be in the freematics code.
Do you have any idea how I could find out what the problem is?

for anyone with the same issue as me:
search for these line of codes in the "FreematicsPlus.cpp" File

#ifndef ARDUINO_ESP32C3_DEV
        if (m_flags & FLAG_GNSS_SOFT_SERIAL) {
            // set GNSS baudrate to 38400bps for M10
            const uint8_t packet[] = {0x0, 0x0, 0xB5, 0x62, 0x06, 0x8A, 0x0C, 0x00, 0x01, 0x01, 0x00, 0x00, 0x01, 0x00, 0x52, 0x40, 0x00, 0x96, 0x00, 0x00, 0xC7, 0x2B}; 
            // set GNSS baudrate to 38400bps for M8
            // const uint8_t packet[] = {0x0, 0x0, 0xB5, 0x62, 0x06, 0x0, 0x14, 0x0, 0x01, 0x0, 0x0, 0x0, 0xD0, 0x08, 0x0, 0x0, 0x0, 0x96, 0x0, 0x0, 0x7, 0x0, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0x93, 0x90};
             for (int i = 0; i < sizeof(packet); i++) softSerialTx(baudrate, packet[i]); 
        }
#endif

and change it like this:

#ifndef ARDUINO_ESP32C3_DEV
        if (m_flags & FLAG_GNSS_SOFT_SERIAL) {
           // switch M8030 GNSS to 38400bps
            const uint8_t packet1[] = {0x0, 0x0, 0xB5, 0x62, 0x06, 0x0, 0x14, 0x0, 0x01, 0x0, 0x0, 0x0, 0xD0, 0x08, 0x0, 0x0, 0x0, 0x96, 0x0, 0x0, 0x7, 0x0, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0, 0x93, 0x90};
            const uint8_t packet2[] = {0xB5, 0x62, 0x06, 0x0, 0x1, 0x0, 0x1, 0x8, 0x22};
            for (int i = 0; i < sizeof(packet1); i++) softSerialTx(baudrate, packet1[i]);
            delay(20);
            for (int i = 0; i < sizeof(packet2); i++) softSerialTx(baudrate, packet2[i]);
        }
#endif
Anton Tananaev15 days ago

I see the server responses in your second log fragment.

Bernhard15 days ago

ok but why do I get GPS updates when I use 5.9 and the GPS updates stop after a few updates when I switch to 6.10. Then immediately come back when I switch to 5.9 again?
It is the same with a ~2 year old freematics build and an up to date one. I don't know what more I should show you to describe my problem.

I don't really want to roll back to 5.9 (worst case) but it seems like it's the only version that works for me with freematics.

Bernhard15 days ago

and yes .. skies were clear today too. Car was in motion and not in a tunnel. No tall buildings around either.