Change one thing on every unit that has it.

Two tools for the fleet-wide edits Wialon makes you do one unit at a time: Counter Sync sets each odometer from that unit's own mileage sensor, and Sensor Manager renames or deletes a sensor across every unit that carries it.

Fleet Config after scanning every unit that carries the odometer sensor — sensor reading, stored odometer and the difference — with three rows ticked for writing, then its sensor manager staging a rename of the ACC sensor across 36 units

What it fixes

  • Copying a template and editing one property are different jobs

    Import from WLP moves whole blocks between units. Renaming a sensor that already exists on three hundred units has to change it in place.

  • A sensor belongs to a unit, so a rename is N edits

    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.

What it does

  • Counter Sync

    Switches the counter to mileage-sensor mode and sets the odometer from that unit's own reading.

  • Sensor Manager

    Finds every unit carrying a sensor and renames or deletes it across all of them at once.

  • Preview, then write

    Every tool reads first and shows the exact units and values it would change.

  • The preview is the instruction

    Writes send the IDs the preview displayed, so a sensor changed in between cannot be caught up in it.

  • One unit's failure stays with it

    Wialon's batch call reports the unit it refused by name and the run continues.

  • No credential of its own

    The deployment holds no token: writes happen as the signed-in user, with that user's rights.

What it costs

The same two numbers the homepage states: free on the Wialon Marketplace under our name, $500 a month per application under your brand.

  • Wialon Marketplace

    Free

    The application on the Wialon Marketplace, at no charge, under our name.

    • Counter Sync and Sensor Manager across every unit in the account
    • Every write previewed first, and only the previewed list applied
    • Runs on the Wialon account or token you already have
  • White-label

    $500 / month

    The same application under the partner's brand, colours and domain, from the login screen on. Priced per application, per month.

    • The partner invoices their own customer, at whatever price they set
    • Nothing about the application changes for that customer
    • Start with one and add the others as they sell

How to open it

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.

  • Option A: Sign in with Wialon credentials

    1. 1. Open the app.
    2. 2. Choose your Wialon server.
    3. 3. Sign in with Wialon, using Wialon's own login.
  • Option B: Register it in the Apps configurator

    1. 1. In Wialon CMS Manager, create a new application.
    2. 2. Point it at the URL below and enable the listed advanced URL parameters.
    3. 3. It then opens from inside Wialon with the session already established.
    Advanced URL parameters
    Active SID · Host URL · Current user · Base URL · Authorize hash

FAQ

How is this different from Wialon's export and import?

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.

Does it actually write to Wialon?

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.

Can a change be undone?

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.

What happens if Wialon rejects one unit?

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.

Do you store our Wialon token?

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.

Can we run it under our own brand?

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.

Related

Let's connect

  • “Our client needed a data pipeline. It came back working, plus a few Wialon fixes we had not asked for. That client trusts us more now.”
    Faiz K. Customer Manager · Trakpro Limited