Should I update to the latest firmware?
Yes, it's recommended to update the firmware to get the latest and greatest functionality. See Update Thingy:91 firmware.
What if I want to try it on NB-IoT?
Due to restrictions in the use of TCP and direct internet access in some NB-IoT networks, this may not be an option for your chosen network. The modem firmware supports both LTE-M and NB-IoT modes, but the application is adopted differently among network types and will need to be re-flashed. You will find two NB-IoT images in the "Thingy91 Application" images zip. One is for networks with legacy PCO handling and one is for the rest. With very few exceptions, the "thingy91_nbiot_v*.hex" will be correct. Flash per the instructions above.
Where will the Thingy:91 work?
If you are in a country where LTE-M is enabled on one of the supported bands, you should be able to connect. Check this list from iBasis for countries that have confirmed coverage with the included card. Currently, certified bands are listed in the user guide and the restriction is set in the application code using the %XBANDLOCK AT command.
What to do if I can’t get GPS fixes
First of all: go outside. Good signal levels are important, especially for the first fix.
Be aware that some carriers put limitations on the use of IoT features with roaming SIM cards. Power Saving Mode (PSM) is a feature that is not always available with roaming cards, and the Thingy:91 battery life and GPS functionality depend on it. If you can’t connect and get GPS with the included SIM card, please order an IoT SIM from your local carrier.
Is the source code available for the Thingy:91 application?
Yes, Thingy:91 ships with the asset tracker application found in nRF Connect SDK. Source code is found in this GitHub repository applications/asset_tracker.
I get "Socket error: POLLHUP" when running the Thingy:91 example. What should I do?
You have probably paired your Thingy:91 to the nRF Cloud with an old version of the firmware (pre-release) using different certificates. Delete the Thingy:91 from nRF Cloud and add it again.
If deleting the device from nRF Cloud does not work, then try to update the certificates on your Thingy:91 following this guide.
What should I do when getting "nrf_cloud_connect failed: -111" when trying to connect to nRF Cloud?
First, check that there is still data left on the SIM card by going into nRF Cloud SIM cards view. If there is no data left, then you have to buy more and restart your device. If you have data left, error -111 might indicate that your certificates have been deleted or overwritten, and you should try to update the certificates by following this guide.
What can I do with the nRF52840 on the board?
The current demo application for Thingy:91 is with the Thingy:91 itself being the sensor end-node in the system. An alternate use is to let Thingy:91 be the gateway between short-range sensors and the cloud. We haven't made this demo for the Thingy:91 yet, but it will be very similar to the "LTE BLE Gateway" sample in nRF Connect SDK that was written for the nRF9160 DK: https://github.com/NordicPlayground/fw-nrfconnect-nrf/tree/master/samples/nrf9160/lte_ble_gateway
How do I update the firmware on the Thingy:91?
There are two important blogs to review Thingy:91 Firmware Update using MCUboot and How to add DFU support to a Thingy:91 Project