Config Manager does the fleet-wide edits Wialon makes you do one unit at a time. Two tools today: 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. Unlike the rest of this family it writes to Wialon — so every tool reads first, shows exactly what it would change, and writes only what the preview displayed.
A sensor found across every unit that carries it, ready to rename or remove.
After the write: what went through, and what Wialon refused and why.
Every claim below is published by the platform vendors themselves. Follow the links.
The documented way to move configuration between units is Export to WLP and Import from WLP, and the export options are whole blocks — Counters, Sensors, Eco driving, Custom fields. That copies a source unit's configuration onto targets, which is the right shape for cloning a new unit and the wrong one for renaming a sensor that already exists on three hundred units with different settings each.
help.wialon.com — transferring unit propertiesSensors are configured in a unit's own properties. There is no fleet-level sensor to rename once and have it take everywhere, which is why a naming cleanup across a large account is measured in hours of opening unit cards rather than in one action.
help.wialon.com — sensorsFleet operators whose sensor naming drifted as the fleet grew, and who now have the same measurement under three 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 rather than overwritten.
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 swept up in the change.
Changes go through Wialon's batch call, so a unit Wialon refuses is reported against that unit instead of taking the rest of the run down with it.
It holds no token. The write happens as the signed-in user, with exactly 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.
Authenticate on Wialon's own login page, or paste a Wialon API token. There is no separate account here.
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 has been written yet.
The write goes through in a batch. Units Wialon accepts are changed; units it refuses come back named, with the reason.
Config Manager ships white-label. For a partner doing onboarding and cleanup it is an internal tool as often as a customer-facing one.
Export to WLP copies a source unit's configuration onto other units. That is the right tool for setting up a new unit like an existing one. It is the wrong tool for changing one property on units that already have their own settings — copying a sensor block over would replace everything else in it. Config Manager edits what is there instead of overwriting it with a template.
Yes, and that is the point — it is the only app in this family that does. Counter Sync calls unit/update_calc_flags and unit/update_mileage_counter; Sensor Manager calls unit/update_sensor. Each is preceded by a preview showing exactly 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 rather than after.
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 others.
No. The token is the signed-in user's own Wialon session. The deployment holds no credential, which also means it can never do more than the person using it is allowed to do.
Yes. Your brand and domain, your commercial relationship. 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.