Fleetrun
Hecterra
NimBus
Other apps
Wialon for Android/iOS
Logistics
Wialon Local
Wialon Hosting
WiaTag
Configurator
LeaseControl
Android
en
en ru es
Contents
Appendix 1

The Share configuration option in the administrative settings of the application allows configuring some settings remotely. To do this, a text file in the JSON format containing the required configuration should be attached to the command. 

The configuration file consists of the "key":value pairs, where the key is a setting of the application, and the value is the configuration of the setting. Below is the list of keys and their configurations.

KeySettingValue
data_collection_modedata collection0 — continuous, 1 — by timeout, 2 — smart mode
data_collection_timeoutdata collection timeoutcustom value, min
motion_detectorsmotion detection0x1 — activity recognition, 0x2 — accelerometer, 0x4 — Wi-Fi, 0x8 — GSM, 0x10 — motion sensor
motion_detectors_timeouttimeout for motion detectioncustom value, min
detect_motion_continuouslydetect motion continuouslytrue — enable, false — disable
data_sending_modedata sending0 — continuous, 1 — by timeout, 2 — manual
data_sending_timeoutdata sending timeoutcustom value, min
send_data_in_roamingsend data in roamingtrue — enable, false — disable
auto_startupauto startuptrue — enable, false — disable
work_while_chargingwork while chargingtrue — enable, false — disable
work_by_schedulework by scheduletrue — enable, false — disable
schedulesadd scheduleThe key has nesting because you should specify the days of the week and intervals of the application operation. The keys of these parameters are described below.
time_frombeginning of the application operation intervaltime in the hh:mm format
time_toend of the application operation intervaltime in the hh:mm format
week_daysdays of the week on which the specified interval of the application operation should be applied1 — Monday, 2 — Tuesday, 3 — Wednesday, 4 — Thursday, 5 — Friday, 6 — Saturday, 7 — Sunday
location_sourcelocation source0 — Google Fused, 1 — GPS, 2 — WiFi+mobile networks, 3 — GPS+WI-Fi+mobile networks
enable_filtrationenable filtrationtrue — enable, false — disable
filtration_min_timemin time intervalcustom value, sec
filtration_min_distancemin distancecustom value, m (ft)
filtration_change_in_coursechange in coursecustom value, 0-360°
filtration_change_in_speedchange in speedcustom value km/h (mph)
filtration_max_accuracymax accuracycustom value, m (ft)
filtration_max_speedmax speedcustom value km/h (mph)
send_parameter_lbsadditional parameters, LBS datatrue — enable, false — disable
send_parameter_provider_nameadditional parameters,
provider name
true — enable, false — disable
send_parameter_accuracyadditional parameters, accuracytrue — enable, false — disable
send_parameter_battery_leveladditional parameters, battery leveltrue — enable, false — disable
send_parameter_last_statusadditional parameters, last statustrue — enable, false — disable
enable_action_send_photoactions menu adjustment, sending phototrue — enable, false — disable
enable_action_send_positionactions menu adjustment, sending positiontrue — enable, false — disable
enable_action_send_sosactions menu adjustment, sending SOStrue — enable, false — disable
visible_statisticsvisible settings0x1 — time, 0x2 — speed, 0x4 — altitude, 0x8 — course, 0x10 — location, 0x20 — accuracy
user_modeuser modeTo prevent errors when loading the configuration, it is not recommended to change the user mode at the same time as changing the user settings. If both modifications are required, you must first upload the configuration with the user mode changes, and then the one with the user settings.
0 — active, 1 — standard, 2 — lite, 3 — custom
use_admin_passwordadmin passwordtrue — enable, false — disable
admin_passwordset admin passwordany numeric and alphabetic value
photo_qualityphoto quality0 — original, 1 — high, 2 — medium, 3 — low
enable_debug_modedebug modetrue — enable, false — disable
power_save_mode_at_low_batterypower save mode at low batterytrue — enable, false — disable
enable_power_save_modepower save modetrue — enable, false — disable
statusescustom statusesThis key has nesting because the template of the arbitrary state includes several settings. Available settings are described below.
namethe name of the templatecustom value
param_namethe name of the parametercustom value
valuesvaluesCustom values. The maximum number of values is 6. Each value is indicated in double quotation marks (for example, "Value1"). A comma (,) is used to separate values.
activeuse the template from the main screentrue — enable, false — disable
visible_settingsvisible settingsThis key has nestings because it is necessary to specify a section of visible settings as well as a value. All the possible values for each section are listed below.
connection_settingsconnection settings0x1 — server, 0x2 — unit properties
operation_modeoperation mode0x1 — data collection, 0x2 — data sending, 0x4 — start/stop by event
data_settingsdata settings0x1 — location source, 0x2 — filtration, 0x4 — additional parameters
main_screen_customizermain screen0x1 — latest data, 0x2 — actions
administrative_settingsadministrative settings0x1 — user mode, 0x2 — admin password, 0x4 — custom statuses, 0x8 — remote control, 0x20 — notifications, 0x40 — photo quality, 0x80 — debug mode, 0x100 — power save mode, 0x200 — clear black box, 0x400 — reset, 0x800 — NFC reader
other_itemsother parameters0x1 — contact us, 0x2 — help, 0x4 — measurement system

Keys can have numerical (0, 1, 2, etc.), alphabetical (true/false) values or such values as 0x1, 0x2, 0x20, etc. The latter is specified as a key only after conversion to the decimal number system. For example, if you want to display such parameters as Contact Us and Help in the user menu, you need to sum up their values ​​(0x1 + 0x2 = 0x3), convert the sum into a decimal number system and specify the result as the value of this key. Numeric and text values are used to select one parameter or state. 

Example of a configuration file for visible settings:


"visible_settings":{
"connection_settings":1,
"operation_mode":1,
"data_settings":4,
"main_screen_customizer":0,
"administrative_settings":2,
"other_items":2
}


Example of a configuration file for work by schedule:

"work_by_schedule":true,"schedules":[{"time_from":"0:05","time_to":"1:00","week_days":[2,3,4]},{"time_from":"0:00","time_to":"3:00","week_days":[1,7]}]

If you find a mistake in the text, please select it and press Ctrl+Enter.
Thank you for your feedback!
Report a mistake
Text with the mistake Comment
Maximum 500 characters