SMS Commands
When the SMS setup and configuration is complete, SMS features may be activated. Commands, depending on SMS configuration, are sent using a PIN or caller ID. The type of PIN depends on what is set for SMS Authentication.
The table below provides all available SMS commands. Subsequent action and response are also provided.
SMS Commands are sent as texts to the phone number of the SIM card on the controller.
For commands using a PIN, the format of the text is:
****.command or **** command
where **** is the PIN and “command” is the command, that is, the PIN followed by either a space or a full stop. For example, the command “FSET” is entered as: **** FSET or ****.FSET. The full version of the command, where listed, can also be used. For example, ****.FULLSET.
If the user does not have sufficient rights to perform a command, the system returns ACCESS DENIED.
If Caller ID is enabled, and the sender’s SMS number is configured, the PIN prefix is not required.
COMMANDS (**** = code)
Using Code |
Using Caller ID |
Action |
Response |
---|---|---|---|
**** HELP ****.HELP |
HELP |
All available commands are displayed. |
All available commands |
**** FSET ****.FSET ****.FULLSET |
FSET FULLSET |
Sets all areas the user has access to. |
Time/date of system set. If applicable, responds with open zones/force set zones |
**** ASET ****.ASET |
|
Allows Partset A of alarm by SMS. It is also possible to specify the custom name defined in the PARTSET rename field of the Options page. See Options. |
System set |
**** BSET ****.BSET |
|
Allows Partset B of alarm by SMS. It is also possible to specify the custom name defined in the PARTSET rename field of the Options page. See Options. For example: ****.ASET NIGHT |
System set |
**** USET ****.USET ****.UNSET |
USET UNSET |
Unsets all areas the user has access to. |
System Unset |
**** SSTA ****.SSTA ****.STATUS |
SSTA STATUS |
Retrieves the status of areas. |
Status of system and applicable areas
|
**** XA1.ON ****.XA1.ON |
|
Where X10 device is identified as “A1”, it is triggered on. |
Status of “A1” |
**** XA1.OFF ****.XA1.OFF |
|
Where X10 device is identified as “A1”, it is triggered off. |
Status of “A1” |
**** LOG ****.LOG |
|
Up to 10 recent events are displayed. |
Recent events |
**** ENGA.ON ****.ENGA.ON |
ENGA.ON |
Enable Engineer access. |
Allow Engineer |
**** ENGA.OFF ****.ENGA.OFF |
ENGA.OFF |
Disable Engineer access. |
Revoke Engineer |
**** MANA.ON ****.MANA.ON |
|
Enable Manufacturer access. |
Manufacturer status |
**** MANA.OFF ****.MANA.OFF |
|
Disable Manufacturer access. |
Manufacturer status |
**** O5.ON ****.O5.ON ****.OUTPUT |
|
Where output (mapping gate) is identified as “O5”, it is triggered on. |
Status of “O5” For example:
|
**** O5.OFF ****.O5.OFF |
|
Where output (mapping gate) is identified as “O5”, it is triggered off. |
Status of “O5” For example: Output O5 off |
****.CLR ****.RESTORE |
|
Allows clear alerts by SMS. |
|
For SMS recognition, output (mapping gate) identification uses the format ONNN, where O stands for output, and NNN are the numeric placeholders, of which not all are necessary. For SMS recognition, X-10 device uses the format: XYNN, where X stands for X-10; Y stands for the alphabetic identity and NN are the available numeric placeholders. (Example: XA1) |
The SMS operates using a standard protocol that is used in SMS telephones. Note that some PSTN operators do not provide the service of SMS over PSTN. For SMS to operate over PSTN, the following criteria are required:
-
Caller ID needs to be enabled on the telephone line.
-
Direct telephone line – not through PABX or other communications equipment.
-
Also note that most Service Providers only allow SMS to a telephone registered in the same country. (This is due to billing issues.)