You see one of these:
- The import wizard refuses the file with "Please select a valid JSON file", "File Parse Error" or "No Configurations Found".
- A unit you want to import into is greyed out in Destination Object.
- The Import Summary dialog says "N devices imported successfully, M failed." and lists the failed units.
- On the Migration of units from Wialon screen, a unit stays "Not imported", or its log shows an error.
Import, export and migration are for dealer accounts. A user in a consumer account who opens them sees "Un-authorized action".
- The file is not a configuration export
- The destination devices are from another manufacturer
- Some units failed in the import summary
- A part was skipped because the destination lacks a sensor
- A Wialon unit failed to migrate
- The Wialon connection no longer works
| Message |
Cause |
| "Please select a valid JSON file" |
The file name does not end in .json and its type is not JSON. |
| "File Parse Error" |
The text is not valid JSON, for example after someone edited it by hand. |
| "No Configurations Found" |
The file has no settings: configurations is missing or empty. |
Fix
- Export the source unit's configuration again. See Export a unit's configuration to a file.
The file name starts with export_.
- Import the new file without opening it in an editor.
A report template file is a different kind of file; import it on the Report templates screen. See Share, import, export and delete templates.
A file fits only units whose device has the same manufacturer as the source. Destination Object greys out every other unit, and you cannot choose them.
Check
- Compare the destination device's manufacturer with the source unit's.
Fix
- Export a configuration from a unit with the same manufacturer as the destination.
- Or set up the destination's sensors by hand. See Copy sensors between devices.
The file does not name a model. After an import, check that the sensors' parameters exist in the destination device's messages.
An import to several units writes one unit after another. A failure on one does not stop the others. The Import Summary dialog gives the server's reason for each failed unit.
Fix
- Read the reason on each failed line.
- Select Close.
- Fix the cause on those units.
- Import again for those units only.
See Import a configuration file into units.
Some parts of a file need a sensor on the destination. Without it, the app skips that part for that unit and imports the rest:
| Part |
Needs on the destination |
| Trip detector and filters |
A GPS sensor |
| Fuel settings |
A FUEL sensor |
| Commands that start and stop a video stream |
A VIDEO_STREAM sensor |
Fix
- Add the sensor to the destination device, or tick the sensors in the import so the file brings them.
- Import again.
See Configuration file format and import modes.
A unit that failed shows "Not imported" and a log with the reason. Common reasons:
- The unit name is outside the device name limit of 3 to 50 characters.
- Some Wialon sensor types have no match. The app skips them and lists them in the log under "Unsupported sensors". The unit itself still imports.
Do not rely on the counts in "Migration Completed". Check Migration Status for each unit.
Check
- In the unit's row, select Check Logs.
- Read the error at the end of the log.
Fix
- Fix the cause in Wialon, for example rename the unit.
- Import the unit again.
The app skips a unit marked "Imported", so nothing doubles up.
- Add unsupported sensors by hand in the app. See Add a sensor.
See What a Wialon migration brings across.
The app keeps your Wialon access after you connect. If imports fail for every unit and the logs point at the connection to Wialon, connect again.
Fix
- On the Migrate data screen, select Disconnect Account.
The row shows "Not connected". The units the app already read stay in the list.
- Connect the Wialon account again.
- Import the units again.
See Migrate units from Wialon.
Contact support@getgps.eu with:
- The source unit and the destination units, or the Wialon unit names.
- The text of the Import Summary or the unit's migration log.
- When you ran the import, with your time zone.
Do not send the configuration file to anyone else; it describes how your units are set up.