ibutton support

That was BRILLIANT!
Thats the solution

Thank you Anton

Hi all,

We are currently planning to upgrade our Traccar server from version 4.10 to 6.5 and have encountered an issue related to iButton driver IDs (driveruniqueId).

In the older version (4.10), Traccar was reading the iButton/driverUniqueId in reversed order, so during our initial setup, we created all drivers in tc_drivers using the reversed uniqueId values to make driver assignment work correctly.

For example:
Actual iButton ID:
1234
Stored in database:
4321

Now, in newer Traccar versions, it appears this issue has been fixed and the incoming driverUniqueId is being read correctly. Because of this, live driver matching no longer works after the upgrade since the IDs stored in our database are reversed.

The main challenge is that we have billions of rows in tc_positions, including historical data and reports that depend on these driver IDs. Performing full migration will be risky.

What would be the recommended migration strategy in this situation?

Has anyone handled a similar migration with very large databases?

Any guidance, please?

Thank you.

If you want both historical and new data to work, you can just register both versions of the iButton ID.

Thanks for the suggestion.

Just to clarify, if we register both versions of the iButton ID (normal and reversed), wouldn’t that result in duplicate driver entries in tc_drivers?

Yes.

Ok, Thank you.