MQTT input error: -128 when trying to connect Thingy:91 to nRFcloud

[Angel]

Hello,

My thingy:91 was working nicely, even connecting to nRFcloud. But after updating the firmware to thingy91_fw_2022-09-15_7a358cb7 and Update jitp certificates it doesn't connect to nRFcloud anymore.

It connects to LTE with the log:

Fullscreen 2022-10-22T13_36_48.525Z-log.txt Download

2022-10-22T13:36:49.366Z DEBUG Application data folder: /home/atreyu/.config/nrfconnect/pc-nrfconnect-linkmonitor
2022-10-22T13:36:49.738Z INFO Using nrf-device-lib-js version: 0.4.13
2022-10-22T13:36:49.739Z INFO Using nrf-device-lib version: 0.12.8
2022-10-22T13:36:49.739Z INFO Using nrfjprog DLL version: 10.16.0
2022-10-22T13:36:49.739Z INFO Using JLink version: JLink_V7.80c
2022-10-22T13:36:49.810Z DEBUG App pc-nrfconnect-linkmonitor v2.0.2 official
2022-10-22T13:36:49.810Z DEBUG App path: /home/atreyu/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2022-10-22T13:36:49.810Z DEBUG nRFConnect 3.12.0, required by the app is (^3.12.0)
2022-10-22T13:36:49.811Z DEBUG nRFConnect path: /tmp/.mount_nrfconrE8Wik/resources/app.asar
2022-10-22T13:36:49.811Z DEBUG HomeDir: /home/atreyu
2022-10-22T13:36:49.811Z DEBUG TmpDir: /tmp
2022-10-22T13:36:49.818Z INFO Installed JLink version does not match the provided version (V7.66a)
2022-10-22T13:36:56.570Z INFO Modem port is opened
2022-10-22T13:36:56.598Z DEBUG modem >> AT+CFUN?
2022-10-22T13:36:56.645Z DEBUG modem << +CFUN: 1
2022-10-22T13:36:56.651Z DEBUG modem << OK
2022-10-22T13:36:56.676Z DEBUG modem >> AT+CGSN=1
2022-10-22T13:36:56.688Z DEBUG modem << +CGSN: "352656106100541"
2022-10-22T13:36:56.696Z DEBUG modem << OK
2022-10-22T13:36:56.717Z DEBUG modem >> AT+CGMI
2022-10-22T13:36:56.735Z DEBUG modem << Nordic Semiconductor ASA
2022-10-22T13:36:56.739Z DEBUG modem << OK
2022-10-22T13:36:56.747Z DEBUG modem >> AT+CGMM
2022-10-22T13:36:56.758Z DEBUG modem << nRF9160-SICA
2022-10-22T13:36:56.763Z DEBUG modem << OK
2022-10-22T13:36:56.768Z DEBUG modem >> AT+CGMR
2022-10-22T13:36:56.782Z DEBUG modem << mfw_nrf9160_1.3.2
2022-10-22T13:36:56.784Z DEBUG modem << OK
2022-10-22T13:36:56.787Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.3.2] SerNr: 352656106100541
2022-10-22T13:36:56.788Z DEBUG modem >> AT+CEMODE?
2022-10-22T13:36:56.796Z DEBUG modem << +CEMODE: 2
2022-10-22T13:36:56.801Z DEBUG modem << OK
2022-10-22T13:36:56.817Z DEBUG modem >> AT%XCBAND=?
2022-10-22T13:36:56.823Z DEBUG modem << [00:00:01.510,589] [0m<inf> app_event_manager: APP_EVT_START[0m
2022-10-22T13:36:56.826Z DEBUG modem << [00:00:01.512,115] [0m<inf> app_event_manager: MODEM_EVT_INITIALIZED[0m
2022-10-22T13:36:56.829Z DEBUG modem << [00:00:01.587,982] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTING[0m
2022-10-22T13:36:56.834Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2022-10-22T13:36:56.837Z DEBUG modem << OK
2022-10-22T13:36:56.853Z DEBUG modem >> AT+CMEE?
2022-10-22T13:36:56.876Z DEBUG modem << +CMEE: 0
2022-10-22T13:36:56.884Z DEBUG modem << OK
2022-10-22T13:36:56.888Z DEBUG modem >> AT+CMEE=1
2022-10-22T13:36:56.895Z DEBUG modem << OK
2022-10-22T13:36:56.900Z DEBUG modem >> AT+CNEC?
2022-10-22T13:36:56.914Z DEBUG modem << +CNEC: 16
2022-10-22T13:36:56.916Z DEBUG modem << OK
2022-10-22T13:36:56.919Z DEBUG modem >> AT+CNEC=24
2022-10-22T13:36:56.926Z DEBUG modem << OK
2022-10-22T13:36:56.933Z DEBUG modem >> AT+CGEREP?
2022-10-22T13:36:56.941Z DEBUG modem << +CGEREP: 1,0
2022-10-22T13:36:56.943Z DEBUG modem << OK
2022-10-22T13:36:56.946Z DEBUG modem >> AT+CIND=1,1,1
2022-10-22T13:36:56.952Z DEBUG modem << OK
2022-10-22T13:36:56.956Z DEBUG modem >> AT+CEREG=5
2022-10-22T13:36:56.963Z DEBUG modem << OK
2022-10-22T13:36:56.966Z DEBUG modem >> AT+CEREG?
2022-10-22T13:36:56.985Z DEBUG modem << +CEREG: 5,4
2022-10-22T13:36:56.989Z DEBUG modem << OK
2022-10-22T13:36:57.002Z DEBUG modem >> AT%CESQ=1
2022-10-22T13:36:57.008Z DEBUG modem << OK
2022-10-22T13:36:57.012Z DEBUG modem >> AT+CESQ
2022-10-22T13:36:57.022Z DEBUG modem << +CESQ: 99,99,255,255,255,255
2022-10-22T13:36:57.025Z DEBUG modem << OK
2022-10-22T13:36:57.044Z DEBUG modem >> AT%XSIM=1
2022-10-22T13:36:57.051Z DEBUG modem << OK
2022-10-22T13:36:57.054Z DEBUG modem >> AT%XSIM?
2022-10-22T13:36:57.062Z DEBUG modem << %XSIM: 1
2022-10-22T13:36:57.064Z DEBUG modem << OK
2022-10-22T13:36:57.083Z DEBUG modem >> AT+CPIN?
2022-10-22T13:36:57.091Z DEBUG modem << +CPIN: READY
2022-10-22T13:36:57.095Z DEBUG modem << OK
2022-10-22T13:36:57.113Z DEBUG modem >> AT+CPINR="SIM PIN"
2022-10-22T13:36:57.127Z DEBUG modem << +CPINR: "SIM PIN",3
2022-10-22T13:36:57.129Z DEBUG modem << OK
2022-10-22T13:36:57.140Z DEBUG modem >> AT+CIMI
2022-10-22T13:36:57.150Z DEBUG modem << 204080813563092
2022-10-22T13:36:57.161Z DEBUG modem << OK
2022-10-22T13:36:57.166Z INFO IMSIdentity: 204080813563092
2022-10-22T13:36:57.829Z DEBUG modem << [00:00:02.530,151] [0m<inf> app_event_manager: DATA_EVT_CONFIG_INIT[0m
2022-10-22T13:36:58.828Z DEBUG modem << %CESQ: 23,1,5,0
2022-10-22T13:36:58.841Z DEBUG modem << +CEREG: 2,"B9F0","072BFE0A",7
2022-10-22T13:36:58.864Z DEBUG modem << %CESQ: 27,1,11,1
2022-10-22T13:36:59.035Z DEBUG modem << +CSCON: 1
2022-10-22T13:36:59.836Z DEBUG modem << [00:00:04.536,651] [0m<inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE[0m
2022-10-22T13:37:00.787Z DEBUG modem << +CGEV: ME PDN ACT 0,0
2022-10-22T13:37:00.806Z DEBUG modem << +CNEC_ESM: 50,0
2022-10-22T13:37:00.815Z DEBUG modem << %MDMEV: SEARCH STATUS 2
2022-10-22T13:37:00.817Z DEBUG modem << +CEREG: 5,"B9F0","072BFE0A",7,,,"00001010","11000001"
2022-10-22T13:37:00.831Z DEBUG modem << +CIND: "service",1
2022-10-22T13:37:00.843Z DEBUG modem << +CIND: "roam",1
2022-10-22T13:37:00.848Z DEBUG modem << %XTIME: "80","22012231730080","01"
2022-10-22T13:37:00.850Z DEBUG modem >> AT+CGDCONT?
2022-10-22T13:37:00.862Z DEBUG modem << +CGDCONT: 0,"IP","IBASIS.IOT","10.160.190.17",0,0
2022-10-22T13:37:00.865Z DEBUG modem << OK
2022-10-22T13:37:00.882Z DEBUG modem >> AT+COPS=3,2
2022-10-22T13:37:00.890Z DEBUG modem << OK
2022-10-22T13:37:00.899Z DEBUG modem >> AT+CGACT?
2022-10-22T13:37:00.909Z DEBUG modem << +CGACT: 0,1
2022-10-22T13:37:00.912Z DEBUG modem << OK
2022-10-22T13:37:00.922Z DEBUG modem >> AT+COPS?
2022-10-22T13:37:00.931Z DEBUG modem << +COPS: 0,2,"21407",7
2022-10-22T13:37:00.935Z DEBUG modem << OK
2022-10-22T13:37:00.955Z DEBUG modem >> AT%XCBAND
2022-10-22T13:37:00.961Z DEBUG modem << %XCBAND: 3
2022-10-22T13:37:00.963Z DEBUG modem << OK
2022-10-22T13:37:00.978Z DEBUG modem >> AT+CGDCONT?
2022-10-22T13:37:00.990Z DEBUG modem << +CGDCONT: 0,"IP","IBASIS.IOT","10.160.190.17",0,0
2022-10-22T13:37:00.995Z DEBUG modem << OK
2022-10-22T13:37:01.010Z DEBUG modem >> AT+CGACT?
2022-10-22T13:37:01.018Z DEBUG modem << +CGACT: 0,1
2022-10-22T13:37:01.022Z DEBUG modem << OK
2022-10-22T13:37:01.836Z DEBUG modem << [00:00:06.487,457] [1;33m<wrn> modem_module: Event: PDP context 0, PDN type IPv4 only allowed[0m
2022-10-22T13:37:01.839Z DEBUG modem << [00:00:06.502,593] [0m<inf> app_event_manager: MODEM_EVT_LTE_CONNECTED[0m
2022-10-22T13:37:01.840Z DEBUG modem << [00:00:06.503,204] [0m<inf> app_event_manager: MODEM_EVT_LTE_PSM_UPDATE[0m
2022-10-22T13:37:01.842Z DEBUG modem << [00:00:06.503,784] [0m<inf> app_event_manager: DATA_EVT_DATE_TIME_OBTAINED[0m
2022-10-22T13:37:01.844Z DEBUG modem << [00:00:06.504,913] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-10-22T13:37:01.845Z DEBUG modem << [00:00:06.504,943] [1;33m<wrn> cloud_module: New connection attempt in 32 seconds if not successful[0m
2022-10-22T13:37:01.847Z DEBUG modem << [00:00:06.505,187] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-10-22T13:37:08.900Z DEBUG modem << %CESQ: 27,1,16,2
2022-10-22T13:37:10.935Z DEBUG modem << [00:00:15.622,772] [0m<inf> app_event_manager: CLOUD_EVT_CONFIG_RECEIVED[0m
2022-10-22T13:37:10.942Z DEBUG modem << [00:00:15.631,134] [0m<inf> app_event_manager: DATA_EVT_CONFIG_SEND[0m
2022-10-22T13:37:10.945Z DEBUG modem << [00:00:15.631,988] [0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS[0m
2022-10-22T13:37:14.176Z DEBUG modem << [00:00:18.861,968] [0m<inf> app_event_manager: CLOUD_EVT_DISCONNECTED[0m
2022-10-22T13:37:14.179Z DEBUG modem << [00:00:18.862,579] [1;31m<err> nrf_cloud_transport: MQTT input error: -128[0m
2022-10-22T13:37:14.183Z DEBUG modem << [00:00:18.862,701] [1;31m<err> nrf_cloud_transport: Error disconnecting from cloud: -128[0m
2022-10-22T13:37:16.704Z DEBUG modem << +CSCON: 0
2022-10-22T13:37:16.724Z DEBUG modem << %CESQ: 25,1,9,1
2022-10-22T13:37:19.314Z DEBUG modem << %CESQ: 27,1,15,2
2022-10-22T13:37:32.923Z DEBUG modem << +CSCON: 1
2022-10-22T13:37:32.929Z DEBUG modem << %CESQ: 26,1,9,1
2022-10-22T13:37:33.528Z DEBUG modem << %CESQ: 27,1,15,2
2022-10-22T13:37:33.841Z DEBUG modem << [00:00:38.505,096] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTION_TIMEOUT[0m
2022-10-22T13:37:33.843Z DEBUG modem << [00:00:38.505,645] [1;33m<wrn> cloud_module: Cloud connection establishment in progress[0m
2022-10-22T13:37:33.845Z DEBUG modem << [00:00:38.505,676] [1;33m<wrn> cloud_module: New connection attempt in 64 seconds if not successful[0m
2022-10-22T13:37:33.847Z DEBUG modem << [00:00:38.505,828] [0m<inf> app_event_manager: CLOUD_EVT_CONNECTING[0m
2022-10-22T13:37:35.136Z DEBUG modem << %CESQ: 26,1,10,1
2022-10-22T13:37:37.911Z DEBUG modem << +CSCON: 0
2022-10-22T13:37:41.133Z DEBUG modem << +CSCON: 1
2022-10-22T13:37:43.563Z DEBUG modem << %CESQ: 27,1,15,2
2022-10-22T13:37:46.312Z DEBUG modem << [00:00:51.001,159] [0m<inf> app_event_manager: CLOUD_EVT_CONFIG_RECEIVED[0m
2022-10-22T13:37:46.325Z DEBUG modem << [00:00:51.009,521] [0m<inf> app_event_manager: DATA_EVT_CONFIG_SEND[0m
2022-10-22T13:37:46.329Z DEBUG modem << [00:00:51.010,375] [0m<inf> app_event_manager: CLOUD_EVT_DATA_SEND_QOS[0m

but remains Green, triple pulse blinking. In the nRFcloud appears as not connected.

I have send the AT commands:

at+cereg=5

at+cfun=1

at+cfun?

Please find attached the log.

How may I connect to nRFcloud?

Thanks,

Angel Espeso

[Håkon Alseth]

Hi,

 

But after updating the firmware to thingy91_fw_2022-09-15_7a358cb7 and Update jitp certificates it doesn't connect to nRFcloud anymore.

Since this is a device that has been added previously to nrfcloud, you must delete it after issuing new jitp certificates.

If you have removed your "former device" from nrfcloud and deleted it, you shall be able to provision new jitp certificates and connect successfully, provided that the new device is also added to your nrfcloud account.

 

However, from the log, it seems that the connection is not successful. By looking at the signal strength, it seems that this is very low. You can try to move the thingy91 to an area with better reception (CESQ > 35 is recommended).

Did you remove and delete the former device in your nrfcloud account?

 

Kind regards,

Håkon

[Angel]

Hi,

I have removed the device and added again to the nrfcloud. It has connected successfully now.

Thanks a lot for your help.

Best Regards,

atreyu

[Håkon Alseth]

I'm glad to hear that the issue was solved. Hope you have a wonderful day!

Cheers,

Håkon