SENSBLUE ATLAS/Datasheet: Difference between revisions
| Line 8,439: | Line 8,439: | ||
* Any SMS that does not match a known fixed or parameterized command is still reported over MQTT (<code>SMS_RECEIVED</code>) but no action is taken. | * Any SMS that does not match a known fixed or parameterized command is still reported over MQTT (<code>SMS_RECEIVED</code>) but no action is taken. | ||
* An SMS whose recognised lines are not all the '''same action''' (e.g. a relay command mixed with <code>reboot</code>, or with a digital output command) is treated the same way: reported via <code>SMS_RECEIVED</code>, but no command runs and no auto-reply is sent (see [[#c) Multiple commands per SMS|''<u>Multiple commands per SMS</u>'']]). | * An SMS whose recognised lines are not all the '''same action''' (e.g. a relay command mixed with <code>reboot</code>, or with a digital output command) is treated the same way: reported via <code>SMS_RECEIVED</code>, but no command runs and no auto-reply is sent (see [[#c) Multiple commands per SMS|''<u>Multiple commands per SMS</u>'']]). | ||
* Unlike the fixed commands, a parameterized command's auto-reply is only sent when the action '''succeeds'''. If it fails, no SMS reply is sent, but the failure is still published over MQTT (see e) | * Unlike the fixed commands, a parameterized command's auto-reply is only sent when the action '''succeeds'''. If it fails, no SMS reply is sent, but the failure is still published over MQTT (see [[e) Command result (parameterized commands)|Command result (parameterized commands)]]). | ||
'''Security note:''' there is currently no sender allow-list or authentication on inbound SMS commands. Any SMS with the exact matching text/pattern will trigger the corresponding action, regardless of sender. Restrict knowledge of the SIM number and treat it as a sensitive credential. | '''Security note:''' there is currently no sender allow-list or authentication on inbound SMS commands. Any SMS with the exact matching text/pattern will trigger the corresponding action, regardless of sender. Restrict knowledge of the SIM number and treat it as a sensitive credential. | ||