TrackeraX v4.5.0

TrackeraX रिलीज़ नोट्स और संपूर्ण चेंजलॉग 4.5.0 (minor) — 2026-08-27.

New Features

  • Beacons available through the API — Beacons could only be managed from the tracking screen. They now have their own API endpoints to list, create and edit them, so an external system can keep them in sync without anyone opening the web.
  • Commands grouped by protocol — When you select devices that speak different protocols, the command list can now be returned grouped by protocol instead of merged into one list, so it is clear which devices accept each command. Existing integrations keep receiving the flat list unless they ask for the grouped one.
  • Assign users to an alert from the API — Alerts could already be linked to devices, drivers and geofences from the API, but not to users. Now they can, and the alert responses return the linked users along with the rest.
  • History filtered by server time — The message history can now be filtered by the time the server received each position instead of the time the GPS reported it. Useful for systems that sync by ingestion and were losing records sent late by the device.
  • A manager can now report to another manager — The manager dropdown used to list only top-level managers with a special permission ticked, so chaining was not possible in practice. That permission is gone and the dropdown lists every manager. Users, Managers, Demo and Operator accounts can have a parent manager.
  • Client comment in the account API — The account endpoint can optionally return the client comment, so a reseller portal can show it without a second call. It is off by default and enabled per server.

Improvements

  • Faster push notifications — Push messages used to be sent one device at a time, so an account with several phones slowed down the whole notification queue. They are now sent in parallel, and only the ones that fail are retried individually.
  • Event lists show the alert name — Events and the Recent Events widget now show the name of the alert that fired instead of a generic message, so you can tell two alerts of the same type apart at a glance.
  • Changing your password now signs out the mobile app — Changing the password already ended the API session, but the phone kept receiving push notifications. Those are now revoked too, so a device you no longer control stops receiving anything.
  • Expired accounts get a clear message when signing in — Signing in with an expired subscription used to reload the login screen without saying why. It now answers with the actual reason.
  • Sensor widget no longer overflows — Long sensor names used to stretch the widget and distort the layout. They are now trimmed to fit.
  • Object quota shown against the right manager — When an administrator edits a sub-manager, the remaining object quota is now calculated against that user's parent manager instead of against whoever is saving, and the hint refreshes when you change the manager.
  • An expired top manager now suspends the whole branch — Only the direct manager was checked, so if the root manager expired, users hanging from a sub-manager could still sign in. The full chain is checked now.

Fixes

  • Drivers no longer show devices from other accounts — A device transferred to another account kept appearing in the previous owner's driver list and in their reports. Driver device lists are now filtered by the real owner, and the leftover links are cleaned up when a device changes hands or is deleted.
  • Duplicate alerts and pop-ups for a single event — An event that fired once could be reported again by the next position if the first one did not finish writing. The alert is now marked as fired the moment it triggers.
  • Fuel consumption inflated by reporting gaps — If a device stopped reporting for hours, the hourly consumption report billed every one of those hours at once. The gap that can be charged is now capped.
  • Company logo broken on PDF reports — A logo saved as a CMYK JPEG was embedded as-is and came out with inverted colours on every report. It is now converted when uploaded, and if the server cannot convert it the upload is rejected with an explanation instead of silently breaking the reports.
  • Permissions lost when switching a user to Manager — Changing a user to the Manager group and saving in one go dropped their permissions, because they were calculated against the old role. They are now recalculated after the new group is saved.
  • Call-action alerts accepted future dates — The call date could be set in the future. It is now capped at the current time.
  • SMS template edit returned an empty response — Editing an SMS template through the API answered with an empty body, so integrations could not tell whether it worked.

Device Support

  • SEEWORLD W20L: sensors, alarms and beacons — Full support for its Bluetooth accessories — door sensor, tyre pressure, temperature tag, beacon and oil level — plus its own alarms: high and low temperature, water immersion, roll over, door, and displacement. Its OBD data is decoded as well: RPM, speed, fuel, coolant temperature, throttle, consumption, fault count and VIN.
  • Jimi JC400 and JC261 dash cams: recording list — These cameras upload their recording list over HTTP instead of answering on the tracking channel. The list is now received and shown in the recordings window.
  • Temperature readings on 208L trackers — The eight temperature points these devices upload are now decoded and stored.
  • Stability on GT06 and JT808 devices — Two malformed frames could bring down the tracking backend: short GT06 event frames and truncated JT808 cell-tower batches. Both are now handled safely.

सभी संस्करण देखें