Inquiry Regarding Jimi JC261 Camera Integration with Traccar
Hi,
From the proxy setup the heartbeat packets are reaching Traccar correctly and the device stays online, but the lastUpdate field is not updating because position packets are apparently not being processed correctly by Traccar.
The Jimi devices use a GT06-based protocol variant. (here is a sample position packet : 78782622190b03091739cf02c484460601327012152a01a80200000263bb010000000217860f8b12840d0a) I am forwarding all raw packets without modification to Traccar. Login packets work and device stays connected, but location packets are not updating the device position in Traccar.
Is Traccar able to decode Jimi GT06 variant packets directly, or do I need to convert/normalize the packets before forwarding?
If Traccar’s GT06 decoder does not fully understand Jimi dialect, what is the recommended approach?
Configure proper port?
Use OsmAnd?
Convert raw packets to Traccar JSON API?
Create a custom Traccar decoder?
Could you please suggest ?
The recommended approach is to implement support for any unsupported message types in Traccar.
Thanks again for the guidance.
The devices are accepting the position packets on port 5023, and Traccar is successfully decoding the position packets; the location updates are showing correctly on the map. However, when the device goes offline, the last state remains “moving” at the last reported point and time.
Do we need to implement support for the remaining Jimi-specific message types to get proper status transitions (moving → parking→ idling), or could this still be a configuration/protocol mismatch issue?
Would appreciate your thoughts on whether adding support for the missing message types is required here.
or could this still be a configuration/protocol mismatch issue?
No.
Hi Anton,
I have managed to resolve initial connectivity issues, and it was because of device authentication, and I preserved the auth packets from device and sent them to Traccar when the device connection was lost. Now my Jimi JC261 device appears as online on Traccar. However, the coordinates and last updated time are not displaying correctly. The status changes to online when I send the following packets, but no proper location or time updates are registered.
Sample packets received from the device:
78780a130406040002095d35230d0a
78780be001010101020008af10fb0d0a
Traccar shows the device as online after receiving these packets
Position and last update time are not updating correctly
Could you please help analyze if the incoming message format is correct or suggest what configuration might be missing for Traccar to parse these packets properly? Should I try any other port? Please suggest.