Thank you…
It sure seems like there is a lot of opportunity here to enhance the AT interface to let you do a lot more.
I understand that this AT interface is proprietary… and they want to protect the work that went into creating it… but not being able to update it to future versions that are more capable seems like a very limiting view.
For example: This device absolutely can support SigFox. It seems very reasonable to me that a future AT command set could be added to let them device operate on SigFox… and yet all of the hardware being shipped seems forever doomed to not be able to do that under the AT structure.
So on one hand, you have this easy to use AT interface, but no ability to use any of the other IO capabilities of the platform, or you have to jump all the way into doing fairly deep embedded development.
Someone is likely to make from scratch a load for the AT library… which would then completely replace the investment that is being protected by this pollicy…