Saving AWS certs in ELS81 EV kit using AT cmds. | Telit Cinterion IoT Developer Community
January 8, 2019 - 2:25pm, 6234 views
Hi
I have successfully connected to our server and download the certs which are required to make connection with the AWS IOT. Now I need to save and install this certs into the modem so I need some documents or help to do this using AT commands only.
Our customised board will have MCU and this modem to make connection to the AWS .
There will be no connection to PC so the given examples below are of no help:
https://iot-developer.thalesgroup.com/showcase/concept-board-connection-...
https://iot-developer.thalesgroup.com/tutorial/internet-services-ssltls
My Board details are:
ati1<\r>
<\r><\n>Cinterion<\r><\n>
ELS81-E<\r><\n>
REVISION 04.000<\r><\n>
A-REVISION 01.000.03<\r><\n>
Kindly guide.
Regards,
SS
Hello,
It might mean that there is a problem with certificates. Have you also checked the scenario with AT commands - with additional diagnostic commands before AT^SIST command?
I think that it would be easier to say anything more if you could provide us the certificates and connection address so that we could try to connect. You could do it via Gemalto support.
Regards,
Bartłomiej
Hello,
Thanks for all the help!!
I am able to connect to aws IOT and can see the data published on channel "test/004401082448966".
Can you tell me how to interact with the thingsname shadow?
I have to read as well as modify the shadow content.
I have tried with
but nothing updates on shadow.
Regards,
SS
Hello,
Please try in this order (message first and topin as second parameter):
at^sjmqtt="PUB","{ \"state\": {\"desired\": {\"device\":{\"status\": \"request\"}}}} ","$aws/things/001WV7PRTOZA/shadow/update"
Regards,
Bartłomiej
Hi
I have tried this but its not working.
Do I have to include imei or something to update or read from shadow?
Because in case of channel I have to include imei "test/004401082448966" to see the data.
Regards,
SS
Hello,
I'm not really MQTT expert and I don't know where this IMEI come from in the channel name (if it's added by AWS or this demo MQTT application) but I was able to find the message published by my module on '$aws/things/001WV7PRTOZA/shadow/update' channel on '$aws/things/001WV7PRTOZA/shadow/update/004401081941722'.
Regards,
Bartłomiej
Hello,
This IMEI is added by the demo MQTT application and not by AWS.
We can interact with the shadow using reserved topics which I can not edit.
There must be some other way to interact to this thing shadow.
Regards,
SS
Hello,
I have looked at the code of ATSJMQTT and the IMEI number (which is treated as client ID) is indeed added to the topic name when publishing messages.
In my previous test it worked - the application on the module has published to topic '$aws/things/001WV7PRTOZA/shadow/update' and on MQTT.fx client I was able to read this published message from topic '$aws/things/001WV7PRTOZA/shadow/update/004401081941722'.
This is a demo app and that's how it works. It may not fit your *****. It's built on MQTT libraries which you can find in this article: https://iot-developer.thalesgroup.com/showcase/paho-project-110-july-201... So I think that if you are interested in using such a solution instead of your previous one you may need to build your own app based on these MQTT libraries. You may also try to ask the author of these demos for a hint or source code.
Regards,
Bartłomiej
Thank you for all your great advice here Bartlomiej!
I think my original version of the "AT^SJMQTT demo" was wrong to be appending the ClientID to each MQTT Publishing Topic; I have recompiled it to Publish to Topics exactly as there were intended, by the user, with no ClientID appended.
Best regards
Simon