> 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.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](/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**](/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](/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](/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.
What became available in this release
### Bringing external data in
The **Software** tab in the [Data Source node](/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](/docs/iot-logic-api/navixy-iot-guide/merging-external-data-into-a-flow.md).
### Sending data out
The new [Webhook node](/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](/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](/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](/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](/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](/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](/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](/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](/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](/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.
The lists below cover new integrations and devices, platform improvements, and bug fixes.
Integrated
### **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](/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](/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](/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 |
Improved
* **General Platform improvements**
* Reimplemented the [Navixy Admin Panel](/docs/admin/overview.md), [Reports](/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](/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.
Fixed
* **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.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://navixy.com/docs/on-premise/versions/2026.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.