This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Problem adding Thingy:91 in the nRF Cloud

Hello,

I try to add a Thingy:91 to the nRF Cloud after I received it today. The sim card got's activated without a problem. When I try to key in my IMEI and the Pin which is printed on the label I receive this error: "There was an error adding your device. It wasn't found. Is it connected?"

How to solve this and add the device to my account?

  • Yes, thank you. 

    Could you also connect your Thingy:91 to your computer via USB and use a program like Termite or PuTTY to read the output and add it here. Use these configurations (except for the port)

  • This is what I got after around 5 minutes:

    ***** B***** Booting Zephyr OS v1.14.99-ncs2-rc3 *****
    [00:00:01.685,363] [1;31m<err> at_host: UART check failed
    [0m
    [00:00:01.690,979] [1;31m<err> at_host: UART could not be initialized: -22[0m
    [00:00:01.698,333] [0m<dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMODEMTRACE=0[0m
    [00:00:01.708,251] [0m<dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK
    [0m
    [00:00:01.716,125] [0m<dbg> board_nonsecure.pca20035_magpio_configure: AT CMD: AT%XMAGPIO=1,1,1,7,1,746,803,2,698,748,2,1710,2200,3,824,894,4,880,960,5,791,849,7,1574,1577[0m
    [00:00:01.731,933] [0m<dbg> board_nonsecure.pca20035_magpio_configure: AT RESP: OK
    [0m
    [00:00:01.739,807] [0m<dbg> board_nonsecure.pca20035_magpio_configure: MAGPIO successfully configured[0m
    Asset tracker started
    [00:00:01.751,983] [0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100443962[0m
    [00:00:01.761,077] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100443962/shadow[0m
    [00:00:01.772,552] [0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: $aws/things/nrf-352656100443962/shadow/get/accepted[0m
    [00:00:01.784,912] [0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100443962/shadow/get/rejected[0m
    [00:00:01.797,271] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100443962/shadow/update/delta[0m
    [00:00:01.809,967] [0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100443962/shadow/update[0m
    [00:00:01.821,655] [0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100443962/shadow/get[0m
    Connecting to LTE network. This may take several minutes.
    [00:00:47.738,067] [0m<dbg> lte_lc.at_handler: recv: +CEREG: 2,"FFFE","FFFFFFFF",7
    [0m

  • I tried a different sim card and I get the same result.

    Any new information from your site, ?

  • Another thing which is might important: I live in germany. If I look at the deployment map nb-iot or lte-m should be covered... https://www.gsma.com/iot/deployment-map/ 

  • Could you follow the list here in this Thingy:91 FAQ to update to the latest firmware. You can find both the modem firmware and application firmware packages on the Thingy:91 webpage.

    However, according to the iBasis coverage map there is limited coverage in Germany, so that could be the root of the issue. 

Related