Huabao Protocol Travel Reports
If you want it to be resolved - yes.
As I said I have a platform with traccar 6.3 and another with traccar 5.12, a device with Huabao protocol that has reported to both platforms to compare the behaviour and I have detected that in the platform with traccar 6.3 the motion data that the device delivers is always in false, on the other hand the platform with traccar 5.12 the motion data goes from false to true depending on the case. I think this is where the problem lies.
change this line
https://github.com/traccar/traccar/blob/v6.3/src/main/java/org/traccar/protocol/HuabaoProtocolDecoder.java#L368
for this line
https://github.com/traccar/traccar/blob/v5.12/src/main/java/org/traccar/protocol/HuabaoProtocolDecoder.java#L632
and the trip report works
The change consists of replacing the 4 with a 2, I leave image
that is a competent answer from Cristian and not read the documentation.
the change did not completely solve the problem, now the device remains permanently with the motion option set to true, recording a single trip whose end time changes when the ignition is switched to off. I think it's a protocol issue.
to close this topic, I made the following changes
this line was commented on
https://github.com/traccar/traccar/blob/v6.3/src/main/java/org/traccar/protocol/HuabaoProtocolDecoder.java#L368
this line is left unchanged
https://github.com/traccar/traccar/blob/v6.3/src/main/java/org/traccar/protocol/HuabaoProtocolDecoder.java#L592
trips are now displayed separately and I receive notifications of device movement
in the image you can see that the first trip is with the error, from the second trip after the modifications to the protocol it is working as expected.
I also receive movement notifications
This should fix the problem:
https://github.com/traccar/traccar/commit/43b876dec70353f96cb82f7b3b95b322741a18ef
thanks Anton, I'll try the modification
I now have this problem with Haubao protocol also. I'm using Traccar version 6.6.
The device is shown correctly on the map when watching live but doesn't show up in any reports. I got it to show up in reports by emulate it, but then it goes over to osmand so I guess that's why. Note that only the positions when emulating is shown in the reports, not the ones reported by the device.
One thing also when emulating, it apparently records the clicks on the map (as its logged ant shown in the log and report) but it does not move the device icon. I have a dummy-device that is only for emulation and also a device with h02 protocol, both of those move around the map when emulating but the device with Huabao does not, the icon stay where the Huabo-protocol last reported the position.
I'm sorry, I found the problem. It appears to be the timezone. Apparently Haubao (JT808) always reports time in GMT+8 so the trips were recorded but on the wrong day.
Now I'm playing around with the timezone attribute for the device, is that meant to help with this kind of problem or is there an other solution maybe?
@sb_sthlm The same thing happens to me, did you find the solution?
I think so, by adding the attribute timezone to the device with the value GMT+8.
5.12 works -> 6.0 and above not... do I need to read documentation and looking for a fault?