Tracker One stopped working abroad / keeps blinking green

I'm traveling to Iceland and brought my Particle Tracker One with me (EU/non-US band). It worked well on the first day but suddenly stopped connecting to the cloud and keeps blinking green for two days now.
I connected it to my computer and used the Particle CLI to check if I can debug it myself:

$ particle update
Updating tracker e00fce68557cd01815149452 to latest Device OS version
Downloaded Device OS 6.1.1
[█████████████████████████] 100% | Flash success!
Update success!

$ particle keys doctor
New key e00fce68557cd01815149452_ec_new.der created for device e00fce68557cd01815149452
Writing key to device
Writing key e00fce68557cd01815149452_ec_new.der to device e00fce68557cd01815149452
Saved existing key to backup_ec_e00fce68557cd01815149452_ec_new.der
Key e00fce68557cd01815149452_ec_new.der written to device
attempting to add a new public key for device e00fce68557cd01815149452
submitting public key succeeded!
Okay!  New keys in place, your device should restart.

$ particle identify
Your device id is e00fce68557cd01815149452
Your IMEI is 867648044132007
Your ICCID is 89883070000008809608
Your system firmware version is 6.1.1

I then used the Device Doctor to connect and generate the requested log file. Unfortunately, I'm not allowed to upload it here but it contains lines like these:

0000411785 [ncp.at] TRACE: > AT+CEER
0000411789 [ncp.at] TRACE: < +CEER: 5,38
0000411789 [ncp.at] TRACE: < OK
0000411790 [ncp.at] TRACE: > AT+CMEE?
0000411792 [ncp.at] TRACE: < +CMEE: 1
0000411792 [ncp.at] TRACE: < OK
0000411793 [ncp.at] TRACE: > AT+CREG?
0000411795 [ncp.at] TRACE: < +CREG: 2,5,"0133","0FE12E3",2
0000411795 [ncp.at] TRACE: < OK
0000411796 [ncp.at] TRACE: > AT+CEREG?
0000411798 [ncp.at] TRACE: < +CEREG: 2,4
0000411798 [ncp.at] TRACE: < OK
0000411799 [ncp.at] TRACE: > AT+QCSQ
0000411801 [ncp.at] TRACE: < +QCSQ: "WCDMA",81,-82,-3
0000411801 [ncp.at] TRACE: < OK
0000411901 [ncp.client] TRACE: NCP connection state changed: 2
0000411901 [mux] INFO: Mux channel 2 already opened
0000411902 [net.pppncp] TRACE: NCP event 100
0000411902 [net.pppncp] TRACE: New auth info
0000411904 [net.pppncp] TRACE: NCP event 2
0000411904 [net.pppncp] TRACE: State changed event: 2
0000411905 [net.ppp.client] TRACE: PPP thread event LOWER_UP
0000411905 [net.ppp.client] TRACE: State READY -> CONNECT
0000411906 [net.ppp.client] TRACE: State CONNECT -> CONNECTING
0000411906 [ncp.at] TRACE: > AT+CIMI
0000411907 [ncp.at] TRACE: < 234500011816662
0000411908 [ncp.at] TRACE: < OK
0000412162 [app.gps.nmea] TRACE: RX: $PUBX,00,203755.00,6533.18057,N,01926.86434,W,101.378,DR,11,13
0000412667 [app] TRACE: publishing from triggers
0000412910 [ncp.at] TRACE: > AT
0000412911 [ncp.at] TRACE: < OK
0000412912 [ncp.at] TRACE: > ATO
0000412914 [ncp.at] TRACE: < NO CARRIER
0000412914 [ncp.at] TRACE: > ATD*99***1#
0000412923 [ncp.at] TRACE: < CONNECT 150000000

I have other devices/smartphones with me and they work well; I couldn't tell if there's weak signal coverage.

I appreciate any idea what could be done to bring the device back online. Thanks!

I can't tell from that section of the log.

This indicates that it is searching for a carrier:

0000411798 [ncp.at] TRACE: < +CEREG: 2,4

This indicates a tower with WCDMA/HSDPA/HSPA. Assuming the RSSI is -82, that would be a fair signal strength.

0000411801 [ncp.at] TRACE: < +QCSQ: "WCDMA",81,-82,-3

I can't tell what happens next; it is possible that that carrier is not supported by EtherSIM.

Is this working now? It appears that the device was able to connect and there are call detail records for successful data transmission on Nova on the 7th.

Hi @rickkas7, thanks for checking the status in the background. It did work indeed the day after. I left it on the desk and it somehow managed to get back online. On my journey, I must have found another coverage hole, as I'm back with a blinking green device. I assume once it loses connectivity, it's stuck in a loop and I'm trying to get it out of its misery. Do you have an idea what's missing given these logs?

➜ particle serial monitor
Opening serial monitor for com port: " /dev/tty.usbmodem101 "
Serial monitor opened successfully:
0005729093 [system.nm] TRACE: Request to power on interface 5
0005730546 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005730611 [app.gps.ubx] INFO: UBX_NAV_SAT: 27 sats in view
0005731496 [ncp.esp32.at] TRACE: > AT
0005731498 [ncp.esp32.at] TRACE: < OK
0005731522 [net.pppncp] ERROR: PPP error event data=5
0005732499 [ncp.esp32.client] TRACE: NCP ready to accept AT commands
0005732500 [ncp.esp32.at] TRACE: > AT+MVER
0005732502 [ncp.esp32.at] TRACE: < 7
0005732503 [ncp.esp32.at] TRACE: < OK
0005732504 [ncp.esp32.at] TRACE: > AT+GETMAC=0
0005732506 [ncp.esp32.at] TRACE: < +GETMAC: "30:ae:a4:a9:df:5c"
0005732507 [ncp.esp32.at] TRACE: < OK
0005732510 [ncp.esp32.at] TRACE: > AT+CMUX=0
0005732512 [ncp.esp32.at] TRACE: < OK
0005732513 [ncp.esp32.mux] INFO: Starting GSM07.10 muxer
0005732514 [ncp.esp32.mux] INFO: Opening mux channel 0
0005732515 [ncp.esp32.mux] INFO: GSM07.10 muxer thread started
0005732520 [ncp.esp32.mux] INFO: Opening mux channel 1
0005732536 [ncp.esp32.at] TRACE: > AT
0005732545 [ncp.esp32.at] TRACE: < OK
0005732553 [ncp.esp32.at] TRACE: > AT+CWDHCP=0,3
0005732560 [ncp.esp32.at] TRACE: < OK
0005732560 [ncp.esp32.client] TRACE: NCP state changed: 1
0005732561 [system.nm] TRACE: Interface 5 power state changed: UP
0005732566 [ncp.esp32.at] TRACE: > AT+CWLAP
0005734449 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005734511 [app.gps.ubx] INFO: UBX_NAV_SAT: 27 sats in view
0005734675 [ncp.esp32.at] TRACE: < +CWLAP: <- snip (a couple of wlan ssids) ->
0005734694 [ncp.esp32.at] TRACE: < OK
0005735699 [app] INFO: cloud sent: {"cmd":"loc","time":1752167738,"loc":{"lck":1,"time":1752167729,"lat":65.23175000,"lon":-14.47122217,"alt":101.629,"hd":166.06,"spd":0.38,"h_acc":~
0005735701 [system.nm] TRACE: Request to power off interface 5
0005735702 [ncp.esp32.mux] INFO: Stopping GSM07.10 muxer
0005735702 [ncp.esp32.mux] INFO: Gracefully stopping GSM07.10 muxer
0005735702 [ncp.esp32.mux] INFO: Closing all muxed channels
0005735703 [ncp.esp32.mux] INFO: Closing mux channel 1
0005735703 [ncp.esp32.mux] INFO: Muxed channel 2 already closed
0005735704 [ncp.esp32.mux] INFO: Muxed channel 3 already closed
0005735704 [ncp.esp32.mux] INFO: Muxed channel 4 already closed
0005735713 [app] INFO: location cb publish 5735 failure
0005736975 [ncp.esp32.mux] INFO: Sending CLD (multiplexer close down)
0005736981 [ncp.esp32.mux] INFO: Received response to CLD or timed out, exiting multiplexed mode
0005736982 [ncp.esp32.mux] INFO: GSM07.10 muxer thread exiting
0005736982 [ncp.esp32.mux] INFO: GSM07.10 muxer stopped
0005736983 [system.nm] TRACE: Interface 5 power state changed: DOWN
0005736983 [ncp.esp32.client] TRACE: Deinit modem serial.
0005736984 [system.nm] TRACE: Interface 5 power state changed: POWERING_DOWN
0005736984 [system.nm] TRACE: Interface 5 power state changed: DOWN
0005736985 [ncp.esp32.client] TRACE: NCP state changed: 0
0005736985 [ncp.esp32.client] TRACE: Deinit modem serial.
0005739473 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005739567 [app.gps.ubx] INFO: UBX_NAV_SAT: 27 sats in view
0005739587 [app.gps.ubx] INFO: AOPSTATUS: iTOW:407759000ms, aopCfg:1, aopStatus:0
0005744477 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005744571 [app.gps.ubx] INFO: UBX_NAV_SAT: 27 sats in view
0005749480 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005749572 [app.gps.ubx] INFO: UBX_NAV_SAT: 26 sats in view
0005754475 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005754567 [app.gps.ubx] INFO: UBX_NAV_SAT: 26 sats in view
0005759480 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005759572 [app.gps.ubx] INFO: UBX_NAV_SAT: 26 sats in view
0005764472 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005764564 [app.gps.ubx] INFO: UBX_NAV_SAT: 26 sats in view
0005766548 [ncp.client] TRACE: NCP connection state changed: 1
0005766548 [net.pppncp] TRACE: NCP event 2
0005766549 [net.pppncp] TRACE: State changed event: 1
0005768249 [ncp.client] TRACE: NCP connection state changed: 2
0005768250 [mux] INFO: Mux channel 2 already opened
0005768250 [net.pppncp] TRACE: NCP event 100
0005768250 [net.pppncp] TRACE: New auth info
0005768252 [net.pppncp] TRACE: NCP event 2
0005768252 [net.pppncp] TRACE: State changed event: 2
0005769414 [app.gps.ubx] INFO: UBX_NAV_ORB: 68 sats in almanac
0005769468 [app.gps.ubx] INFO: UBX_NAV_SAT: 26 sats in view

I think I'll let it drain its battery over night and check again tomorrow.

I can't tell from that portion of the log. Prior to the beginning of the log it probably failed to connect because it reinitialized the cellular modem, which it does after 10 minutes of failing to connect. There are a bunch of messages for GNSS, which doesn't depend on cellular. After the end of the log there are probably some more cellular modem logs (mostly AT commands) that might have some information, but probably it's just unable to connect to a compatible tower.

Thanks, the logs pretty much keep repeating themselves. I found this one that could be of interest:

0008799480 [app.gps.ubx] INFO: AOPSTATUS: iTOW:410819000ms, aopCfg:1, aopStatus:0
0008802058 [net.pppncp] ERROR: PPP error event data=5
0008804296 [net.ppp.ipcp] ERROR: Peer NAK'd an option unknown to us

However, it doesn't say which of the option is unknown. Does that say anything to you?
Also, is there a command to restart the device via USB so that I don't have to wait until the battery is drained or use a screwdriver to get to the battery and quickly unplug it?