ProductTwo tools for the fleet-wide configuration edits Wialon makes you do one unit at a time: Counter Sync, which sets each unit's odometer from its own mileage sensor, and Sensor Manager, which renames or deletes a sensor across every unit that carries it. Both write to Wialon, so both read first and show the exact units and values they would change. The write applies that list and nothing else.
Configuration moves between units through Export to WLP and Import from WLP, and the export options are whole blocks: Counters, Sensors, Eco driving, Custom fields. That is what you want when setting up a new unit like an existing one. Renaming a sensor that already exists on three hundred units, each with its own settings, is the other job: the property has to change in place.
Sensors are configured in a unit's own properties. There is no fleet-level sensor to rename once, so a naming cleanup across a large account is measured in hours of opening unit cards.
Fleet operators whose sensor naming drifted as the fleet grew, and who now hold the same measurement under three different names across a few hundred units.
Wialon partners doing onboarding and cleanup work, where the same configuration change has to land on every unit in an account rather than on one.
Switches the mileage counter to mileage-sensor mode and sets the odometer to that sensor's latest reading, per unit, from that unit's own data. The engine-hours and auto-calc bits are preserved.
Finds every unit carrying a sensor and renames or deletes it across all of them in one action.
Every tool reads first and shows the exact list of units and values it would change. The write applies that list and nothing else.
Writes send the exact unit and sensor IDs the preview displayed, not a name for the server to resolve again. A sensor created or renamed between preview and click cannot be caught up in the change.
Changes go through Wialon's batch call, so a unit Wialon refuses is reported by name and the rest of the run continues.
The deployment holds no token. Writes happen as the signed-in user, with the rights that user has in Wialon.
Searched from your account, with the change scoped to the selection you make.
Matched across units by name, so a measurement recorded under one label everywhere can be found and changed everywhere.
The mileage counter, its calculation mode and the odometer value, read before the write and shown in the preview.
There is no account to create here. Either sign in against your Wialon server, or register the app in the CMS so it opens from Wialon already authenticated. Either way the writes happen as you, with your Wialon rights.
Search your fleet and select what the change should apply to.
Every affected unit is listed with what it holds now and what it would hold after. Nothing is written at this point.
The write goes through in a batch. Units Wialon accepts are changed, and units it refuses come back named, with the reason.
Fleet Configuration Tools ships white-label. Partners doing onboarding and cleanup often run it internally rather than putting it in front of customers.
They do different jobs. Export to WLP copies a source unit's configuration onto other units, which is what you want when setting up a new unit like an existing one. When one property has to change on units that already have their own settings, copying a whole sensor block over would replace the rest of it, so these tools edit the property in place instead.
Yes. Counter Sync calls unit/update_calc_flags and unit/update_mileage_counter, and Sensor Manager calls unit/update_sensor. Each is preceded by a preview showing which units and values are involved.
A rename can be reversed by renaming back. A sensor deletion cannot: it is permanent in Wialon. The preview exists so that decision is made before the write.
That unit is reported by name with the reason, and the rest of the run continues. A single refusal does not roll back or abort the rest.
No. The session belongs to the signed-in user. The deployment holds no credential of its own, so it can never do more than the person using it is allowed to do.
Yes, under your brand and domain, with the commercial relationship yours. Partners often run it internally for onboarding and account cleanup rather than putting it in front of customers.
Audit Wialon unit properties, sensors, hardware parameters, and eco-driving settings in Google Sheets with the open-source Wialon Auditor Apps Script.
Read moreHow FleetSQL began: a passion for telematics reports, years of customer feedback, and the path from one Python script to a full backend service.
Read moreHow a Wialon reseller launched a white-label fleet platform with phased delivery and controlled customization.
Read moreHow a regional distributor stabilized Wialon to ERP sync and eliminated manual reconciliation for delivery operations.
Read moreA fleet organization moved from static report exports to SQL analytics with governed metrics and daily data quality checks.
Read moreHelping businesses to make their fleets safer, teams more productive and processes more efficient.