I installed version 5.3 and I have a device which works with protocol h02 on port 5013.
In the log some messages are decoded and some don't. They have the same structure, I don't understand why
The 127.0.0.1 is because the packets are coming through a proxy but it should not affect the result at all, because as you can see, some messages are decoded and the structure is the same and the info is reaching traccar properly.
As you can see in the example, the first two messages are properly decoded and shown, but the next ones which are very similar are not decoded.
Some times are decoded and sometimes don't. I don't see the different in the structure of the messages.
Might be a problem with the decoder ??
2022-08-15 19:44:47 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517444715082243130965060084477126016263fffffbffff001f790000005200d60300000000022661
2022-08-15 19:44:48 INFO: [Tdf2392d6] id: 4771055555, time: 2022-08-15 19:44:47, lat: 43.21828, lon: -8.74619, speed: 16.0, course: 263.0
2022-08-15 19:45:17 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517451715082243130708060084494636009290fffffbffff001b790000005200d60300000000022a62
2022-08-15 19:45:23 INFO: [Tdf2392d6] id: 4771055555, time: 2022-08-15 19:45:17, lat: 43.21785, lon: -8.74911, speed: 9.0, course: 290.0
2022-08-15 19:45:24 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517452415082243130831060084495896011350fffffbffff0019790000005200d60300000000021463
2022-08-15 19:45:39 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517453915082243131331060084494806011069fffffbffff0012670000005200d60300000000021664
2022-08-15 19:45:47 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517454715082243131410060084490796013079fffffbffff0012680000005200d60300000000021865
2022-08-15 19:46:09 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517460915082243131689060084480616013039fffffbffff0017580000005200d60300000000021866
2022-08-15 19:46:17 INFO: [Tdf2392d6: h02 < 127.0.0.1] 24477105555517461715082243131942060084478366012051fffffbffff0017590000005200d60300000000021667
Are you sure you included everything from the log? Maybe those are filtered?
The only filter I have on traccar.xml is
<entry key='filter.zero'>true</entry>
The log have a lot many lines like that some of them decoded and some of the them don't
I'm trying to create a dummy device and resend the packages modifying the timestamps to the server as well as make the same test to some of the demo traccar servers to reproduce the problem, I'll let you know the result.
I resend the messages changing the timestamp and device id to a dummy device, and the server decode them properly the second time
I don't know why it did not decode them the first time. In any case something to remember just in case.
Thanks anyway Anton
Have you specified h02.messageLength config parameter?
No I did not, but I am not sure if this might be the solution because as you can see in the log posted, all the frames have the same length , 94 bytes in the log either the decoded as the undecoded
However I'll try to check with this parameter.
The length is 47 bytes. Try it please.
Thank you very much for your help once again Anton.
I am going to try this parameter and will come back with a field test results tomorrow
Everything seems to be decoded now.
Thanks for your help Anton
I installed version 5.3 and I have a device which works with protocol h02 on port 5013.
In the log some messages are decoded and some don't. They have the same structure, I don't understand why
The 127.0.0.1 is because the packets are coming through a proxy but it should not affect the result at all, because as you can see, some messages are decoded and the structure is the same and the info is reaching traccar properly.
As you can see in the example, the first two messages are properly decoded and shown, but the next ones which are very similar are not decoded.
Some times are decoded and sometimes don't. I don't see the different in the structure of the messages.
Might be a problem with the decoder ??