> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/on-premise/versions/2026.md).

# 2026

Release notes for Navixy on-premise builds in 2026. Details new features, device integrations, third-party solutions, platform improvements, and bug fixes.

## 2026.10 (18 Nov 2026)

Build 2026.10 lets a platform administrator add web applications to the menus of many users. It also adds a phone layout for the user interface and the Navixy Admin Panel. The Linux installation script supports more distributions, and the Windows script now also works on Windows Server 2016. The release also adds new GPS devices, such as the Teltonika ATC774 and ATM774 asset GPS devices, and includes improvements and fixes. The entry also covers the 2026.07 updates released after July 30, 2026.

{% hint style="warning" %}

### Before you update

* **Java:** Like build 2026.07, Standalone build 2026.10 requires Java 25. Make sure that your Java version is 25 before you run the update script. On Windows, if your installation still runs on Java 21, install JDK 25 first. Then add the JDK 25 `bin` folder to the `PATH` system variable, set `JAVA_HOME` to the JDK 25 folder, and run the updater.
* **Backups and disk space:** Perform a backup before any Navixy version update. The Linux update script needs about 2 GB of free disk space and checks it before the update. A Docker update needs much more, because the new images are built next to the old ones. On installations with many devices, the database update takes longer than in earlier updates. If the database update fails, the update script stops with an error. On Linux, it leaves the Navixy services stopped. Contact Navixy support in that case.
* **SMS through Textlocal:** Textlocal no longer sends messages, because its service moved to Webex Interact. If your instance sends SMS through Textlocal, set up the Webex Interact gateway after the update. To do this, run `configure.sh`, choose **Configure SMS gateway** → **Webex Interact**, and enter your Webex access token. The Webex Interact gateway only sends messages. Unlike Textlocal, it doesn't receive incoming SMS or delivery reports.
* **Requests to your own network:** Software commands and the IoT Logic Webhook node no longer send requests to the Navixy server itself or to addresses in a private network. To allow requests to systems in your own network, add the line `httpExecutor.forbidSelfHost=false` to the `tcp-server` configuration file. Then restart `tcp-server`.
* **Queclink iButton keys:** Queclink GV300W and GV310LAU devices now record an iButton key in the order that the device sends it in. Register again every iButton key that was registered under the reversed number.
  {% endhint %}

### Installation and update

These changes affect how a Standalone instance is installed and updated. For the full procedure, see the [update guide](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/update.md).

* The Linux installation script supports Ubuntu 22.04, 24.04, and 26.04, Debian 12 and 13, and AlmaLinux, Rocky Linux, and Red Hat Enterprise Linux 9 and 10. Ubuntu 20.04 is no longer supported. New installations get MySQL 8.4. On Debian 12, which has no OpenJDK 25 package, the script offers Temurin JDK 25.
* The Windows installation script now also works on Windows Server 2016, so it supports Windows Server 2016 to 2025. Windows Server 2016 has no `tar` command, so unpack the package there with an archiver such as 7-Zip.
* Fixed the Windows installation on two servers. The installation no longer stops on an application server without a local MySQL server. A database-only server can open the MySQL port for the local network.
* New Windows installations get a random password for the MySQL root user. The Windows updater offers to set one on installations with MySQL 8.4 whose root user has no password. The password is stored in `C:\ProgramData\Navixy\mysql-root.cnf`, which only administrators can read. If your own scripts connect to MySQL as root, for example backup scripts, make them read the password from this file with the `--defaults-extra-file` option.
* Navixy services restart automatically after a failure.
* The Windows updater runs Nginx as the **Navixy nginx** Windows service, and only administrators can open `C:\nginx` and `C:\java`. To apply changes to the Nginx configuration, run `C:\nginx\nginx-reload.bat` as administrator.
* Docker containers created by the 2026.10 `docker-update.sh` or by `docker compose up -d` start again after a server restart.
* The image preview cache moved from `/tmp/nginx-images-cache` to `/var/cache/nginx/images`. The update script changes the path in all Nginx configuration files, including your own.
* Docker images are built only from public base images.
* `configure.sh` supports installations without HTTPS.
* Fixed file uploads on new installations. The Linux and Windows installation scripts set up the file storage, and the update creates it on installations that have none.
* Fixed links to uploaded files on Linux installations set up with `configure.sh`, and on Windows and Docker installations. The links use your service domain, and HTTPS when it's set up.
* Fixed links in emails and reports starting with `http://` after HTTPS was set up, and pointing to a sample domain on new Windows installations.

### Applications for all users

The new **Applications** tab in Admin Panel **Settings** lets a platform administrator add a web application once and show it to many users. Place the application in the users' menu with the [Menu editor](https://navixy.com/docs/admin/settings/custom-menu-editor.md), as a menu item or as a tab inside an item. The application opens inside the user interface or in a new browser tab.

Users keep their own [user applications](https://navixy.com/docs/user/guide/account/user-applications.md).

### Phone layout

The user interface and the Navixy Admin Panel have a layout for phones. In a phone browser, a navigation bar at the bottom of the screen replaces the side menu.

The lists below cover new integrations and devices, platform improvements, and bug fixes.

<details>

<summary>Integrated</summary>

### Devices

| Manufacturer          | Device                                                                                                                                     | Type                                                                                                                                                                         |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Jimi IoT (Concox)** | JM-LL307                                                                                                                                   | Asset GPS device                                                                                                                                                             |
|                       | PL601                                                                                                                                      | Personal GPS device                                                                                                                                                          |
|                       | VL863P                                                                                                                                     | Vehicle GPS device with driver identification                                                                                                                                |
| **KCS TraceME**       | TM-178/R9H7, TM-178/R9H10, TM-186, TM-188, TM-R9B3                                                                                         | Vehicle modules. TraceME modules don't connect to Navixy directly: KCS converts their data and sends it in the Wialon IPS protocol. Ask KCS to send the data to your server. |
|                       | TM-231, TM-901, TM-1025, TM-2001, TM-2011, TM-2016, TM-2206, TM-2207, TM-2208, TM-3001, TM-3201, TM-4202, TM-4400                          | Asset modules and tags, connected through KCS like the vehicle modules                                                                                                       |
| **Meitrack**          | K211L, K211E                                                                                                                               | Electronic padlocks                                                                                                                                                          |
| **Queclink**          | GL30MEU                                                                                                                                    | Asset GPS device                                                                                                                                                             |
|                       | [GV58LAU](https://navixy.com/en/devices/queclink/queclink-gv58lau/), [GV310LAU](https://navixy.com/en/devices/queclink/queclink-gv310lau/) | Vehicle GPS devices                                                                                                                                                          |
| **Suntech**           | ST8310U 4G                                                                                                                                 | Vehicle GPS device. Use this profile for ST8310U devices with firmware 1.146 or newer.                                                                                       |
| **Teltonika**         | ATC774, ATM774                                                                                                                             | Asset GPS devices                                                                                                                                                            |
| **Topin**             | YG-T91, YG-T92                                                                                                                             | Vehicle GPS devices                                                                                                                                                          |

</details>

<details>

<summary>Improved</summary>

* **General platform improvements**
  * The Navixy Admin Panel can [change the plan](https://navixy.com/docs/admin/devices/change-plan.md) of several devices at once.
  * The new **Hide device IMEI** option in the Admin Panel [user defaults](https://navixy.com/docs/admin/settings/user-defaults.md) and in the user form hides device IMEIs from users.
  * Admin Panel users can change the interface language from the side menu.
  * Admin Panel exports can contain only the filtered rows or the selected devices.
  * The Admin Panel user list can be sorted by status.
  * Technician accounts in the Admin Panel see the same logo as their dealer.
  * The geofence picker has a strict search mode that finds only exact name matches.
  * Shift-click a group in the object list expands or collapses all groups.
* **Tracking and data**
  * [Commands](https://navixy.com/docs/user/guide/devices-and-settings/object-management/commands.md) can contain a value that the Navixy platform asks for each time you send the command. After you send a command, the Navixy platform shows its result.
  * The Driver widget in Tracking shows the employee's photo.
  * Users of the X-GPS Mobile apps receive push notifications from a Standalone instance. These apps are built into the SMS server, so no setup is needed.
  * The tracking server can connect to several MQTT brokers and switches to the next broker when a broker isn't available.
* **Reports**
  * The [Measuring sensors report](https://navixy.com/docs/user/guide/reports/specific-report-details/measuring-sensors-report.md) has detail intervals from 5 seconds to 6 hours.
  * The report preview map has a **Clear all marks** tool.
  * A report chart's tooltip lists every data series.
  * The [maintenance](https://navixy.com/docs/user/guide/fleet-management/maintenance.md) export can include the remaining mileage, the remaining engine hours, and the remaining days.
* **IoT Logic**
  * When you close a node's settings panel with unsaved changes, IoT Logic asks for confirmation.
* **Devices and protocols**
  * Teltonika [FMB920](https://navixy.com/en/devices/teltonika-telematics/teltonika-fmb920/), [FMC920](https://navixy.com/en/devices/teltonika-telematics/teltonika-fmc920/), and [FMM920](https://navixy.com/en/devices/teltonika-telematics/teltonika-fmm920/) have new activation profiles with 3 digital inputs.
  * Added CAN data for Assistant Telematics AVT110 and AVT110T, such as fuel level, tire pressure, and current gear.
  * Restored hardware mileage for Assistant Telematics AVT devices.
  * Added diagnostic trouble codes, the ICCID, and the VIN for Teltonika FMC650 and the FMB640 line.
  * Added hardware mileage, temperature, humidity, and more events for Micodus devices.
  * Added Bluetooth magnet sensors for StarLink devices.
  * Meitrack devices receive the server time when they request it.
  * Activation no longer overwrites the settings stored on Gosafe G1C+ 5W devices.
  * Neomatica ADM50 gets an SOS rule automatically.
  * Added TopFlyTech Bluetooth sensors for TopFlyTech KnightX and SolarGuardX devices.
* **Security**
  * Updated third-party libraries and the time zone database.

</details>

<details>

<summary>Fixed</summary>

* **Security and access control**
  * Fixed the failed sign-in limit, which didn't block further sign-in attempts.
  * IoT Logic formulas can use only IoT Logic and math functions.
  * KML geofence import rejects files with unsafe content.
  * Fixed the two-factor authentication checkbox in the Admin Panel user form showing the wrong state.
  * Fixed Admin Panel users with limited permissions, such as technicians, seeing errors after sign-in.
  * Fixed users being signed out when they closed a Chromium-based browser.
  * Fixed password changes that could fail after the update to 2026.07.
  * Fixed sub-users being able to create and change the main account's IoT Logic flows.
* **Navixy Admin Panel**
  * Fixed **Service preferences** that couldn't be saved while **Display What's new** was off.
  * Fixed moving a tracker to another user leaving a duplicate entry in the list.
  * Fixed column choices in tracker lists being reset each time the window opened.
  * Fixed user transactions for a period missing part of its first or last day.
  * Fixed the user import template not downloading in some languages.
  * Fixed **Log in as user** not opening from a phone browser.
  * Fixed the device replacement dialog closing without a message when the device can't be replaced.
  * Fixed the audit log showing the server address instead of the user's IP address.
* **Devices and protocols**
  * Fixed TopFlyTech TorchX 100 location and alarm messages not being processed.
  * Fixed TopFlyTech Bluetooth sensors showing invalid values after a sensor stopped reporting.
  * Fixed wrong board voltage, dropped connections, and invalid positions for Queclink GV50M.
  * Fixed the processing of several Queclink message types.
  * Fixed harsh driving settings for the Xirgo and BCE MQTT profiles not being saved.
  * Fixed Micodus devices being decoded with another device's settings, and wrong values for negative temperatures.
  * Fixed wrong ignition and idling for Starcom Helios.
  * Fixed the StarLink TrackerBT output state not updating after an output was switched.
  * Fixed Teltonika FTC305, FTC134, and FTC164 not entering moving mode because of wrong voltage thresholds.
  * Fixed wrong green driving and auto geofence settings for Teltonika FMB640 and FMM640.
  * Fixed the decoding of several Teltonika values, such as AdBlue level and engine temperatures.
  * Fixed delayed output commands for AVEMA AT35.
  * Fixed missing track points for Neomatica ADM50, and invalid positions for Neomatica ADM devices.
* **Tracking, geofences, and alerts**
  * Fixed the **Events** tab in History staying on **Loading**.
  * Fixed commands being delayed when the device was connected to another tracking server.
  * Fixed device settings showing an error for devices on plans without work statuses.
  * Fixed address search on the Tracking map not finding exact addresses.
  * Fixed the device information panel not opening again after trip history was built.
  * Fixed a newly activated device showing empty widgets until the page was reloaded.
  * Fixed device activation not applying the default values of additional fields.
  * Fixed small odometer corrections being saved as 0%.
  * Fixed the connection status timeout being copied to only some of the selected devices.
  * Fixed wrong fuel drain thresholds with the Metric + US gallons unit system.
  * Fixed engine hours counters that read a CAN sensor. Before, they stopped increasing after their value was set manually.
  * Fixed the Geo link page showing a wrong address.
* **IoT Logic**
  * Fixed a new Device Action or Webhook node getting the ID and name of a node whose settings were closed with Escape.
  * Fixed `enterGeofence()` and `leaveGeofence()` missing some geofence entries and exits.
  * Fixed Data Stream Analyzer losing values when device monitoring stopped.
* **Reports and exports**
  * Fixed the Fuel, Engine hours, Flowmeter, and Vehicle sensor reports sometimes showing no devices.
  * Fixed reports failing when the period started later on the current day.
  * Fixed an error when every weekday was cleared in the report day filter.
  * Fixed the Eco driving report not being built **By objects**.
  * Fixed the **Ignore peaks** slider in the Fuel volume report resetting.
  * Fixed the place and geofence visits reports leaving out places that nobody visited.
  * Fixed documents such as waybills being generated empty when an error occurred.
* **Field service and fleet**
  * Fixed waybill downloads being canceled in Chrome.
  * Fixed the Driver journal header and totals being cut off in narrow windows.
  * Fixed garages being saved without a location.
  * Fixed the Maintenance list becoming empty when sorted by vehicle.
  * Fixed the recurring task list showing a placeholder instead of the assigned employee's name.
  * Fixed recurring tasks that couldn't be saved after their form template was deleted.
  * Fixed forms that fail to load showing an empty viewer instead of an error message.
* **Other**
  * Fixed the sign-in page offering X-GPS Monitor instead of X-GPS Mobile.
  * Fixed `configure.sh` leaving an SMS gateway on when you chose **Disable** or **Cancel**.
  * Fixed embedded user applications being reported as unavailable.
  * Fixed untranslated text on the Places screens, and corrected Spanish translations.

</details>

## 2026.07 (30 Jul 2026)

Build 2026.07 rebuilds the Navixy Admin Panel and Reports interfaces and adds the Commands functionality. The release also extends IoT Logic, adds Ford Pro integration, includes new GPS devices and fixes.

{% hint style="warning" %}

### Before you update

* **Java:** Standalone build 2026.07 requires Java 25. Make sure your Java version is 25 before running the update script.
* **Backups:** Perform a backup before any Navixy version update. If you are migrating to MySQL 8.4, create and keep separate backups at each major stage: before updating Navixy, before migrating MySQL, and after verifying the completed migration. Contact Navixy support before planning or performing a database migration.
  {% endhint %}

### Installation and update

These changes affect how a Standalone instance is installed and updated. For the full procedure, see the [update guide](https://navixy.com/docs/on-premise/on-premise/how-to-guide/installation/update.md).

* The updater installs Navixy Admin Panel v3 and updates the related web-server configuration.
* New installations support Ubuntu 26.04 LTS in addition to the previously supported Ubuntu releases.
* The Windows Server installation script now uses MySQL 8.4.10.

### Commands

The new [**Commands**](https://navixy.com/docs/user/guide/devices-and-settings/object-management/commands.md) block on the device settings page lets you save an instruction once and send it on demand, instead of composing it each time.

Two command types are available. A **device command** sends a protocol-level instruction string directly to the hardware, for example to send a CAN command or activate an output. A **software command** sends an HTTP POST request with a JSON body to an external URL. The request can include current device data such as location, speed, or device ID. Commands are saved per device and dispatched with a single click from the device's Object widget in the Tracking module.

Commands can also be created, updated, listed, and executed through the [Commands API](https://navixy.com/docs/navixy-api/user-api/resources/tracking/tracker/commands.md). For automated, rule-based sending across several devices, use IoT Logic instead.

### IoT Logic updates

> IoT Logic is a separately licensed feature. These updates apply automatically to Standalone instances that already have it enabled.

[IoT Logic](https://navixy.com/docs/user/guide/account/iot-logic.md) processes incoming telemetry through configurable flows before it reaches the platform. This release extends it in both directions, an external system can feed data into a flow and a flow can send data out, and adds actions that target devices other than the one that triggered them.

<details>

<summary>What became available in this release</summary>

### Bringing external data in

The **Software** tab in the [Data Source node](https://navixy.com/docs/user/guide/account/iot-logic/nodes/data-source-node.md) provides an HTTP endpoint that accepts JSON from an external system. Incoming values are matched to devices existing in the Navixy account, then become available alongside the device's own telemetry for the rest of the flow. See [Merging external system data into a flow](https://navixy.com/docs/iot-logic-api/navixy-iot-guide/merging-external-data-into-a-flow.md).

### Sending data out

The new [Webhook node](https://navixy.com/docs/user/guide/account/iot-logic/nodes/webhook-node.md) sends a structured HTTP request from a flow using a configurable URL, headers, and JSON body. Allows focused data transmission to external systems instead of complete data forwarding. Can be useful for integrations and alerting.

### Acting on other devices

The [Action node](https://navixy.com/docs/user/guide/account/iot-logic/nodes/action-node.md) has a new **Advanced** tab that lists additional devices to receive the same commands when the node is triggered. A reading from one device can therefore act on others, for example to switch an output on a second device.

### Other updates

The release also includes the following changes:

* A redesigned start page and flow editor, with a [Flow templates](https://navixy.com/docs/user/guide/account/iot-logic/quick-start-guide/templates.md) gallery that creates a ready-made flow from a template card. Reduces the entry barrier of flow creation.
* [Geofence functions](https://navixy.com/docs/user/guide/account/iot-logic/nodes/geofence-functions.md) in the Logic node. `inGeofence()`, `enterGeofence()`, and `leaveGeofence()` let flow logic branch on whether a device is inside a geofence, has just entered or left it.
* Support for including a device in several enabled [flows](https://navixy.com/docs/user/guide/account/iot-logic/flow-management.md) at the same time, so separate processing scenarios no longer have to be combined into one flow.
* [Nodes](https://navixy.com/docs/user/guide/account/iot-logic/nodes.md) configuration dialog moved from the canvas into a side panel. Now the flow remains wisible while editing a node.
* A [device mapping table](https://navixy.com/docs/user/guide/account/iot-logic/flow-management.md#mapping-table) in the flow interface that enables quick lookup of device distribution between flows.
* The **Use times** option is removed from the [Initiate Attribute node](https://navixy.com/docs/user/guide/account/iot-logic/nodes/initiate-attribute-node.md). `genTime()` and `srvTime()` remain available inside formulas, only the automatic introduction of these values is gone. Values previously declared through **Use times** are skipped.
* [Data Stream Analyzer](https://navixy.com/docs/user/guide/account/iot-logic/data-stream-analyzer.md) indicators showing attributes for commands from Device action or Webhook nodes dispatched during flow processing. The indicator confirms node execution, not delivery to an external destination.
* Removed the visible Default Flow from the flow list. [Default processing](https://navixy.com/docs/user/guide/account/iot-logic/flow-management/default-flow.md) continues to run automatically for devices that are not included in another flow.
* Flows can be exported and imported as files, so a configuration can be moved between accounts or kept outside the platform.
* Formulas are validated before a flow is saved, and errors are reported in the editor.
* The `device_label` attribute is available in flows, so a device label can be used in conditions and in outgoing payloads.
* BLE data packets are available to flows and distinguishable in Data Strem Analyzer.

</details>

The lists below cover new integrations and devices, platform improvements, and bug fixes.

<details>

<summary>Integrated</summary>

### **Iridium SBD**

Iridium Short Burst Data (satellite data transport) lets a device report over the Iridium satellite network where there is no cellular coverage. Navixy can now receive SBD tracking data for supported Teltonika and Galileosky integrations, and supported output-control commands can use the satellite channel when the last connection from the device came in over SBD. Devices on satellite networks are activated manually, as described in [Activate GPS device](https://navixy.com/docs/user/guide/quick-start/activate-gps-device.md).

### Devices

| Manufacturer             | Device                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   | Type                                                                                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Assistant Telematics** | [AVT80](https://navixy.com/devices/assistant-telematics/assistant-telematics-avt80/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | Vehicle GPS device                                                                                                                              |
| **Ford**                 | [Ford Pro](https://navixy.com/docs/user/guide/quick-start/activate-oem-device.md)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | OEM telematics for vehicles with FordPass Connect. Requires a data feed prepared by service provider, contact Navixy support before activating. |
| **Xirgo Global**         | [LX41](https://navixy.com/en/devices/xirgo-global/xirgo-lx41-mqtt-iotm/), [LX42](https://navixy.com/en/devices/xirgo-global/xirgo-lx42-mqtt-iotm/), [LX43](https://navixy.com/en/devices/xirgo-global/xirgo-lx43-mqtt-iotm/), [LX44](https://navixy.com/en/devices/xirgo-global/xirgo-lx44-mqtt-iotm/), [LX45](https://navixy.com/en/devices/xirgo-global/xirgo-lx45-mqtt-iotm/), [XG37 One](https://navixy.com/en/devices/xirgo-global/xirgo-xg37-one-mqtt-iotm/), [XG37 Light](https://navixy.com/en/devices/xirgo-global/xirgo-xg37-light-mqtt-iotm-2/), [XG37 Light+](https://navixy.com/en/devices/xirgo-global/xirgo-xg37-light-mqtt-iotm/), [XG37 Tacho](https://navixy.com/en/devices/xirgo-global/xirgo-xg37-tacho-mqtt-iotm/), [XG37 XtCAN](https://navixy.com/en/devices/xirgo-global/xirgo-xg37-xtcan-mqtt-iotm/), [XG47 CAN](https://navixy.com/en/devices/xirgo-global/xirgo-xg47-can-mqtt-iotm/), [XG47 RS232](https://navixy.com/en/devices/xirgo-global/xirgo-xg47-rs232-mqtt-iotm/) MQTT/IOTM profiles | Vehicle and asset GPS device profiles                                                                                                           |
| **Inmosat**              | Carfindersat                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Satellite GPS device                                                                                                                            |
| **Jimi IoT (Concox)**    | JC171                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | GPS device                                                                                                                                      |
| **Megastek**             | S921                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | GPS device                                                                                                                                      |
| **Micodus**              | [ML300](https://navixy.com/en/devices/micodus/micodus-ml300/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | GPS device                                                                                                                                      |
| **Navtelecom**           | SIGNAL S-4751, SIGNAL S-4753                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Vehicle GPS devices                                                                                                                             |
| **Qianfeng**             | J16                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | GPS device                                                                                                                                      |
| **Queclink**             | GV30CAU                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | Vehicle GPS device                                                                                                                              |
| **RAMAC**                | AT1L                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | GPS and LBS device, connected via [NGP](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol.md)                          |
| **SEEWORLD**             | [R16](https://navixy.com/devices/seeworld/seeworld-r16/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | Vehicle GPS device                                                                                                                              |
| **Suntech**              | [ST390](https://navixy.com/en/devices/suntech/suntech-st390/), ST419, SD8000U, ST4230, ST4280, ST4315B, ST6952, ST8210P, ST9730B                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | GPS devices                                                                                                                                     |
| **Teltonika**            | [ATC700](https://navixy.com/en/devices/teltonika-telematics/teltonika-atc700/), [ATM700](https://navixy.com/en/devices/teltonika-telematics/teltonika-atm700/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Asset GPS devices                                                                                                                               |
|                          | [FTC134](https://navixy.com/en/devices/teltonika-telematics/teltonika-ftc134/), [FTM134](https://navixy.com/en/devices/teltonika-telematics/teltonika-ftm134/), FTC164, FTM164, [FTC920](https://navixy.com/en/devices/teltonika-telematics/teltonika-ftc920/), [FTC924](https://navixy.com/en/devices/teltonika-telematics/teltonika-ftc924/), [FTC927](https://navixy.com/en/devices/teltonika-telematics/teltonika-ftc927/), [FTC965](https://navixy.com/en/devices/teltonika-telematics/teltonika-ftc965/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           | Vehicle GPS devices                                                                                                                             |
| **ThinkRace**            | [PT400HT](https://navixy.com/en/devices/thinkrace/thinkrace-pt400ht/), [MT4](https://navixy.com/en/devices/thinkrace/thinkrace-mt4/), [TR40](https://navixy.com/en/devices/thinkrace/thinkrace-tr40/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | Wearable and personal GPS devices                                                                                                               |
| **ATrack**               | [AK300](https://navixy.com/en/devices/atrack/atrack-ak300/)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Vehicle GPS device                                                                                                                              |
| **X3Tech**               | XT40                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | GPS device                                                                                                                                      |

</details>

<details>

<summary>Improved</summary>

* **General Platform improvements**
  * Reimplemented the [Navixy Admin Panel](https://navixy.com/docs/admin/overview.md), [Reports](https://navixy.com/docs/user/guide/reports.md), and the device activation wizard on the current Navixy frontend stack. Existing functionality and screen layouts are preserved, so operators do not need to relearn these sections.
  * Hidden and deleted devices no longer count toward an account's device quota.
  * Raised password strength requirements and widened the set of accepted special characters. A new password now must be 12-20 characters long, combine uppercase and lowercase letters, digits, and one special character. It cannot repeat any of the last 10 passwords used on the account.\
    Existing passwords are not affected.
  * Devices can now be found by tag in the device picker, not only by name, which narrows long device lists faster.
  * The service task list is no longer limited to 1,000 entries. Accounts with more tasks can now view, print, and export the full list.
  * Added CSV export of a user's GPS devices to the user details card in the Navixy Admin Panel.
* **Tracking and data**
  * NWS retranslation now identifies devices by their External ID instead of the internal Navixy device ID, so the receiving system can match devices by your own identifier.
  * KML geofence import was reworked and now imports circular geofences, which previously could not be created from a KML file.
  * Added the last connection time to the tracking CSV export.
  * Measurement and aggregation sensor accuracy now accepts decimal values such as 0.25, instead of rounding to whole units.
  * Corrected battery charge readings for devices that report both a percentage and a voltage. When a device sends a percentage and the charge scale of its model is declared in volts, the platform now converts the reported value into that scale instead of showing the two on different scales. Battery level and battery voltage are also handled separately across device protocols now.
  * Improved loading when editing Geo links that contain many GPS devices.
* **Reports and notifications**
  * Geofence and POI names are now hidden in trip report addresses by default. Enable **Include POI in location address** and **Include geofence in location address** in the [report parameters](https://navixy.com/docs/user/guide/reports/specific-report-details/trip-report.md) to display them.
  * Adopted a new naming convention and format for tachograph DDD files.
  * Converted values in sensor range rule notifications to the account measurement units.
  * Scheduled reports with large device or employee selections now save reliably, where saving could previously fail.
* **Devices and protocols**
  * Added vibration alarm decoding for GT06N devices, so a vibration event can raise a harsh driving alert or an accident report.
  * Added driver identification from an external serial card reader on Suntech devices, so a reader such as the Jmak JM15 can be used to identify drivers.
  * Added hardware mileage input for Jimi VL111.
  * Added engine hour data for Assistant Telematics AVT50.
  * Added ignition reading and immobilizer status and control for Dunasys DCAR S.
  * Added harsh driving support for Gosafe G1C+ and G1C+ 5W.
  * Added humidity and temperature parameters for Megastek MT60Pro.
  * Added reading of ANT battery management system data from electric vehicles.
  * Updated SinoTrack ST906 support after the manufacturer moved from protocol V1 to V8.
  * Corrected the monitoring mode scheme for Concox and Jimi models and their clones.
  * Updated Navtelecom manufacturer and model names to use Latin characters.
  * Split Jimi JC400, JC400D, and JC400P activation profiles for firmware earlier than 1.6.3 and firmware 1.6.3 or newer.
  * Teltonika FMC150 is now activated per hardware variant, FMC150-QJIB0 (2 Digital Outputs) or FMC150-QKIB0 (3 Digital Outputs), instead of one generic profile, so output settings match the device.

</details>

<details>

<summary>Fixed</summary>

* **Security and access control**
  * Fixed users being able to see geofences outside their access scope.
  * Fixed alert emails still being sent after the notification address was removed.
* **Devices and protocols**
  * Fixed devices connecting over UDP no longer sending data.
  * Fixed data from Galileosky 10 not being decoded, and missing temperature values for Galileosky 7x.
  * Fixed Globalstar SmartOne data not being processed.
  * Fixed missing location data from the Xexun GPS Ankle DDX14.
  * Fixed Digital Matter Eco5 Lite sending heartbeats without location data.
  * Fixed ACK handling and the `getio` command for Ruptela Pro5 Lite.
  * Corrected the SERVER auto-configuration command for Jimi VL802 and the tracking mode command for Jointech JT710D.
  * Corrected input mapping for Teltonika [FMC125](https://navixy.com/en/devices/teltonika-telematics/teltonika-fmc125/) and [FMC225](https://navixy.com/en/devices/teltonika-telematics/teltonika-fmc225/).
  * Corrected the number of available discrete inputs for Suntech ST8300V to 5.
  * Corrected the battery reading for Suntech ST4290 and battery value mapping for Jimi JM-LL301, JM-LL302, and JM-LL303.
  * Fixed missing cellular network information for Suntech ST300.
  * Restored the Bluetooth information block for Jimi JM-LL301.
  * Fixed false digital input and output states on Queclink GV305CEU.
  * Corrected accessory event decoding for Queclink GV50CEU and GV30CEU.
  * Fixed Jointech JT709A points being incorrectly classified as LBS positions.
  * Fixed false rule triggering for Arnavi and Autolink devices.
  * Removed imprecise hardware mileage from Assistant Telematics AVT models. GPS mileage is the recommended odometer source for these models.
  * Fixed Satsol and Fleetguide activation failing with a password error.
  * Fixed Output control addressing outputs by their position in the widget instead of their real output number.
  * Fixed device replacement failing for supported models, and allowed replacement of devices that are only just registered.
* **Tracking, geofences, and alerts**
  * Fixed duplicate geofence exit events being generated for one departure.
  * Fixed alert notification links opening the wrong map.
  * Fixed false Driving Time alerts caused by parking detection.
  * Fixed the odometer not updating promptly.
  * Fixed valid fuel sensor readings being discarded by data filtering.
  * Fixed date range arrows not moving the selected period in Tracking.
  * Fixed missing History events when many GPS devices were selected.
  * Fixed route colors not updating after changing the ranges used by **Color by speed**.
  * Fixed an error caused by clicking a parameter already displayed in the object widget.
  * Fixed temperature values shown with duplicated unit labels.
* **Reports and exports**
  * Fixed the end point of a trip being reported in the wrong region.
  * Fixed tachograph DDD downloads returning incomplete vehicle data.
  * Fixed device data downloads failing or producing incomplete files.
  * Fixed the first page of the Geofences report not displaying, on screen and in the downloaded PDF.
  * Fixed the date order on the Overview mileage chart.
  * Fixed the sensor calibration chart being cut off.
  * Fixed maintenance works not appearing correctly when sorted by creation date.
  * Fixed malformed negative task and stay durations in downloaded forms.
  * Fixed bulk image download failing in File manager.
  * Fixed the Geo link map preview not being displayed.
* **Accounts and access**
  * Fixed sub-user roles that could not be changed, and the Menu editor not reflecting changes made to templates.
  * Fixed user data not updating after a user was transferred between accounts.
  * Fixed user guide requests submitted from the platform interface not reaching their recipients.
* **Field service**
  * Fixed field service tasks that could not be completed or have their status changed.
  * Fixed field service PDF export failing when the browser blocks pop-ups, and the broken download link in employee invitations.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/on-premise/versions/2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
