• State Not Answered
  • Replies 3 replies
  • Subscribers 87 subscribers
  • Views 631 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 258288
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

No connection to nrfcloud

gersto

Hello!

I'am from austria and try to connect a Thingy:91 to your nrf-Cloud. First I tried it with your

iBASIS sim-card, but in austria we can't use this card.

Then I tried it with a sim-card from a local provider (Telekom-Austria) and with the

nbiot_legacy_pco_dfu.hex image first it looks good but I don't get a connection to

your cloud. See below for output from the lte-link-monitor. The only problem I'll see is

an err with modem_info params.

Do you have any experience or could you help me what is wrong.

Best regard

Gerald

2020-10-19T09:28:21.026Z INFO Application data folder: C:\Users\gersto\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2020-10-19T09:28:21.082Z DEBUG App pc-nrfconnect-linkmonitor v1.1.8 official
2020-10-19T09:28:21.082Z DEBUG App path: C:\Users\gersto\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2020-10-19T09:28:21.082Z DEBUG nRFConnect 3.6.0 is supported by the app (^3.6.0)
2020-10-19T09:28:21.082Z DEBUG nRFConnect path: C:\Users\gersto\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-10-19T09:28:21.082Z DEBUG HomeDir: C:\Users\gersto
2020-10-19T09:28:21.082Z DEBUG TmpDir: C:\Users\gersto\AppData\Local\Temp
2020-10-19T09:28:21.609Z VERBOSE Could not fetch serial number for serial port at COM7
2020-10-19T09:28:21.609Z VERBOSE Could not fetch serial number for serial port at COM8
2020-10-19T09:28:23.821Z ERROR Opening COM11: Access denied
2020-10-19T09:28:33.442Z INFO Modem port is opened
2020-10-19T09:28:33.452Z DEBUG modem >> AT+CFUN?
2020-10-19T09:28:33.471Z DEBUG modem << +CFUN: 1
2020-10-19T09:28:33.474Z DEBUG modem << OK
2020-10-19T09:28:33.499Z DEBUG modem >> AT+CGSN=1
2020-10-19T09:28:33.508Z DEBUG modem << +CGSN: "352656101112863"
2020-10-19T09:28:33.510Z DEBUG modem << OK
2020-10-19T09:28:33.517Z DEBUG modem >> AT+CGMI
2020-10-19T09:28:33.525Z DEBUG modem << Nordic Semiconductor ASA
2020-10-19T09:28:33.528Z DEBUG modem << OK
2020-10-19T09:28:33.534Z DEBUG modem >> AT+CGMM
2020-10-19T09:28:33.542Z DEBUG modem << nRF9160-SICA
2020-10-19T09:28:33.543Z DEBUG modem << OK
2020-10-19T09:28:33.551Z DEBUG modem >> AT+CGMR
2020-10-19T09:28:33.565Z DEBUG modem << mfw_nrf9160_1.2.1
2020-10-19T09:28:33.567Z DEBUG modem << OK
2020-10-19T09:28:33.570Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.2.1] SerNr: 352656101112863
2020-10-19T09:28:33.571Z DEBUG modem >> AT+CEMODE?
2020-10-19T09:28:33.583Z DEBUG modem << +CEMODE: 0
2020-10-19T09:28:33.585Z DEBUG modem << OK
2020-10-19T09:28:33.593Z DEBUG modem >> AT%XCBAND=?
2020-10-19T09:28:33.606Z DEBUG modem << %XCBAND: (2,3,4,8,12,13,20,28)
2020-10-19T09:28:33.608Z DEBUG modem << OK
2020-10-19T09:28:33.621Z DEBUG modem >> AT+CMEE?
2020-10-19T09:28:33.631Z DEBUG modem << +CMEE: 0
2020-10-19T09:28:33.634Z DEBUG modem << OK
2020-10-19T09:28:33.639Z DEBUG modem >> AT+CMEE=1
2020-10-19T09:28:33.650Z DEBUG modem << OK
2020-10-19T09:28:33.652Z DEBUG modem >> AT+CNEC?
2020-10-19T09:28:33.659Z DEBUG modem << +CNEC: 0
2020-10-19T09:28:33.663Z DEBUG modem << OK
2020-10-19T09:28:33.669Z DEBUG modem >> AT+CNEC=24
2020-10-19T09:28:33.677Z DEBUG modem << OK
2020-10-19T09:28:33.686Z DEBUG modem >> AT+CGEREP?
2020-10-19T09:28:33.700Z DEBUG modem << +CGEREP: 0,0
2020-10-19T09:28:33.703Z DEBUG modem << OK
2020-10-19T09:28:33.707Z DEBUG modem >> AT+CGDCONT?
2020-10-19T09:28:33.717Z DEBUG modem << +CGDCONT: 0,"IP","m2m.tag.com","10.248.43.39",0,0
2020-10-19T09:28:33.720Z DEBUG modem << OK
2020-10-19T09:28:33.725Z DEBUG modem >> AT+CGACT?
2020-10-19T09:28:33.735Z DEBUG modem << +CGACT: 0,1
2020-10-19T09:28:33.738Z DEBUG modem << OK
2020-10-19T09:28:33.743Z DEBUG modem >> AT+CGEREP=1
2020-10-19T09:28:33.753Z DEBUG modem << OK
2020-10-19T09:28:33.759Z DEBUG modem >> AT+CIND=1,1,1
2020-10-19T09:28:33.767Z DEBUG modem << OK
2020-10-19T09:28:33.772Z DEBUG modem >> AT+CEREG=2
2020-10-19T09:28:33.784Z DEBUG modem << OK
2020-10-19T09:28:33.788Z DEBUG modem >> AT+CEREG?
2020-10-19T09:28:33.808Z DEBUG modem << +CEREG: 2,1,"C355","000F53CE",9
2020-10-19T09:28:33.818Z DEBUG modem << OK
2020-10-19T09:28:33.840Z DEBUG modem >> AT+COPS=3,2
2020-10-19T09:28:33.850Z DEBUG modem << OK
2020-10-19T09:28:33.855Z DEBUG modem >> AT+COPS?
2020-10-19T09:28:33.867Z DEBUG modem << +COPS: 0,2,"23201",9
2020-10-19T09:28:33.869Z DEBUG modem << OK
2020-10-19T09:28:33.886Z DEBUG modem >> AT%XCBAND
2020-10-19T09:28:33.893Z DEBUG modem << %XCBAND: 20
2020-10-19T09:28:33.896Z DEBUG modem << OK
2020-10-19T09:28:33.907Z DEBUG modem >> AT+CGDCONT?
2020-10-19T09:28:33.925Z DEBUG modem << +CGDCONT: 0,"IP","m2m.tag.com","10.248.43.39",0,0
2020-10-19T09:28:33.926Z DEBUG modem << OK
2020-10-19T09:28:33.937Z DEBUG modem >> AT+CGACT?
2020-10-19T09:28:33.950Z DEBUG modem << +CGACT: 0,1
2020-10-19T09:28:33.953Z DEBUG modem << OK
2020-10-19T09:28:33.957Z DEBUG modem >> AT%CESQ=1
2020-10-19T09:28:33.967Z DEBUG modem << OK
2020-10-19T09:28:33.974Z DEBUG modem >> AT+CESQ
2020-10-19T09:28:33.985Z DEBUG modem << +CESQ: 99,99,255,255,26,61
2020-10-19T09:28:33.987Z DEBUG modem << OK
2020-10-19T09:28:33.992Z DEBUG modem >> AT%XSIM=1
2020-10-19T09:28:34.002Z DEBUG modem << OK
2020-10-19T09:28:34.007Z DEBUG modem >> AT%XSIM?
2020-10-19T09:28:34.019Z DEBUG modem << %XSIM: 1
2020-10-19T09:28:34.022Z DEBUG modem << OK
2020-10-19T09:28:34.037Z DEBUG modem >> AT+CPIN?
2020-10-19T09:28:34.051Z DEBUG modem << +CPIN: READY
2020-10-19T09:28:34.053Z DEBUG modem << OK
2020-10-19T09:28:34.071Z DEBUG modem >> AT+CPINR="SIM PIN"
2020-10-19T09:28:34.087Z DEBUG modem << +CPINR: "SIM PIN",3
2020-10-19T09:28:34.089Z DEBUG modem << OK
2020-10-19T09:28:34.093Z DEBUG modem >> AT+CIMI
2020-10-19T09:28:34.107Z DEBUG modem << 232010839656939
2020-10-19T09:28:34.109Z DEBUG modem << OK
2020-10-19T09:28:34.112Z INFO IMSIdentity: 232010839656939
2020-10-19T09:28:42.514Z DEBUG modem << [00:00:16.267,913] [0m<inf> nrf_cloud_transport: Using non-blocking socket[0m
2020-10-19T09:28:42.516Z DEBUG modem << [00:00:16.275,115] [0m<dbg> nrf_cloud.nrf_cloud_run: Cloud connection request sent.[0m
2020-10-19T09:28:44.370Z DEBUG modem << [00:00:18.024,841] [0m<dbg> aws_fota.aws_fota_mqtt_evt_handler: Previous session valid; skipping FOTA subscriptions[0m
2020-10-19T09:28:44.377Z DEBUG modem << [00:00:18.035,705] [0m<inf> aws_fota: Created notify_next_topic $aws/things/nrf-352656101112863/jobs/notify-next[0m
2020-10-19T09:28:44.379Z DEBUG modem << [00:00:18.046,325] [0m<inf> aws_fota: Created get_topic $aws/things/nrf-352656101112863/jobs/$next/get/#[0m
2020-10-19T09:28:44.380Z DEBUG modem << [00:00:18.056,213] [0m<inf> aws_fota: previously subscribed to notify-next topic[0m
2020-10-19T09:28:44.383Z DEBUG modem << [00:00:18.063,995] [0m<inf> aws_jobs: Publish topic: $aws/things/nrf-352656101112863/jobs/$next/get[0m
2020-10-19T09:28:44.386Z DEBUG modem << [00:00:18.073,364] [0m<inf> aws_jobs: Publish payload {"clientToken": ""}[0m
2020-10-19T09:28:44.388Z DEBUG modem << [00:00:18.081,329] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_CONNACK: result 0[0m
2020-10-19T09:28:44.390Z DEBUG modem << [00:00:18.090,515] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 2[0m
2020-10-19T09:28:44.391Z DEBUG modem << [00:00:18.098,297] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_TRANSPORT_CONNECTED[0m
2020-10-19T09:28:44.392Z DEBUG modem << [00:00:18.106,872] [0m<inf> asset_tracker: CLOUD_EVT_CONNECTED[0m
2020-10-19T09:28:44.394Z DEBUG modem << [00:00:18.113,006] [0m<inf> asset_tracker: Persistent Sessions = 1[0m
2020-10-19T09:28:44.395Z DEBUG modem << [00:00:18.119,506] [0m<dbg> nrf_cloud_fsm.connection_handler: Previous session valid; skipping nct_cc_connect()[0m
2020-10-19T09:28:44.396Z DEBUG modem << [00:00:18.130,004] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 4[0m
2020-10-19T09:28:44.415Z DEBUG modem << [00:00:18.137,817] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 5678 opcode = 0 len = 0[0m
2020-10-19T09:28:44.418Z DEBUG modem << [00:00:18.148,376] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
2020-10-19T09:28:45.273Z DEBUG modem << [00:00:19.032,043] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 2636 result = 0[0m
2020-10-19T09:28:45.770Z DEBUG modem << [00:00:19.494,934] [0m<dbg> aws_fota.on_publish_evt: Received topic: $aws/things/nrf-352656101112863/jobs/$next/get/accepted[0m
2020-10-19T09:28:45.775Z DEBUG modem << [00:00:19.506,500] [0m<inf> aws_fota: Checking for an available job[0m
2020-10-19T09:28:45.789Z DEBUG modem << [00:00:19.513,153] [0m<dbg> aws_fota.get_job_execution: Job doc: {"clientToken":"","timestamp":1603099725}[0m
2020-10-19T09:28:45.794Z DEBUG modem << [00:00:19.523,406] [0m<dbg> aws_fota.get_job_execution: Got only one field[0m
2020-10-19T09:28:45.797Z DEBUG modem << [00:00:19.530,578] [0m<inf> aws_fota: No queued jobs for this device[0m
2020-10-19T09:28:46.003Z DEBUG modem << [00:00:19.751,861] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 5678 result = 0[0m
2020-10-19T09:28:46.007Z DEBUG modem << [00:00:19.761,932] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
2020-10-19T09:28:46.530Z DEBUG modem << [00:00:20.233,306] [0m<dbg> aws_fota.on_publish_evt: Received topic: nrf-352656101112863/shadow/get/accepted[0m
2020-10-19T09:28:46.541Z DEBUG modem << [00:00:20.243,469] [0m<dbg> aws_fota.on_publish_evt: received an unhandled MQTT publish event on topic: nrf-352656101112863/shadow/get/accepted[0m
2020-10-19T09:28:46.542Z DEBUG modem << [00:00:20.256,744] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBLISH: id = 0 len = 317[0m
2020-10-19T09:28:46.544Z DEBUG modem << [00:00:20.267,761] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 5[0m
2020-10-19T09:28:46.546Z DEBUG modem << [00:00:20.275,573] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_RX_DATA[0m
2020-10-19T09:28:46.547Z DEBUG modem << [00:00:20.283,111] [0m<inf> asset_tracker: CLOUD_EVT_DATA_RECEIVED[0m
2020-10-19T09:28:46.549Z DEBUG modem << [00:00:20.290,374] [0m<inf> cloud_codec: [cloud_search_config:898] Found cfg item GPS, enable
2020-10-19T09:28:46.552Z DEBUG modem << [0m
2020-10-19T09:28:46.561Z DEBUG modem << [00:00:20.301,879] [0m<dbg> nrf_cloud_transport.nct_dc_endpoint_set: nct_dc_endpoint_set[0m
2020-10-19T09:28:46.563Z DEBUG modem << [00:00:20.310,516] [0m<dbg> nrf_cloud_transport.nct_dc_endpoint_get: nct_dc_endpoint_get[0m
2020-10-19T09:28:46.585Z DEBUG modem << [00:00:20.320,251] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 7890 opcode = 1 len = 329[0m
2020-10-19T09:28:46.587Z DEBUG modem << [00:00:20.331,848] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 7[0m
2020-10-19T09:28:46.589Z DEBUG modem << [00:00:20.339,630] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED[0m
2020-10-19T09:28:46.591Z DEBUG modem << [00:00:20.347,869] [0m<inf> asset_tracker: CLOUD_EVT_PAIR_DONE[0m
2020-10-19T09:28:48.138Z DEBUG modem << [00:00:21.864,929] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 7890 result = 0[0m
2020-10-19T09:28:48.139Z DEBUG modem << [00:00:21.875,061] [0m<dbg> nrf_cloud_fsm.cc_tx_ack_handler: Previous session valid; skipping nct_dc_connect()[0m
2020-10-19T09:28:48.151Z DEBUG modem << [00:00:21.885,406] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9[0m
2020-10-19T09:28:48.152Z DEBUG modem << [00:00:21.893,218] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_READY[0m
2020-10-19T09:28:48.153Z DEBUG modem << [00:00:21.900,543] [0m<inf> asset_tracker: CLOUD_EVT_READY[0m
2020-10-19T09:28:48.214Z DEBUG modem << [00:00:21.936,920] [0m<dbg> nrf9160_gps.init: GPS socket created, fd: 1232491587[0m
2020-10-19T09:28:48.215Z DEBUG modem << [00:00:21.950,744] [0m<inf> gps_control: GPS initialized[0m
2020-10-19T09:28:48.216Z DEBUG modem << [00:00:21.943,786] [1;31m<err> modem_info_params: Link data not obtained: 20 -22[0m
2020-10-19T09:28:48.225Z DEBUG modem << [00:00:21.966,644] [1;31m<err> modem_info_params: Network data not obtained: -22[0m
2020-10-19T09:28:48.227Z DEBUG modem << [00:00:21.974,334] [1;31m<err> asset_tracker: Unable to obtain modem parameters: -11[0m
2020-10-19T09:28:48.228Z DEBUG modem << [00:00:21.983,947] [0m<dbg> nrf_cloud_transport.nct_cc_send: mqtt_publish: id = 1 opcode = 1 len = 162[0m
2020-10-19T09:28:49.879Z DEBUG modem << [00:00:23.637,969] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 1 result = 0[0m
2020-10-19T09:29:00.433Z DEBUG modem << +CSCON: 0
2020-10-19T09:29:00.437Z DEBUG modem << [00:00:34.196,746] [0m<dbg> lte_lc.at_handler: +CSCON notification[0m
2020-10-19T09:29:00.632Z DEBUG modem << %CESQ: 255,0,255,0
2020-10-19T09:29:04.345Z DEBUG modem << %CESQ: 62,3,32,4
2020-10-19T09:29:04.611Z DEBUG modem << +CSCON: 1
2020-10-19T09:29:04.624Z DEBUG modem << [00:00:38.374,542] [0m<dbg> lte_lc.at_handler: +CSCON notification[0m
2020-10-19T09:29:11.153Z DEBUG modem << +CSCON: 0
2020-10-19T09:29:11.164Z DEBUG modem << [00:00:44.916,992] [0m<dbg> lte_lc.at_handler: +CSCON notification[0m
2020-10-19T09:29:11.510Z DEBUG modem << %CESQ: 255,0,255,0
2020-10-19T09:29:14.584Z DEBUG modem << %CESQ: 62,3,31,4
2020-10-19T09:29:23.490Z DEBUG modem << +CSCON: 1
2020-10-19T09:29:23.501Z DEBUG modem << [00:00:57.255,035] [0m<dbg> lte_lc.at_handler: +CSCON notification[0m
2020-10-19T09:29:30.833Z DEBUG modem << +CSCON: 0
2020-10-19T09:29:30.851Z DEBUG modem << [00:01:04.597,534] [0m<dbg> lte_lc.at_handler: +CSCON notification[0m
2020-10-19T09:29:31.030Z DEBUG modem << %CESQ: 255,0,255,0
2020-10-19T09:29:35.065Z DEBUG modem << %CESQ: 61,3,30,4
2020-10-19T09:29:40.184Z DEBUG modem << %CESQ: 63,3,34,4

Parents
  • 0

    Hi,

    From the logs, it seems like things are mostly working as it should.

    Could you try again, but this time with "automatic requests" turned off, and not pressing the 'AT+CFUN?' button?

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hello,

    Thanks for your tip, but I don't understand it. I image a default asset-tracker application and monitor the start with the LTE Link Monitor. When I configure e.g. "Automatic requests" what influence had this on the application start.

    I try your tip but nothing changed. In the nrfcloud I will always see "Device added to account. Waiting for it to connect..."

    Best regards

  • 0 in reply to gersto
    gersto said:
    Thanks for your tip, but I don't understand it.

     The lte_link_control library uses the unsolicited +CEREG notifications to see if the device has been granted PSM by the network. For this to work, the +CEREG notification level must be set to 5, but the Link Monitor sets it to 2. This can potentially cause some problems. But, that doesn't seem to be the case here.

    I have some problems understanding exactly what is wrong. According to the log you posted, it seems the device is connected to nRF Cloud as it should:

    2020-10-19T09:28:46.589Z DEBUG modem << [00:00:20.339,630] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED[0m
2020-10-19T09:28:46.591Z DEBUG modem << [00:00:20.347,869] [0m<inf> asset_tracker: CLOUD_EVT_PAIR_DONE[0m
2020-10-19T09:28:48.138Z DEBUG modem << [00:00:21.864,929] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 7890 result = 0[0m
2020-10-19T09:28:48.139Z DEBUG modem << [00:00:21.875,061] [0m<dbg> nrf_cloud_fsm.cc_tx_ack_handler: Previous session valid; skipping nct_dc_connect()[0m
2020-10-19T09:28:48.151Z DEBUG modem << [00:00:21.885,406] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9[0m
2020-10-19T09:28:48.152Z DEBUG modem << [00:00:21.893,218] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_READY[0m
2020-10-19T09:28:48.153Z DEBUG modem << [00:00:21.900,543] [0m<inf> asset_tracker: CLOUD_EVT_READY[0m

    Are you sure you are looking at the right device, or that the device is associated with the right account?

    Could you explain a bit more what you are seeing in nRF Cloud?

Reply
  • 0 in reply to gersto
    gersto said:
    Thanks for your tip, but I don't understand it.

     The lte_link_control library uses the unsolicited +CEREG notifications to see if the device has been granted PSM by the network. For this to work, the +CEREG notification level must be set to 5, but the Link Monitor sets it to 2. This can potentially cause some problems. But, that doesn't seem to be the case here.

    I have some problems understanding exactly what is wrong. According to the log you posted, it seems the device is connected to nRF Cloud as it should:

    2020-10-19T09:28:46.589Z DEBUG modem << [00:00:20.339,630] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_USER_ASSOCIATED[0m
2020-10-19T09:28:46.591Z DEBUG modem << [00:00:20.347,869] [0m<inf> asset_tracker: CLOUD_EVT_PAIR_DONE[0m
2020-10-19T09:28:48.138Z DEBUG modem << [00:00:21.864,929] [0m<dbg> nrf_cloud_transport.nct_mqtt_evt_handler: MQTT_EVT_PUBACK: id = 7890 result = 0[0m
2020-10-19T09:28:48.139Z DEBUG modem << [00:00:21.875,061] [0m<dbg> nrf_cloud_fsm.cc_tx_ack_handler: Previous session valid; skipping nct_dc_connect()[0m
2020-10-19T09:28:48.151Z DEBUG modem << [00:00:21.885,406] [0m<dbg> nrf_cloud.nfsm_set_current_state_and_notify: state: 9[0m
2020-10-19T09:28:48.152Z DEBUG modem << [00:00:21.893,218] [0m<dbg> nrf_cloud.api_event_handler: NRF_CLOUD_EVT_READY[0m
2020-10-19T09:28:48.153Z DEBUG modem << [00:00:21.900,543] [0m<inf> asset_tracker: CLOUD_EVT_READY[0m

    Are you sure you are looking at the right device, or that the device is associated with the right account?

    Could you explain a bit more what you are seeing in nRF Cloud?

Children
No Data
Related
Terms of service