Mqtt client Nrf9160 Module

RE: Mqtt client Nrf9160 Module

Øyvind — Wed, 27 Jan 2021 09:43:18 GMT

Hello,

I'm glad that you were able to fix this issue. I have reported the documentation bug to our NCS team.

Kind regards,
Øyvind

RE: Mqtt client Nrf9160 Module

Ukhan — Tue, 26 Jan 2021 05:12:28 GMT

Hi,

I could finally connect to AWS-IoT core on SLM.
There are issues with the slm application I suppose, but here is what I did that let me connect.

Updated Modem to latest fw.
Removed all the certificates that were there in the modem.
Flashed new certificates on the modem for the IoT thing created in AWS.
In AWS IoT Core, subscribed to all the topics mentioned below:

aws/things/uskh-n91/shadow/get/accepted
aws/things/uskh-n91/shadow/get/rejected
Aws/things/uskh-n91/shadow/update/accepted
aws/things/uskh-n91/shadow/update/delta
aws/things/uskh-n91/shadow/update/rejected
aws/things/uskh-n91/shadow/delete/accepted
aws/things/uskh-n91/shadow/delete/rejected

From LTE Link Monitor I sent the following commands:

AT+CFUN=1
AT+CFUN? (Queries all the configurations if automatic requests are enabled on LTE Link Monitor)

Now, once I see LTE is registered, I send the XMQTTCON and it responds with

2021-01-26T02:36:27.941Z DEBUG modem << OK
2021-01-26T02:36:28.621Z DEBUG modem << #XMQTTEVT: 0,0

Attached are the logs for your reference.

Now I haven't dug deep into the issue and it can be looked into further and fixed.

However, following those steps I could establish a connection and publish and subscribe to AWS via MQTT.

Please update the documentation here, like I mentioned before, that's very misleading, stating 0 for connect and 1 for disconnect.

devzone.nordicsemi.com/.../2021_2D00_01_2D00_26T02_5F00_35_5F00_42.210Z_2D00_log.txt

terminal a contact on an electrical device (such as a battery) at which electric current enters or leaves More (Definitions, Synonyms, Translation)

RE: Mqtt client Nrf9160 Module

Øyvind — Mon, 25 Jan 2021 17:13:17 GMT

Hello Ukhan,

I'm seeing the same issue as you with SLM. When trying to send XMQTTCON i receive ERROR. Will forward to our developer.

Kind regards,
Øyvind

RE: Mqtt client Nrf9160 Module

Øyvind — Mon, 25 Jan 2021 09:03:05 GMT

Hello,

I've been testing AWS_IoT on my side, and I'm not able to reproduce the error.

Have you verified that CONFIG_AWS_IOT_CLIENT_ID_STATIC is configured to your Thing ID, and that your device is programmed with correct certificates which belong to your Thing ID? Have you used correct certificates? As described in step 9 of "Creating a thing in AWS IoT"?

Also, have you configured correct Rest API Endpoint in CONFIG_AWS_IOT_BROKER_HOST_NAME ? And configured CONFIG_AWS_IOT_SEC_TAG to the correct sec tag used when provisioning certificates?

I will test with the SLM MQTT API as well and get back to you.

Kind regards,
Øyvind

RE: Mqtt client Nrf9160 Module

Ukhan — Fri, 22 Jan 2021 02:37:02 GMT

devzone.nordicsemi.com/.../8883_2D00_log.txt devzone.nordicsemi.com/.../443_2D00_log.txt

Are you able to provide a full log output when connecting to AWS-IoT?
See attachments.

What modem fw are you running?

at+cgmr

mfw_nrf9160_1.2.2

And what is the network provider that you use?
1nce SIM and tried with two MNOs : Korea Telecom and SKT

RE: Mqtt client Nrf9160 Module

Øyvind — Thu, 21 Jan 2021 10:00:17 GMT

Are you able to provide a full log output when connecting to AWS-IoT? Both with 433 and 8333. I will discuss this with our R&D team. What modem fw are you running? And what is the network provider that you use?

aws_iot_connect, error: -119 means "Connection already in progress", while mqtt_connect, error: -116 means "Connection timed out".

RE: Mqtt client Nrf9160 Module

Ukhan — Thu, 21 Jan 2021 04:26:10 GMT

I tried the simple one before and AWS-IoT example as well. I tried everything again.
And it seems to be a problem with the MNO as Farhang pointed out in the ticket you shared.

Now, I have tried two different MNOs KT and SK Telecom(by configuring with AT commands) and both of them have a problem with socket connection.

On AWS Cloudwatch I can see this

The AWS-IoT example in the NCS, I tried that as well, with two different ports: 8333 and 443.
With 433 it gives the aws_iot_connect, error: -119 and with 8333 it gives E: mqtt_connect, error: -116.

Can you highlight what else can I try?

RE: Mqtt client Nrf9160 Module

Øyvind — Wed, 20 Jan 2021 14:25:30 GMT

Have you tested the MQTT connection using e.g. Simple MQTT sample? Have a look at the answer my colleague Heidi gives here.

Please make sure to use correct username, password and sec_tag for your certificates. Have you verified that you have added correct certificates?

RE: Mqtt client Nrf9160 Module

Ukhan — Wed, 20 Jan 2021 13:52:36 GMT

Could you explain how do I fix that? Do I need to issue a different at command before that?
I was assuming all of this will be handled in the slm application.

RE: Mqtt client Nrf9160 Module

Øyvind — Wed, 20 Jan 2021 11:46:00 GMT

Hello,

Yes, you are correct. There seems to be a bug in the documentation which I will report. This also explains the ERROR you received in your last comment.

The MQTTEVT reports -128, which means "Socket is not connected".

RE: Mqtt client Nrf9160 Module

Ukhan — Wed, 20 Jan 2021 08:02:32 GMT

Correct me if I am wrong but in the code the macro AT_MQTTCON_CONNECT is set to 1 while in the documentation it says

AT#XMQTTCON=<op>[,<client_id>,<username>,<password>,<url>,<port>[,<sec_tag>]]

The <op> parameter is an integer. It can accept one of the following values:
- 0 - Connect to the MQTT broker.
- 1 - Disconnect from the MQTT broker.

That seems to be contradictory. I debugged and it seemed to hit the connect case AT_MQTTCON_CONNECT case only when 1 was sent. And then it polls for CONACK where it returns error.

So basically this is happening on nrf Connect

RE: Mqtt client Nrf9160 Module

Ukhan — Wed, 20 Jan 2021 02:09:49 GMT

NCS: v1.4.99, I suppose this is the latest.

I tried with Serial LTE modem application as well.
Following the documentation, I send

AT#XMQTTCON=0,"nrf91","","","myAWSendpoint.com",8883,123

ERROR

On nrf connect desktop app I can see that signal strength is fine and the module is awake as well.

One weird thing is that on AWS-IoT core I can see that a connection was established in the Manage section where it shows connections graph.

RE: Mqtt client Nrf9160 Module

Øyvind — Tue, 19 Jan 2021 08:24:37 GMT

Hello,

First of all, what version of NCS are you working on?

[quote user=""] flashed at_client example inside the nrf9160 and trying to send AT#XMQTTCON command to[/quote]

Have you tried with the Serial LTE modem application? The MQTT AT command is only available in this application.

Edit: For AT commands that work with the AT client, please see the AT Commands documentation.

Kind regards,
Øyvind