01-28-2021, 12:53 PM
(This post was last modified: 02-12-2021, 08:30 AM by gReatAutomation.)
I found an issue with the SMS driver and was able to fix it.
Added:
The addition of CallerID will allow you to do many things, once of which is securing the processing of commands and restricting it based off of the CallerID value.
Added:
- SignalStrength - Calculated based on the RSSI
- CallerID - extracts the caller id from the SMS message and stores it. When you clear the NewMessage or NewCommand flag, the CallerID field will be blank.
- NewMessage - This was an existing a R/W Boolean field. When a new message (+M:MESSAGE) is received, this field will be True and you will see the message text in the ReceiveMessage field. The NewMessage field will remain True until you change it back to False, at which point the ReceiveMessage field will be blank
- NewCommand - This was an existing a R/W Boolean field. When a new command (+C:COMMAND) is received, this field will be True and you will see the command text in the ReceiveCommand field. The NewCommand will remain True until you change it back to False, at which point the ReceiveCommand field will be cleared out.
The addition of CallerID will allow you to do many things, once of which is securing the processing of commands and restricting it based off of the CallerID value.