This page provides a list of ZentriOS variables with a full description of the function of each variable together with example usage.
Variables are cached in volatile RAM and must be saved to non-volatile flash memory to persist between reboots. To save variables to flash, use the save command. Some variables impact the operation of the entire system, wake and sleep timers for example. A save and reboot is required before new settings for these types of variables take effect.
The get and set Command API functions are used to read and write ZentriOS variables respectively.
A shortcut is assigned to each variable. The format for shortcuts is shown in the following table. The shortcut is a hybrid of the first two characters of the first word of the variable name, plus (typically) the first character of the second word (if a second word exists), plus (typically) the first character of the third word of the variable name (if a third word exists). Each of these characters is separated by a space character. In some instances, it was not possible to use the first letter of the second or third word in the variable name, in these cases another letter has been somewhat arbitrarily chosen.
|Template||first_word.second_word.third_word||fi s t|
|Example 1||time.uptime||ti u|
|Example 2||wlan.scan.retries||wl s r|
Many ZentriOS responses shown in the examples on this page were captured with system.print_level = 0, and system.cmd.header_enabled = 1. These machine friendly settings make it easy for a host MCU to parse responses by examining response headers. Documentation for each variable is provided in the format shown below.
A description of the function of the variable.
A full list of mandatory and optional arguments.
The factory reset default value.
An example of how to read the variable, including response codes.
An example of how to write the variable, including response codes (for writeable variables).
NOTE! Don't forget to check out command navigation tips to make it easier to find and type specific variable names.
List of Variables
- All Variables
- HTTP Server
- IO Connection
- Remote Terminal
- SoftAP Interface
- TCP Client
- TCP Keepalive
- TCP Server
- UDP Client
- WLAN Interface
The table below indicates properties of variables:
- When a change in variable value takes effect:
Immediate- a change in the variable value takes effect immediately
uart_update- run the uart_update command to apply a change in the variable value
Network Restart- restart the network to apply a change in the variable value
Setup Restart- restart the web setup to apply a change in the variable value
Save/Reboot- a save and reboot is required to apply a change in the variable value
Safe Mode- variable is available in safe mode