NRF9160 AWS IOT no connection possible.

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Thu, 23 Nov 2023 16:23:48 GMT

Did you try to use nrf_setdnsaddr to provide a back-up DNS server?

RE: NRF9160 AWS IOT no connection possible.

emsys — Tue, 21 Nov 2023 17:42:38 GMT

Hello

I try with the same SIM, URL and topic same certificates, with other hardware from a competitor (Not Nordic based) and i works, i van post MQTT message tot de AWS cloud.

So there is some problem with the configuration of the Nordic modem i think?

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Mon, 20 Nov 2023 14:10:29 GMT

The modem trace shows that the device tries to do a DNS lookup, but it doesn't get any response from the DNS server.

Are you able to run other samples, or connect to other servers?

Are you sure the hostname is correct?

You can also try to add a back-up DNS server with nrf_setdnsaddr.

RE: NRF9160 AWS IOT no connection possible.

emsys — Sat, 18 Nov 2023 17:57:06 GMT

Hello

Please find here the trace file.

Kind Regards

devzone.nordicsemi.com/.../trace_2D00_2023_2D00_11_2D00_18T17_2D00_48_2D00_41.328Z.mtrace

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Fri, 17 Nov 2023 10:19:00 GMT

That is log from the application, not the modem.

Please see the link in my previous reply on how to take a modem trace.

RE: NRF9160 AWS IOT no connection possible.

emsys — Thu, 16 Nov 2023 19:12:45 GMT

Modem Trace:

*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
*** Booting Zephyr OS build v3.3.99-ncs1-1 ***
I: The AWS IoT sample started, version: v1.0.0
I: Trace thread ready
I: Trace level override: 2
+CEREG: 2,"0C3F","02C93C01",7
I: LTE cell changed: Cell ID: 46742529, Tracking area: 3135
+CSCON: 1
I: RRC mode: Connected
+CEREG: 1,"0C3F","02C93C01",7,,,"11100000","00000110"
I: Network registration status: Connected - home network
I: PSM parameter update: TAU: 3600, Active time: -1
%XTIME: "40","32116191900540","00"
I: Date time obtained
I: Next connection retry in 30 seconds
I: AWS_IOT_EVT_CONNECTING
W: connection_poll_start failed, error: -119
E: aws_iot_connect, error: -119
I: Next connection retry in 30 seconds
W: getaddrinfo, error: -11

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Fri, 29 Sep 2023 09:31:30 GMT

Could you enable debug logging in the aws_iot library to see if that gives us some more information?

CONFIG_AWS_IOT_LOG_LEVEL_DBG=y

Also, if you disable minimal logging, it will be easier to see where various log lines come from.

CONFIG_LOG_MODE_MINIMAL=n

Also, if you can take a modem trace, that would be helpful.

RE: NRF9160 AWS IOT no connection possible.

emsys — Thu, 28 Sep 2023 18:20:53 GMT

Hello

Sorry for the delay, other project gets a bigger priority.

The problem is still exist.

I update my certificate without any success.

This the output from the debug trace

Connection poll in progress

W: connection_poll_start failed, error: -119

E: aws_iot_connect, error: -119

I: Next connection retry in 5 seconds

E: getaddrinfo, error -11

E: client_broker_init, error: -10

I changed this 3 lines

CONFIG_AWS_IOT_CLIENT_ID_STATIC="AWS_Thing"

CONFIG_AWS_IOT_BROKER_HOST_NAME="avbdfegwrkr9hu-ats.iot.eu-west-1.amazonaws.com"

CONFIG_AWS_IOT_SEC_TAG=16842750

The tag was changed to this number by uploading the certificates.

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Wed, 21 Jun 2023 08:42:22 GMT

[quote user="emsys"]I added the lines by myself and got this error: "warning: attempt to assign the value 'y' to the undefined symbol AWS_IOT_LOG_LEVE_DBG" i added this to prj.conf[/quote]

I'm sorry, that was a typo on my end. It should be CONFIG_AWS_IOT_LOG_LEVEL_DBG=y.

[quote user="emsys"]Maybe, HOST name is changed the other are stock values.[/quote]

Which sec_tag did you write the credentials to? 201?

And what did you name the device in AWS and the device certificate?

RE: NRF9160 AWS IOT no connection possible.

emsys — Mon, 19 Jun 2023 19:41:06 GMT

Hello

I added the lines by myself and got this error: "warning: attempt to assign the value 'y' to the undefined symbol AWS_IOT_LOG_LEVE_DBG" i added this to prj.conf

[quote userid="81181" url="~/f/nordic-q-a/100846/nrf9160-aws-iot-no-connection-possible/431803"]Which sec_tag did you write the credentials to, and have you changed CONFIG_AWS_IOT_CLIENT_ID_STATIC, CONFIG_AWS_IOT_BROKER_HOST_NAME and CONFIG_AWS_IOT_SEC_TAG to the correct values?[/quote]

Maybe, HOST name is changed the other are stock values.

CONFIG_AWS_IOT_CLIENT_ID_STATIC="my-thing"
CONFIG_AWS_IOT_BROKER_HOST_NAME="xxxxx.iot.xxxx.amazonaws.com"

CONFIG_AWS_IOT_SEC_TAG=201

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Mon, 19 Jun 2023 13:56:12 GMT

[quote user="emsys"]For some reason i can't find this lines in my config prj.conf?[/quote]

You need to add them yourself.

Which sec_tag did you write the credentials to, and have you changed CONFIG_AWS_IOT_CLIENT_ID_STATIC, CONFIG_AWS_IOT_BROKER_HOST_NAME and CONFIG_AWS_IOT_SEC_TAG to the correct values?

RE: NRF9160 AWS IOT no connection possible.

emsys — Thu, 15 Jun 2023 17:45:26 GMT

Yes i added this lines to my code.

For some reason i can't find this lines in my config prj.conf?

[quote userid="81181" url="~/f/nordic-q-a/100846/nrf9160-aws-iot-no-connection-possible/431341"]CONFIG_LOG_MODE_MINIMAL=n[/quote][quote userid="81181" url="~/f/nordic-q-a/100846/nrf9160-aws-iot-no-connection-possible/431341"]CONFIG_AWS_IOT_LOG_LEVE_DBG=y[/quote]

Tutorial that i used: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/libraries/networking/aws_iot.html#setup-aws-and-permissions

RE: NRF9160 AWS IOT no connection possible.

Didrik Rokhaug — Thu, 15 Jun 2023 15:04:05 GMT

Hi,

E: AWS IoT library could be initialized, error: 0

E: Adding application specific topics succes, error: 0

E: Modem could be configured, error: 0

E: initializing modem info module, error: 0

I assume this is logging you have added to the sample?

Could you enable debug logging in the aws_iot library to see if that gives us some more information?

CONFIG_AWS_IOT_LOG_LEVE_DBG=y

Also, if you disable minimal logging, it will be easier to see where various log lines come from.

CONFIG_LOG_MODE_MINIMAL=n

Also, if you can take a modem trace, that would be helpful.

[quote user=""]described in the tutorial online[/quote]

Just to make sure we talk about the same thing, could you share a link to the tutorial?

Best regards,

Didrik

RE: NRF9160 AWS IOT no connection possible.

JyriLehtinen — Thu, 15 Jun 2023 08:31:11 GMT

Error -119 is EINPROGRESS, which should mean that the device has an ongoing task to connect to the MQTT broker. You probably have multiple concurrent calls to the aws_iot_connect() (or similar)