Thingy:91X doesn't connect with nRF Cloud

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Mon, 09 Feb 2026 09:18:56 GMT

Thank you for your help.
It still does not work.

uart:~$ > at AT%XFACTORYRESET=1
at AT%XFACTORYRESET=1
ERROR

[00:01:36.267,425] <dbg> trigger: trigger_work_fn: Sending data sample trigger
[00:01:36.267,822] <dbg> app: app_task: Trigger received
[00:01:36.267,913] <dbg> battery: state_sampling_run: Data sample trigger received, getting battery data
[00:01:36.268,005] <dbg> trigger: trigger_poll_work_fn: Sending shadow/fota poll trigger
[00:01:36.268,493] <inf> nrf_cloud_fota_poll: Checking for FOTA job...
[00:01:36.270,050] <dbg> environmental_module: state_sampling_run: Data sample trigger received, getting environmental data
[00:01:36.270,141] <dbg> environmental_module: sample: temp: 24.359111; press: 102062.695312; humidity: 16.691154; iaq: 200; CO2: 1883.093750; VOC: 11.507160
[00:01:36.270,355] <dbg> environmental_module: sample: Submitting payload
[00:01:36.270,690] <dbg> location_module: location_task: Trigger received
[00:01:36.270,721] <dbg> location_module: handle_trigger_chan: Data sample trigger received, getting location
[00:01:36.270,751] <dbg> location_module: trigger_location_update: GNSS disabled
[00:01:36.270,782] <dbg> location_module: trigger_location_update: location library initialized
[00:01:36.270,874] <inf> location: Wi-Fi and cellular methods combined
[00:01:36.271,148] <dbg> led: poll_running: poll_running
[00:01:36.271,179] <dbg> led: led_not_set_running: led_not_set_running
[00:01:36.271,209] <dbg> led: running_run: running_run
[00:01:36.271,270] <dbg> trigger: trigger_callback: Received message on channel LOCATION_CHAN
[00:01:36.271,301] <dbg> trigger: trigger_callback: Location search started
[00:01:36.271,301] <dbg> trigger: trigger_callback: Running SMF
[00:01:36.271,331] <dbg> trigger: frequent_poll_run: frequent_poll_run
[00:01:36.271,362] <dbg> trigger: frequent_poll_run: Location search started, going into blocked state
[00:01:36.271,362] <dbg> trigger: frequent_poll_exit: frequent_poll_exit
[00:01:36.271,514] <dbg> led: led_pattern_update_work_fn: Setting LED effect: LED_LOCATION_SEARCHING
[00:01:36.271,545] <dbg> app_led_pwm: led_pwm_set_effect: Power state: 0
[00:01:36.271,667] <dbg> location_module: location_task: Trigger received
[00:01:36.271,728] <dbg> location_module: location_task: Trigger received
[00:01:36.271,850] <dbg> network: state_sampling_run: Data sample trigger received, getting network quality data
[00:01:36.272,064] <dbg> app: app_task: Trigger received
[00:01:36.272,094] <dbg> app: app_task: Poll trigger received
[00:01:36.272,247] <dbg> app: shadow_get: Requesting device configuration from the device shadow
[00:01:36.272,430] <dbg> transport: state_connected_ready_run: state_connected_ready_run
[00:01:36.272,460] <dbg> transport: state_connected_ready_run: Payload
                                    9f bf 21 68 31 34 32 30  35 2f 30 2f 00 61 30 02 |..!h1420 5/0/.a0.
                                    fb 40 38 5b ee b2 d0 a2  44 22 1a 69 89 a5 f0 ff |.@8[.... D".i....
[00:01:36.279,937] <dbg> battery: sample: State of charge: 100.000000
[00:01:36.279,998] <dbg> battery: sample: The battery is charging
[00:01:36.280,700] <inf> wifi_nrf_bus: SPIM spi@b000: freq = 8 MHz
[00:01:36.280,731] <inf> wifi_nrf_bus: SPIM spi@b000: latency = 0
[00:01:40.117,980] <inf> nrf_cloud_fota_poll: No pending FOTA job
[00:01:40.490,051] <dbg> transport: state_running_run: state_running_run
[00:01:40.490,173] <dbg> transport: state_connected_ready_run: state_connected_ready_run
[00:01:40.490,203] <dbg> transport: state_connected_ready_run: Payload
                                    9f bf 21 68 31 34 32 30  32 2f 30 2f 00 61 30 02 |..!h1420 2/0/.a0.
                                    18 64 22 1a 69 89 a5 f0  ff bf 00 61 31 02 fb 40 |.d".i... ...a1..@
[00:01:40.907,989] <dbg> app: shadow_get: No shadow delta changes available
[00:01:40.908,081] <dbg> app: app_task: Trigger received
[00:01:41.339,691] <dbg> transport: state_running_run: state_running_run
[00:01:41.907,958] <dbg> location_module: location_event_handler: Got location: lat: 35.884443, lon: 139.503266, acc: 83.000000, method: 4
[00:01:41.908,020] <dbg> led: poll_running: poll_running
[00:01:41.908,050] <dbg> led: poll_entry: poll_entry
[00:01:41.908,142] <dbg> trigger: trigger_callback: Received message on channel LOCATION_CHAN
[00:01:41.908,172] <dbg> trigger: trigger_callback: Location search done
[00:01:41.908,172] <dbg> trigger: trigger_callback: Running SMF
[00:01:41.908,203] <dbg> trigger: blocked_run: blocked_run
[00:01:41.908,233] <dbg> trigger: blocked_run: Going into frequent poll state
[00:01:41.908,447] <dbg> trigger: frequent_poll_entry: frequent_poll_entry
[00:01:41.908,294] <dbg> led: led_pattern_update_work_fn: Setting LED effect: LED_POLL_MODE
[00:01:41.908,355] <dbg> app_led_pwm: led_pwm_set_effect: Power state: 0
[00:01:41.908,447] <dbg> trigger: frequent_poll_entry: Location search done
[00:02:11.908,599] <dbg> trigger: trigger_poll_work_fn: Sending shadow/fota poll trigger
[00:02:11.909,149] <inf> nrf_cloud_fota_poll: Checking for FOTA job...
[00:02:11.910,583] <dbg> app: app_task: Trigger received
[00:02:11.910,614] <dbg> app: app_task: Poll trigger received
[00:02:11.910,766] <dbg> app: shadow_get: Requesting device configuration from the device shadow
[00:02:11.911,132] <dbg> location_module: location_task: Trigger received
[00:02:11.911,193] <dbg> location_module: location_task: Trigger received
[00:02:13.478,454] <inf> nrf_cloud_fota_poll: No pending FOTA job
[00:02:13.829,193] <dbg> app: shadow_get: No shadow delta changes available
[00:02:13.829,284] <dbg> app: app_task: Trigger received

Anyway, it works now.
Thank you very much for your support!

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Mon, 09 Feb 2026 08:51:52 GMT

It should be AT%XFACTORYRESET=1 since this a proprietary command, and not "AT+XFACTORYRESET=1" as you wrote.

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Sat, 07 Feb 2026 12:23:05 GMT

Thank you for your reply.

Not, I havent tried issuing the command yet.
I tried it today and it seems to have failed.

uart:~$ > at AT+XFACTORYRESET=1
at AT+XFACTORYRESET=1
ERROR

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Tue, 03 Feb 2026 08:55:14 GMT

Have you tried issuing AT%XFACTORYRESET=1 to the modem?

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Mon, 02 Feb 2026 21:58:28 GMT

I set AT+COPS=0 and it went online within a second.
Thanks to you and the modem team!

There is one more thing I would like to ask:
After restarting, the device is stuck again.
So, the setting is not permanent.

I don't completely understand why this problem exists, because I reloaded and updated the modem firmware via QuickStart several times, and therefore, the device should have been in its original state.

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Mon, 02 Feb 2026 09:59:54 GMT

Modem team had a look and is asking now;

Can it be that the app/user has locked the PLMN with +COPS. The modem log is not from the boot so cannot confirm that.

In the NBIOT system it looks like there is manual selection configured with MCC 204 MNC16 belongs to Netherlands T-Mobile. Device is Japan, so this then does not work. Can it be some build config that is now set wrongly?

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Thu, 29 Jan 2026 13:43:50 GMT

Okay, I have asked the modem team to have a look.

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Tue, 27 Jan 2026 21:59:44 GMT

Thank you for bearing with me.
I used the Cellular Monitor app and I can open the trace in Wireshark (Version 4.6.2) by using this button in cellular Monitor with no problem.

However, please find the additional traces attached below.

devzone.nordicsemi.com/.../trace_5F00_conexa.pcapng

devzone.nordicsemi.com/.../trace_5F00_soracom.pcapng

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Mon, 26 Jan 2026 11:29:17 GMT

Still empty;

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Wed, 14 Jan 2026 21:53:28 GMT

Please try this trace file instead

devzone.nordicsemi.com/.../trace_2D00_2026_2D00_01_2D00_13T12_2D00_33_2D00_11.702Z.mtrace

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Wed, 14 Jan 2026 12:38:06 GMT

Seems like the trace file is empty. So you will need to capture another modem trace.

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Wed, 14 Jan 2026 12:35:56 GMT

You can take any cellular sample and build it with modem trace snippet. I will check the trace file and see if it looks okay.

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Mon, 12 Jan 2026 13:11:35 GMT

How can I get a modem trace?

I installed the "thingy91x_hello.nrfcloud.com_v2.0.2_debug.hex" firmware, which is meant for debugging, I suppose. However, after flashing this file, I didn't receive any messages from the device anymore.

I just took this trace. Please let me know whether this trace is sufficient.

devzone.nordicsemi.com/.../trace_2D00_2026_2D00_01_2D00_13T12_2D00_27_2D00_18.522Z.mtrace

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Sun, 11 Jan 2026 17:00:02 GMT

Looks like you are not getting network connection. Can you please also provide a modem trace?

RE: Thingy:91X doesn't connect with nRF Cloud

Jacky_89 — Sat, 10 Jan 2026 00:59:53 GMT

Thank you for your reply.

I recorded this log via terminal and I attached a picture of the cellular monitor.

*** Using Zephyr OS v3.6.99-2fb756ef5c41 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
I: Verifying signature against key 0.
I: Hash: 0x3e...f9
I: Firmware signature verified.
Firmware version 2
Booting (0x8200).
[00:00:00.258,056] <inf> spi_nor: GD25LE255E@0: 32 MiBy flash
[00:00:00.409,820] <inf> wifi_nrf_bus: SPIM spi@b000: freq = 8 MHz
[00:00:00.409,881] <inf> wifi_nrf_bus: SPIM spi@b000: latency = 0
*** Booting Hello, nRF Cloud v3.0.1-83c8857e5f4b ***
*** Using nRF Connect SDK v3.1.0-6c6e5b32496e ***
*** Using Zephyr OS v4.1.99-1612683d4010 ***
[00:00:00.615,447] <dbg> trigger: init_entry: init_entry
[00:00:00.615,509] <dbg> led: normal_entry: normal_entry
[00:00:00.615,783] <dbg> led: led_pattern_update_work_fn: Setting LED effect: LED_OFF
[00:00:00.615,814] <dbg> app_led_pwm: led_pwm_set_effect: Power state: 0
[00:00:00.618,194] <dbg> fota: fota_task: FOTA module task started
[00:00:00.619,781] <dbg> app: app_task: Application module task started
[00:00:00.623,046] <dbg> battery: battery_task: Battery module task started
[00:00:00.632,354] <dbg> environmental_module: environmental_task: Environmental module task started
[00:00:00.641,601] <dbg> location_module: location_task: Location module task started
[00:00:00.667,327] <inf> network: Bringing network interface up and connecting to the network
[00:00:00.667,816] <dbg> shell: shell_task: Shell module task started
[00:00:00.667,999] <dbg> transport: transport_task: Transport module task started
[00:00:00.668,060] <dbg> transport: state_running_entry: state_running_entry
[00:00:00.668,395] <dbg> transport: state_disconnected_entry: state_disconnected_entry
[00:00:00.668,731] <dbg> trigger: trigger_callback: Received message on channel CLOUD_CHAN
[00:00:00.668,731] <dbg> trigger: trigger_callback: Running SMF
[00:00:00.668,762] <dbg> trigger: init_run: init_run
[00:00:00.669,860] <dbg> app: app_task: Cloud connection status received
[00:00:00.683,959] <dbg> location_module: location_task: location library initialized
[00:00:00.933,654] <inf> nrf_modem_lib_trace: Trace thread ready
[00:00:00.941,375] <inf> nrf_modem_lib_trace: Trace level override: 5
[00:00:01.024,200] <inf> wifi_nrf_bus: SPIM spi@b000: freq = 8 MHz
[00:00:01.024,230] <inf> wifi_nrf_bus: SPIM spi@b000: latency = 0
[00:00:01.272,949] <dbg> led: normal_running: normal_running
[00:00:01.272,979] <dbg> led: led_not_set_running: led_not_set_running
[00:00:01.272,979] <dbg> led: running_run: running_run
[00:00:01.273,101] <dbg> led: led_pattern_update_work_fn: Setting LED effect: LED_LTE_CONNECTING
[00:00:01.273,132] <dbg> app_led_pwm: led_pwm_set_effect: Power state: 1
[00:00:01.273,681] <dbg> location_module: location_task: Network status received
[00:00:01.273,803] <dbg> transport: state_disconnected_run: state_disconnected_run
[00:00:01.273,834] <dbg> transport: state_running_run: state_running_run
[00:00:01.273,864] <dbg> transport: state_disconnected_entry: state_disconnected_entry
[00:00:01.274,200] <dbg> trigger: trigger_callback: Received message on channel CLOUD_CHAN
[00:00:01.274,200] <dbg> trigger: trigger_callback: Running SMF
[00:00:01.274,230] <dbg> trigger: init_run: init_run
[00:00:01.275,238] <dbg> app: app_task: Cloud connection status received

RE: Thingy:91X doesn't connect with nRF Cloud

Hakon — Thu, 08 Jan 2026 12:38:53 GMT

Hello,

can you post application log to check if the device is connected to a network?