2017-10-24 00:01:08 INFO: [5B11D28C] connected
2017-10-24 00:01:11 DEBUG: [5B11D28C: 5027 < 213.226.59.239] HEX: 000f333537343534303734353736313037
2017-10-24 00:01:11 DEBUG: [5B11D28C: 5027 > 213.226.59.239] HEX: 01
2017-10-24 00:01:15 DEBUG: [5B11D28C: 5027 < 213.226.59.239] HEX: 000000000000003b08010000015f4b098cf0000ef68e3319a52ed900d70160100000000602010015050142319e02c700000000f100006ef1014e0000000000000000010000e0ea
2017-10-24 00:01:15 DEBUG: [5B11D28C: 5027 > 213.226.59.239] HEX: 00000001
2017-10-24 00:01:16 INFO: [5B11D28C] id: 357454074576107, time: 2017-10-24 00:00:38, lat: 43.02558, lon: 25.10393, speed: 0.0, course: 352.0
2017-10-24 00:02:20 INFO: [5B11D28C] disconnected
2017-10-24 00:06:23 INFO: [2605A999] connected
2017-10-24 00:06:24 DEBUG: [2605A999: 5027 < 213.226.59.135] HEX: 000f333537343534303734353736313037
2017-10-24 00:06:24 DEBUG: [2605A999: 5027 > 213.226.59.135] HEX: 01
2017-10-24 00:06:26 DEBUG: [2605A999: 5027 < 213.226.59.135] HEX: 000000000000003b08010000015f4b0e20d0000ef68e3319a52ed900d70160100000000602010015050142319e02c700000000f100006ef1014e00000000000000000100001d3c
2017-10-24 00:06:26 DEBUG: [2605A999: 5027 > 213.226.59.135] HEX: 00000001
2017-10-24 00:06:26 INFO: [2605A999] id: 357454074576107, time: 2017-10-24 00:05:38, lat: 43.02558, lon: 25.10393, speed: 0.0, course: 352.0
2017-10-24 00:07:32 INFO: [2605A999] disconnected
2017-10-24 00:11:35 INFO: [8A27B6D0] connected
2017-10-24 00:11:37 DEBUG: [8A27B6D0: 5027 < 85.118.74.144] HEX: 000f333537343534303734353736313037
2017-10-24 00:11:37 DEBUG: [8A27B6D0: 5027 > 85.118.74.144] HEX: 01
2017-10-24 00:11:40 DEBUG: [8A27B6D0: 5027 < 85.118.74.144] HEX: 000000000000003b08010000015f4b12b4b0000ef6900519a530de00dc00a5110000000602010015050142319802c700000000f100006ef1014e0000000000000000010000c5d7
2017-10-24 00:11:40 DEBUG: [8A27B6D0: 5027 > 85.118.74.144] HEX: 00000001
2017-10-24 00:11:40 INFO: [8A27B6D0] id: 357454074576107, time: 2017-10-24 00:10:38, lat: 43.02564, lon: 25.10397, speed: 0.0, course: 165.0
2017-10-24 00:12:45 INFO: [8A27B6D0] disconnected
I have checked one of the messages and it has 0000000000000000
as iButton value.
Hi Anton, Greetings!
I am still unable to map the ibutton codes from teltonika devices
Example -
The ibutton code is 4400001940C75001
The driverUniqueId value received in attributes is 94794670286045252
i could not convert the ibutton code to match this value received from the device.
Please can you guide on how to resolve this.
regards,
Naveen
I believe that the issue is already fixed. You need to wait for the next release or build from source.
I will build from source and try.
i have 2 questions
Is the fix done while saving the driver id in drivers table?
or is the fix done while saving in the attributes field in positions table?
After building from source,
traccar\traccar-web\web folder has to be copied and updated in the live server web folder
& tracker-server.jar file has to be copied to the Traccar folder in live server
Are there any other files/folders to be copied after building from source?
Please can you let me know.
regards,
Naveen
This question doesn't make sense to me. In attributes we always store only driver id. Drivers table has nothing to do with this.
You need to update everything. If you don't know what you are doing I would recommend to wait for official release.
Hi, Greetings!?
I get it. Once the new release comes, this issue will be fixed and the ibuttons data will be matching.
How about the old records in the positions table for earlier ibuttons shown.
Is there a way to map these old records as well?
Please let me know.
regards,
Naveen
If you want old records to work you would have to manually update database entries.
Hi, Is there a code to convert the driveruniqueid value in positions table to match the ibutton id
I believe you just need to convert decimal number into the hex number.
Thanks for quick reply.
122483409598546144 is the driveruniqueid in positions table
when i convert to hexa, i get 1B32603180000E0
But the actual ibutton code is 7D000018030C9101
How to get this mapped?
Please let me know.
Don't know. It works for the example that you provided earlier.
Hi Anton,
Greetings!
i upgraded to version 3.15
Now the driver ibutton id shown in positions table is 014FA8F51600000A
In 3.14, it was shown as 94479887787622410
The actual ibutton id is 0A000016F5A84F01
I am not able to map the ibutton id even with the new version.
Please can you check.
regards,
Naveen
Looks like you just need to reverse the number.
Please provide full messages. Your text editor has cut the most important lines.