Version 5.4.4 of Pysae Driver will be rolled out on the Google Play Store from 2 November 2026. It will replace version 5.3.17-1, currently published. No service interruption is expected.
Version 5.4.4 succeeds version 5.4.3, provided for testing, and includes all of its changes.
This note presents the changes made since version 5.3.17-1 and the steps to follow depending on how your devices are managed.
đ Key information
Current version: 5.3.17-1
New version: 5.4.4
Distribution channel: Google Play Store
Availability: from 2 November 2026, as a gradual rollout
Service interruption: none
Action required: only if your deployment method does not automatically rely on the Google Play Store, or if you want to test the version in advance
⨠What's new in this version
Vehicle form at duty start: the duty start form can now be made mandatory. This mode is set in the operations interface; if the setting is left unchanged, the behaviour stays the same.
Dead-run route: the display of the route to the first stop becomes configurable for each network. It remains displayed by default.
WeBreathe boxes: dedicated connector for WeBreathe boxes connected over IP.
Android compatibility: compatibility maintained with the latest Android versions, up to Android 16.
đ What changes in how the app works
Some behaviours change with this version and may be noticed in the field as soon as it is installed:
AEP ticketing console, end-of-duty ticket: the duty stays open between two trips of the same duty. The end-of-duty ticket is printed only once, when the driver ends the duty in Pysae Driver, instead of one ticket at the end of each trip.
AEP console, off route: the last served stop is still sent to the console and ticket sales remain possible.
AEP console, identifier conversion: when CRC-16 conversion is set for an identifier, it is applied. The value sent to the console therefore changes for the networks concerned.
KUBA console (v8 protocol): the manual validator lock key remains available, during and outside trips.
On-board equipment: the IP address and port of each device are checked at startup. A device with an invalid configuration is not started. IRIS sensors and the router are only contacted on the vehicle's local network.
Automatic end of duty: it is triggered according to the network setting, on return to the depot and after the configured delay.
Duty start: a new duty starts in dead run, without taking over the previous driver's duty or trip. A driver changeover keeps the current duty.
Network change: the current duty on the network being left is closed.
Resuming after a restart: a trip is not resumed if its theoretical end time, delay included, is exceeded by more than 10 minutes.
Automatic start: a pending trip starts automatically at its first stop in both trip mode and sequence mode, including when the vehicle is parked next to the stop.
Sequence mode and diversions: diversions are taken into account at the first and last stop. A trip whose stops are all removed by a diversion is skipped in the sequence.
Android Back button: during a duty, it does not lead back to the duty start screens.
GPS positions: a position received more than 2 minutes after it was acquired is not used for tracking. This delay can be set per network.
Mileage: the distance between two position transmissions is fully counted. The kilometres shown may be slightly higher.
Reset: after several failures at startup, a reset button is offered. It deletes data that has not yet been sent.
Teams: trips assigned to an archived team remain visible.
Location permission: it is requested at most three times without an answer.
Fleet management (MDM): Android backup of the app data and technical inspection of the app are disabled.
đ Improved reliability
The reliability of the app has also been strengthened in many areas, including:
stop detection and trip progress, especially on loop routes and out-and-back routes;
automatic trip start and trip chaining, especially in sequence mode and during diversions;
automatic end of duty;
resuming the current trip after the app restarts;
the sequence of duty ends and duty starts, including offline and after an app restart;
GPS position filtering and tracking continuity, including in battery saver mode;
position transmission on a degraded network and optimised exchanges with the server;
GTFS data download and diversion updates;
the operation and link continuity of AEP and KUBA consoles, IRIS sensors and on-board connectors;
the security of connections to on-board equipment and data protection;
the display of the next stop and the calculation of the "off route" status;
the connection status and mileage calculation shown in the operations interface;
the display and filtering of duties by team;
the display of the device's network list;
driver code entry and navigation in the app;
app startup and network outage diagnostics.
đ˛ Steps to follow for your setup
Play Store without MDM: no action required. The update will be offered automatically from 2 November 2026. The rollout is gradual and random: some devices may receive it earlier than others, and this requires no action on your side.
MDM, Play Store version: update the application policy in your MDM console to allow the new version. Without this update, devices will stay on the current version.
MDM, Enterprise version: deploy the Enterprise APK from your MDM console (link below). This variant is not distributed through the Play Store.
For the detailed procedure, see our article Pysae Driver: how to get the new version?
𧪠Test the version before its rollout
You can install version 5.4.4 right now on a few test devices. It comes in two variants: install the one that matches the app already on your devices.
Standard version, the Play Store one, used by the vast majority of networks: download version 5.4.4. It is the same app as the Play Store one: it installs over it, with no uninstallation and no loss of configuration.
Enterprise version, reserved for fleets deployed by MDM with this variant: download version 5.4.4 Enterprise. Deploy it from your MDM console; it is not distributed through the Play Store and therefore does not update automatically.
If you have already installed test version 5.4.3, install version 5.4.4 over it, in the same variant.
đĄ Good to know: the two variants intentionally have different signatures and are two separate apps. Always install the variant already on the device, without switching from one to the other.
If you have any questions, your Customer Success contact and our support team are available: support@pysae.com