# Notecard syncing but with old data

**URL:** <https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248>\
**Category:** Uncategorized\
**Created:** [August 13, 2025, 1:18pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248 "2025-08-13T13:18:42Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 13, 2025, 1:18pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/1 "2025-08-13T13:18:42Z")

</div>

Hi. I have a behavior with my Notecard that has been powered on for approx 7 days on battery. Its set up to sync periodically and also track periodic. However, the data that is syncs is several days old.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/5/5a02eb2bdd839b26169283eea2ffb272d41a661d.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/0/07c12d3ae11dbf4bce483b3924bf411abe734952.png)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/4/4b82857b64bf57efe5089d25d3b94ab4d188d89c.png)

---

<div class="post-metadata">

**Author:** ![tjvantoll](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tjvantoll/32/231_2.png) [@tjvantoll](https://discuss.blues.com/u/tjvantoll)\
**Post date:** [August 13, 2025, 2:16pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/3 "2025-08-13T14:16:44Z")

</div>

Hey @TobiasR,

From this data I’m guessing that the Notecard has not been able to make a GPS fix for several days. You can confirm this by connecting your Notecard to the [In-Browser Terminal](https://dev.blues.io/terminal/) and running a [`card.location` request](https://dev.blues.io/api-reference/notecard-api/card-requests/latest/#card-location). The `time` returned from this request will have the most-recent location your Notecard has acquired.

If that is the case we’ll need to figure out why your Notecard hasn’t been able to make a GPS fix, but we’ll start by seeing what data you get back.

TJ

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 13, 2025, 2:33pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/4 "2025-08-13T14:33:27Z")

</div>

Thank you for quick reply.

Indeed, in the console, the location request returns the same data, from 2025-08-08. Turning on card.trace I could se it was saying something about GPS timeout.

I did FW update to latest LTS, then the card rebooted and got a new location fix pretty much instant.

But as seen in my screenshots its not only the location-data that is old. Also Volt and Temp.

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 13, 2025, 3:41pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/5 "2025-08-13T15:41:47Z")

</div>

I get the same now:

S107:38.47 sync: next wake-up due in 14m 20s to sync (outbound & inbound work pending)  
S117:15.13 journey: beginning new journey  
S117:15.13 sync: wakeup: gps poll  
S117:15.14 \_log.qo: gpsmax: requesting initial GPS refresh: period:300s c:0 f:0 m:1  
S117:15.14 sync: wakeup: gps initiate  
G117:15.30 accel: movements:6 free-falls:0 5s:1000000000000000000000000000000000000000000000000  
G117:43.29 accel: movements:7 free-falls:0 5s:1000010000000000000000000000000000000000000000000  
G118:30.25 journey: unless we start moving, the journey will end in 253 secs  
G118:49.03 journey: unless we start moving, the journey will end in 235 secs  
**G118:49.03 \_log.qo: gpsmax: cancelling GPS seek: no signal after 90 seconds**  
G118:49.06 track: 2025-08-13T15:30:01Z added note 1755098908:1 (4.73)  
G118:49.07 sync: wakeup: gps cancel

The board is located in the exact same spot where it got GPS-position when rebooting after firmware update.

---

<div class="post-metadata">

**Author:** ![tjvantoll](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tjvantoll/32/231_2.png) [@tjvantoll](https://discuss.blues.com/u/tjvantoll)\
**Post date:** [August 13, 2025, 5:17pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/6 "2025-08-13T17:17:04Z")

</div>

> But as seen in my screenshots its not only the location-data that is old. Also Volt and Temp.

The voltage and temperature readings in those screenshots are current, and were taken at the timestamp indicated in the `when` field. The `time` in the `body` just lists the time of the last GPS/GNSS fix.

> The board is located in the exact same spot where it got GPS-position when rebooting after firmware update.

Is your device indoors? In general, you need to have a clear view of the sky for Notecard to reliably get a GPS/GNSS fix. Personally I can usually get a fix when I have my Notecard near a window, but I have to take the device outside if I want it to reliably get a location.

You could consider using an active antenna to get a more reliable connection. See [our guide on GPS/GNSS antennas](https://dev.blues.io/datasheets/application-notes/antenna-guide/#gps-gnss-antennas) for more information.

TJ

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 13, 2025, 6:12pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/7 "2025-08-13T18:12:46Z")

</div>

Thank you.

From [https://dev.blues.io/api-reference/system-notefiles/#track-qo](https://dev.blues.io/api-reference/system-notefiles/#track-qo)

 ![image](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/b/b4cd59418e554733429627e5856a5c35ba17620d.png)

As you say, the temp and voltage reading is from when the last position was fixed (“when”), not when the _actual tracking event_ occurred as stated in the doc’s, if I understand it correctly.

Yes, the device is indoors, by the window. It has no problems getting a GPS fix on that spot after a reboot or setting it in continuous position mode. Its in periodic/track it stops getting position after a while and outputs " \_log.qo: gpsmax: cancelling GPS seek: no signal after 90 seconds".

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 13, 2025, 6:26pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/8 "2025-08-13T18:26:52Z")

</div>

More on the issue not getting GPS fix when in periodic mode. As seen bellow, the card does “gpsmax: cancelling GPS seek: no signal after 90 seconds” when in periodic mode (its been doing that for several days). As soon as a fire a manual “sync” its gets position.

T278:43.15 lwip: IP deactivated to conserve energy  
S285:14.09 journey: beginning new journey  
**S285:14.09 sync: wakeup: gps poll**  
S285:14.10 \_log.qo: gpsmax: requesting initial GPS refresh: period:300s c:0 f:0 m:1  
**S285:14.10 sync: wakeup: gps initiate**  
S285:14.18 sync: next wake-up due in 15m 0s to check on journey’s progress  
G285:14.26 accel: movements:10 free-falls:0 5s:10000000000000000000000000000000  
G285:57.49 journey: unless we start moving, the journey will end in 257 secs  
G286:12.57 journey: unless we start moving, the journey will end in 242 secs  
G286:27.64 journey: unless we start moving, the journey will end in 227 secs  
G286:42.70 journey: unless we start moving, the journey will end in 212 secs  
**G286:44.59 \_log.qo: gpsmax: cancelling GPS seek: no signal after 90 seconds**  
G286:44.68 track: 2025-08-13T18:17:57Z added note 1755108987:1 (4.73)  
**G286:44.68 sync: wakeup: gps cancel**  
G286:44.69 \_log.qo: gpsmax: requesting initial GPS refresh: period:300s c:0 f:0 m:0  
G286:44.69 sync: wakeup: gps initiate  
S286:44.70 sync: next wake-up due in 15m 0s to check on journey’s progress  
G286:58.82 journey: unless we start moving, the journey will end in 196 secs  
G287:17.60 journey: unless we start moving, the journey will end in 177 secs  
G287:36.38 journey: unless we start moving, the journey will end in 158 secs  
**sync**  
R287:47.57 sync: wakeup: diag sync  
S287:47.59 transport: using celluar transport because GPS is needed  
S287:47.59 transport: switched from wifi: to modem:  
S287:47.59 transport: using celluar transport because GPS is needed  
S287:47.63 sync: connect requested by explicit sync request (DATA)  
S287:47.65 connect: 4.70V 29.06C before comms power-on (2025-08-13T18:19:00Z UTC)  
S287:47.65 transport: using celluar transport because GPS is needed  
S287:47.65 apn: for [a.notefile.net](http://a.notefile.net) using apn a-notehub.com.attz  
S287:47.66 sync: wireless: domain [a.notefile.net](http://a.notefile.net) using APN a-notehub.com.attz  
S287:47.66 sync: wireless: starting communications {wait-module} {connecting} {transport}  
S287:47.68 modem: beginning power-on sequence  
S287:52.39 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
S287:52.39 sync: wireless: modem now ON {modem-on}  
S287:52.74 journey: unless we start moving, the journey will end in 142 secs  
S287:52.79 env: updated \_state\_vars\_net  
S287:52.80 env: dfu updated  
M288:09.56 modem: wireless: waiting for wireless service {wait-service} {connecting} {transport}  
M288:10.46 modem: wireless: waiting for wireless service 23 sec [----] {cell-registration-wait}  
M288:13.48 modem: wireless: waiting for data service {wait-data} {connecting} {transport}  
M288:13.57 lwip: tcp task activated  
M288:13.72 S288:13.78 checkpointAllNoteboxes {checkpointed} \_env.dbs  
modem: wireless: network registration took 26 sec  
M288:13.79 modem: wireless: connected {connected-closed} {transport}  
M288:13.79 sync: wakeup: modem connected  
S288:13.89 lwip: setting wideband timeouts  
T288:14.80 tcpip: network: IP local:10.68.60.169 remote:10.64.64.64  
T288:14.81 tcpip: network: IP connect\_status: connected (0)  
S288:14.81 sync: network: IP connect: waiting for connection for 0 sec (sent:191 rcvd:213)  
S288:14.91 sync: network: IP socket connect: success in 1 sec (sent:236 rcvd:258)  
S288:14.92 lwip: opened  
S288:14.92 sync: network: notebox open PPP (sent:236 rcvd:258) {socket-ip-init}  
S288:14.92 sync: project: opening notehub session using product UID product:se..tobias.radenholt:tracker  
S288:14.93 sync: notehub: asking discovery service to assign a notehub session handler  
S288:14.93 sync: network: opening unidirectionally-authenticated secure session to [a.notefile.net:8086](http://a.notefile.net:8086) {socket-open-session}  
S288:14.94 sync: network: resolving tracker.radenholt.tobias..se.product.notefile.net  
S288:15.57 sync: network: resolving [a.notefile.net](http://a.notefile.net)  
S288:15.88 sync: network: DNS lookup of [a.notefile.net](http://a.notefile.net) yielded 10.0.66.13 {socket-dns-success}  
S288:15.89 sync: network: connecting to 10.0.66.13:8086 {socket-connecting}  
S288:16.20 sync: network: connected to 10.0.66.13 (sent:94 rcvd:113) {socket-connected}  
S288:16.31 hsm: secure element enabled  
S288:16.41 sync: network: TLS using ECC curve NIST P384  
S288:16.41 sync: network: TLS cert issuer: /C=NL/O=STMicroelectronics nv/CN=STM STSAFE-A PROD CA 25  
S288:16.42 sync: network: TLS cert subject: /CN=NB1/serialNumber=0209a02ba039dc52c60139  
S288:16.42 sync: network: connect using TLS {socket-tls-connecting}  
S288:17.01 sync: network: TLS is verifying the service  
S288:17.03 sync: network: TLS domain ([a.notefile.net](http://a.notefile.net)) matches hub’s certificate (_.notefile.net) through wildcard  
S288:18.27 sync: network: connected using TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256 {socket-tls-connected}  
S288:18.27 hsm: secure element disabled  
S288:18.28 sync: network: tls authenticated (sent:950 rcvd:2887) {socket-tls}  
S288:18.28 sync: network: session opened {socket-opened-session}  
S288:18.29 tower: req: 240,1,807,26352160,-72,16,-95,-9,lte,0,2,89011704274021110862,a-notehub.com.attz,10.68.60.169  
S288:18.29 ntn: config pv1,0,chacha20-poly1305,(64)  
S288:18.30 discover session handler for dev:351077454475164 product:se.e.tobias.radenholt:tracker  
S288:19.23 sync: network: request socket shutdown {socket-disconnected}  
S288:19.23 sync: network: session closed {socket-closed-session}  
S288:19.27 sync: notehub: discovery service assigned a session handler  
S288:19.27 ntn: handler 216.245.146.112:8089,256,YN,10TPM,1,c32db66fdb45  
S288:19.27 sync: notehub: time is behind local time by -3 seconds  
S288:19.28 notehub time: 1755109175  
S288:19.28 sync: notehub: session ticket issued for 604803 sec (now:1755109172 expires:1755713975)  
S288:19.29 sync: network: opening unidirectionally-authenticated secure session to 10.0.34.13:31566 {socket-open-session}  
S288:19.29 sync: network: connecting to 10.0.34.13:31566 {socket-connecting}  
S288:19.60 sync: network: connected to 10.0.34.13 (sent:138 rcvd:45) {socket-connected}  
S288:19.71 hsm: secure element enabled  
S288:19.82 sync: network: TLS using ECC curve NIST P384  
S288:19.82 sync: network: TLS cert issuer: /C=NL/O=STMicroelectronics nv/CN=STM STSAFE-A PROD CA 25  
S288:19.83 sync: network: TLS cert subject: /CN=NB1/serialNumber=0209a02ba039dc52c60139  
S288:19.83 sync: network: connect using TLS {socket-tls-connecting}  
S288:20.40 sync: network: TLS is verifying the service  
S288:20.43 sync: network: TLS domain ([a.notefile.net](http://a.notefile.net)) matches hub’s certificate (_.notefile.net) through wildcard  
S288:21.68 sync: network: connected using TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256 {socket-tls-connected}  
S288:21.68 hsm: secure element disabled  
S288:21.69 sync: network: tls authenticated (sent:951 rcvd:2886) {socket-tls}  
S288:21.69 sync: network: session opened {socket-opened-session}  
S288:21.69 tower: req: 240,1,807,26352160,-72,16,-95,-9,lte,0,2,89011704274021110862,a-notehub.com.attz,10.68.60.169  
S288:21.70 sync: notehub: opened notehub {notehub-connected}  
S288:21.70 sync: sync triggered by explicit sync request (\_track.qo \_env.dbs)  
S288:21.71 sync: work: begin (anything pending) {sync-begin}  
S288:21.71 sync: request: get notebox change summary  
S288:22.20 tower: rsp: 9F7JXQ63+924W|SE|Europe/Stockholm|CEST|120|Skåne County  
S288:22.20 407 req + 62 rsp = 469 byte network transaction  
S288:22.24 sync: work to be done:  
S288:22.24 upload \_env.dbs  
S288:22.25 upload \_track.qo  
S288:22.29 checkpointAllNoteboxes {checkpointed} \_notefiles.json  
I288:22.30 inbound: listening for notehub changes  
S288:22.44 sync: work: upload \_env.dbs (1 changes) {sync-get-local-changes}  
S288:22.44 sync: request: merge notefile: \_env.dbs  
S288:22.82 274 req + 1 rsp = 275 byte network transaction  
S288:22.90 sync: work: upload \_track.qo (1 changes) {sync-get-local-changes}  
S288:22.91 sync: request: merge notefile: \_track.qo  
S288:23.31 607 req + 1 rsp = 608 byte network transaction  
S288:23.31 purge \_track.qo:  
S288:23.32 1 notes (0 stable, 0 queued, 1 tombstones)  
S288:23.32 → 0 notes (0 stable, 0 queued, 0 tombstones)  
S288:23.47 sync: work to be done:  
S288:23.47 upload \_env.dbs  
S288:23.48 upload \_track.qo  
S288:23.54 deleting /data/\_track-qo.000  
S288:23.54 sync: work: completed {sync-end}  
S288:23.55 sync: advancing last sync time from 18:09:44Z to 18:19:36Z  
S288:23.55 journey: unless we start moving, the journey will end in 111 secs  
S288:23.73 lwip: waiting for mbox to be idle (msgs:0 queues:2 sems:1 mutexes:1)  
S288:24.29 sync: network: request socket shutdown {socket-disconnected}  
S288:24.29 sync: network: session closed {socket-closed-session}  
S288:24.30 sync: notehub: closed notehub {notehub-disconnected}  
S288:24.30 lwip: sending RST to remote host packet:10840 ackno:4090045482  
S288:24.83 lwip: closed  
S288:24.83 sync: network: LWIP terminated (sent:74 rcvd:17) {socket-ip-term}  
S288:24.83 lwip: tcp task deactivated (msgs:0 queues:1 sems:0 mutexes:1)  
S288:24.84 sync: wireless: modem disconnect requested {cell-disconnect-begin}  
S288:24.84 sync: wireless: idle {disconnecting} {transport}  
S288:24.84 sync: wireless: idle {disconnected} {transport}  
S288:25.29 modem: waiting for shutdown  
M288:25.30 modem: wireless: idle {disconnecting} {transport}  
M288:25.63 modem: powering down  
M288:25.69 modem: waiting 5 secs for modem soft-powerdown quiescence  
M288:30.69 usage: adding 4706+7085=11791 to sent+rcvd bytes [1822857/2040411]  
M288:30.70 usage: adding 2+2=4 to TCP/TLS sessions [565/533]  
M288:30.70 usage: adding 6+0=6 to sent+rcvd notes [1742/44]  
M288:30.70 modem: wireless: modem now OFF {modem-off}  
M288:30.71 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
M288:30.71 modem: active for 43 sec  
M288:30.71 modem: user tx+rx=total: 1777+219=1996 (15.9% of total)  
M288:30.72 modem: tls tx+rx=total: 3514+5831=9345 (overhead of 7349, 58.5% of total)  
M288:30.72 modem: ppp tx+rx=total: 5119+7440=12559 (overhead of 3214, 25.6% of total)  
M288:30.73 modem: ota tx+rx=total: 4706+7085=11791 (to/from tower, not to/from modem)  
M288:30.73 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
T288:35.04 lwip: IP deactivated to conserve energy  
M288:35.77 sync: wakeup: modem shutdown  
M288:35.87 modem: wireless: idle {disconnected} {transport}  
S288:35.89 sync: wireless: modem disconnected {cell-disconnected}  
S288:36.51 sync: network: LWIP terminated (sent:0 rcvd:0) {socket-ip-term}  
S288:36.53 transport: using celluar transport because GPS is needed  
S288:36.54 sync: connect requested by GPS (GPS)  
S288:36.55 connect: 4.71V 29.06C before comms power-on (2025-08-13T18:19:49Z UTC)  
S288:36.55 transport: using celluar transport because GPS is needed  
S288:36.55 apn: for [a.notefile.net](http://a.notefile.net) using apn a-notehub.com.attz  
S288:36.56 sync: wireless: domain [a.notefile.net](http://a.notefile.net) using APN a-notehub.com.attz  
S288:36.56 sync: wireless: starting communications {wait-module} {connecting} {transport}  
S288:36.57 modem: beginning power-on sequence  
S288:41.29 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
S288:41.29 sync: wireless: modem now ON {modem-on}  
S288:41.64 journey: unless we start moving, the journey will end in 93 secs  
M288:55.52 modem: suppressing registration  
S288:56.16 journey: unless we start moving, the journey will end in 78 secs  
M288:59.51 gpsmax: modem powered up in gps mode  
M288:59.56 \_log.qo: gpsmax: NMEA data being received  
M288:59.56 GPS search (0 sec, 0/0 dB SNR, 0/0 sats, HDOP 0.00)  
M288:59.59 modem: wireless: connected {connected-closed} {transport}  
M288:59.60 \_log.qo: gpsmax: requesting GPS refresh: modem’s GPS is ready  
S288:59.68 sync: next wake-up due in 15m 0s to check on journey’s progress  
**M289:04.57 GPS search (5 sec, 45/45 dB SNR, 0/2 sats, HDOP 0.00)**  
M289:09.57 GPS search (10 sec, 45/45 dB SNR, 0/4 sats, HDOP 0.00)  
G289:13.68 journey: unless we start moving, the journey will end in 61 secs  
M289:14.57 GPS search (15 sec, 45/45 dB SNR, 0/4 sats, HDOP 0.00)  
M289:19.57 GPS search (20 sec, 45/45 dB SNR, 0/5 sats, HDOP 0.00)  
M289:24.66 GPS search (25 sec, 45/45 dB SNR, 0/6 sats, HDOP 0.00)  
**M289:24.68 \_log.qo: GPS updated to 9F7JXQC8+22J8 ($GPGGA, 0 sats, 45db)**  
M289:24.68 gps: adding track note  
S289:24.76 sync: next wake-up due in 15m 0s to check on journey’s progress  
M289:24.79 track: 2025-08-13T18:20:37Z added note 1755108987:2 (4.62)  
M289:24.80 sync: wakeup: gps update (no refresh needed)  
S289:25.32 sync: network: LWIP terminated (sent:0 rcvd:0) {socket-ip-term}  
S289:25.32 sync: wireless: modem disconnect requested {cell-disconnect-begin}  
S289:25.33 sync: wireless: idle {disconnecting} {transport}  
S289:25.33 sync: wireless: idle {disconnected} {transport}  
S289:25.33 sync: wireless: idle {disconnecting} {transport}  
S289:25.37 modem: waiting for shutdown  
M289:25.48 gps: modem powering down  
M289:25.53 modem: waiting 5 secs for modem soft-powerdown quiescence  
G289:29.46 journey: unless we start moving, the journey will end in 45 secs  
M289:30.53 modem: wireless: modem now OFF {modem-off}  
M289:30.54 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
M289:30.54 modem: active for 53 sec  
M289:30.55 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
M289:35.58 sync: wakeup: modem shutdown  
M289:35.69 modem: wireless: idle {disconnected} {transport}  
S289:35.78 sync: wireless: modem disconnected {cell-disconnected}  
S289:35.79 sync: next wake-up due in 15m 0s to check on journey’s progress

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 13, 2025, 6:47pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/9 "2025-08-13T18:47:52Z")

</div>

More interesting findings on the “old data” topic. Look at these two track notes:

 ![image](https://us1.discourse-cdn.com/flex020/uploads/blues/original/2X/d/d9c65bc29d286d994c56d6caa77be1e717fba4a2.png)

Temp has changed, but Voltage has not. 🙃 Seems like Temp belongs to the time when the tracking note was created and Voltage belongs to the time when the latest GPS fix was achieved.

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 14, 2025, 2:27pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/10 "2025-08-14T14:27:13Z")

</div>

Same again. Been sitting for ~24 hours on battery and not updated GPS-position once (and thus not Temp). When hooking up USB I get this:

Welcome to the Notecard In-Browser Terminal.  
Start making requests below.  
(For advanced info, use the ‘help’ command.)  
~ Connected to serial  
~ Sync Status Monitor enabled  
S1483:22.56 {“cmd”:“echo”,“id”:2000000000,“text”:“hi”}  
**{“req”:“card.trace”,“mode”:“on”}**  
{“stop”:true}  
~ DeviceUID dev:351077454475164 (NOTE-WBGLWT) running firmware 8.2.2.17315  
Hint: A newer firmware, notecard-u5-8.2.3 (LTS8 (Latest LTS)), is available. Run ‘firmware install latest’ to update.  
**S1487:53.19 sync: wakeup: gps poll**  
S1487:53.20 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1487:53.28 accel: movements:44 free-falls:0 5s:1000000000000000000000000000000000000000000000000  
S1488:20.64 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1488:20.71 accel: movements:45 free-falls:0 5s:1000001000000000000000000000000000000000000000000  
G1488:21.28 accel: movements:46 free-falls:0 5s:2000001000000000000000000000000000000000000000000  
G1489:17.57 journey: unless we start moving, the journey will end in 244 secs  
G1490:13.86 journey: unless we start moving, the journey will end in 188 secs  
G1490:13.86 sync: wakeup: gps poll  
S1490:13.89 sync: next wake-up due in 15m 0s to check on journey’s progress  
S1490:25.04 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1490:25.12 accel: movements:47 free-falls:0 5s:1000000000000000000000000200000100000000000000000  
G1490:25.30 accel: movements:49 free-falls:0 5s:3000000000000000000000000200000100000000000000000  
**G1490:50.65 \_log.qo: gpsmax: requesting initial GPS refresh: period:300s c:0 f:0 m:6**  
**G1490:50.65 sync: wakeup: gps initiate**  
S1490:50.68 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1491:09.47 journey: unless we start moving, the journey will end in 256 secs  
G1491:28.24 journey: unless we start moving, the journey will end in 238 secs  
G1491:47.02 journey: unless we start moving, the journey will end in 219 secs  
G1492:05.80 journey: unless we start moving, the journey will end in 200 secs  
G1492:15.19 sync: wakeup: gps poll  
S1492:15.22 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1492:24.62 journey: unless we start moving, the journey will end in 181 secs  
**G1492:24.62 \_log.qo: gpsmax: cancelling GPS seek: no signal after 90 seconds**  
G1492:24.65 track: 2025-08-14T14:23:35Z added note 1755180874:2 (4.72)  
**G1492:24.65 sync: wakeup: gps cancel**  
S1492:24.67 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1493:20.97 journey: unless we start moving, the journey will end in 125 secs  
G1494:17.26 journey: unless we start moving, the journey will end in 69 secs

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 14, 2025, 3:01pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/11 "2025-08-14T15:01:23Z")

</div>

More findings:  
If I move the device (acceleration detected) and see that it tries to do a GPS poll in the serial monitor, then I make a manual sync straight away, it activates the GPS and get a position fix. The fix comes to late though, as the sync has already passed. Please see bellow.

**info**  
~ Blues Wireless Notecard  
~ ProductUID: se.se.karlit.tobias:tracker:tracker  
~ DeviceUID: dev:351077454475164  
~ Serial Number:  
~ Notehub Host: [a.notefile.net](http://a.notefile.net)  
~ Firmware Version: notecard-8.2.2.17315  
~ SKU: NOTE-WBGLWT  
~ Modem: WFM200.3.16.0  
~ IMEI/MAC: 94:DE:B8:26:A0:FA  
~ Provisioned: Sun Jul 27 2025 11:05:13 GMT+0200 (Central European Summer Time) (2025-07-27T09:05:13.000Z)  
~ Used Over-the-Air: 4008686 bytes  
~ Sync Mode: periodic  
~ Sync Upload Period: 60 minutes  
~ Download Period: 60 minutes  
~ Notehub Status: idle (since 2025-08-14T14:51:00Z) {disconnected} {idle}  
~ Last Synced: Thu Aug 14 2025 16:51:03 GMT+0200 (Central European Summer Time) (2025-08-14T14:51:03.000Z)  
~ Voltage: 4.70V  
~ Temperature: 30.63C  
~ GPS Mode: periodic  
~ Location: 55.96997811666667,12.764637233333332  
~ Current Time: Thu Aug 14 2025 16:51:16 GMT+0200 (Central European Summer Time) (2025-08-14T14:51:16.000Z)  
~ Boot Time: Wed Aug 13 2025 15:30:01 GMT+0200 (Central European Summer Time) (2025-08-13T13:30:01.000Z)  
~ Notefiles:  
~ Notefile Storage Used: 2%  
~ Env: {  
~ “\_tri\_mins”: “1440”,  
~ “\_comment”: “Card 1”  
~ }  
S1520:27.52 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1520:27.60 accel: movements:58 free-falls:0 5s:1000000000101000100000000000000000000000000000000  
**G1520:51.08 \_log.qo: gpsmax: requesting initial GPS refresh: period:300s c:0 f:0 m:4**  
G1520:51.08 sync: wakeup: gps initiate  
S1520:51.10 sync: next wake-up due in 15m 0s to check on journey’s progress  
S1520:58.78 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1520:58.86 accel: movements:59 free-falls:0 5s:1000000100000000010100010000000000000000000000000  
**sync**  
R1521:02.21 sync: wakeup: diag sync  
S1521:02.22 transport: using celluar transport because GPS is needed  
S1521:02.22 transport: switched from wifi: to modem:  
**S1521:02.22 transport: using celluar transport because GPS is needed**  
S1521:02.26 sync: connect requested by explicit sync request (DATA)  
S1521:02.27 connect: 4.69V 30.63C before comms power-on (2025-08-14T14:52:13Z UTC)  
S1521:02.28 transport: using celluar transport because GPS is needed  
S1521:02.28 apn: for [a.notefile.net](http://a.notefile.net) using apn a-notehub.com.attz  
S1521:02.28 sync: wireless: domain [a.notefile.net](http://a.notefile.net) using APN a-notehub.com.attz  
S1521:02.29 sync: wireless: starting communications {wait-module} {connecting} {transport}  
S1521:02.30 modem: beginning power-on sequence  
S1521:07.01 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
S1521:07.02 sync: wireless: modem now ON {modem-on}  
S1521:07.37 sync: wakeup: gps poll  
S1521:07.42 env: updated \_state\_vars\_net  
S1521:07.42 env: dfu updated  
M1521:20.78 modem: powered up in data mode  
M1521:23.00 modem: wireless: waiting for wireless service {wait-service} {connecting} {transport}  
M1521:24.94 modem: wireless: waiting for wireless service 23 sec [----] {cell-registration-wait}  
M1521:27.55 modem: wireless: waiting for data service {wait-data} {connecting} {transport}  
M1521:27.59 lwip: tcp task activated  
S1521:27.94 lwip: setting wideband timeouts  
T1521:28.85 tcpip: network: IP local:10.68.62.102 remote:10.64.64.64  
T1521:28.86 tcpip: network: IP connect\_status: connected (0)  
S1521:28.86 sync: network: IP socket connect: success in 0 sec (sent:236 rcvd:257)  
S1521:28.87 lwip: opened  
S1521:28.87 sync: network: notebox open PPP (sent:236 rcvd:229) {socket-ip-init}  
S1521:28.88 sync: project: opening notehub session using product UID product:se.se.karlit.tobias:tracker:tracker  
S1521:28.88 sync: notehub: asking discovery service to assign a notehub session handler  
S1521:28.88 sync: network: opening unidirectionally-authenticated secure session to [a.notefile.net:8086](http://a.notefile.net:8086) {socket-open-session}  
S1521:28.89 sync: network: resolving [tracker.radenholt.tobias.karlite.se.product.notefile.net](http://tracker.radenholt.tobias.karlite.se.product.notefile.net)  
T1521:29.28 lwip: $$$ received unexpected UDP packet  
S1521:29.55 sync: network: resolving [a.notefile.net](http://a.notefile.net)  
S1521:29.87 sync: network: DNS lookup of [a.notefile.net](http://a.notefile.net) yielded 10.0.66.13 {socket-dns-success}  
S1521:29.87 sync: network: connecting to 10.0.66.13:8086 {socket-connecting}  
S1521:30.19 sync: network: connected to 10.0.66.13 (sent:94 rcvd:113) {socket-connected}  
S1521:30.30 hsm: secure element enabled  
S1521:30.41 sync: network: TLS using ECC curve NIST P384  
S1521:30.41 sync: network: TLS cert issuer: /C=NL/O=STMicroelectronics nv/CN=STM STSAFE-A PROD CA 25  
S1521:30.41 sync: network: TLS cert subject: /CN=NB1/serialNumber=0209a02ba039dc52c60139  
S1521:30.42 sync: network: connect using TLS {socket-tls-connecting}  
S1521:31.00 sync: network: TLS is verifying the service  
S1521:31.03 sync: network: TLS domain ([a.notefile.net](http://a.notefile.net)) matches hub’s certificate (_.notefile.net) through wildcard  
S1521:32.28 sync: network: connected using TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256 {socket-tls-connected}  
S1521:32.28 hsm: secure element disabled  
S1521:32.29 sync: network: tls authenticated (sent:954 rcvd:2887) {socket-tls}  
S1521:32.30 sync: network: session opened {socket-opened-session}  
S1521:32.30 tower: req: 240,1,807,26352160,-64,9,-94,-13,lte,0,2,89011704274021110862,a-notehub.com.attz,10.68.62.102  
S1521:32.30 ntn: config pv1,0,chacha20-poly1305,(64)  
S1521:32.31 discover session handler for dev:351077454475164 product:se.se.karlit.tobias:tracker:tracker  
S1521:33.24 sync: network: request socket shutdown {socket-disconnected}  
S1521:33.25 sync: network: session closed {socket-closed-session}  
S1521:33.29 sync: notehub: discovery service assigned a session handler  
S1521:33.29 ntn: handler 216.245.146.112:8089,256,YN,10TPM,1,c32db66fdb45  
S1521:33.30 sync: notehub: time is behind local time by -10 seconds  
S1521:33.30 sync: notehub: adjusting time from notehub (-10 seconds)  
S1521:33.30 time-set: 1755183174 2025-08-14T14:52:54Z  
S1521:33.31 notehub time: 1755183174  
S1521:33.31 sync: notehub: session ticket issued for 604800 sec (now:1755183174 expires:1755787974)  
S1521:33.32 sync: network: opening unidirectionally-authenticated secure session to 10.0.34.7:23080 {socket-open-session}  
S1521:33.32 sync: network: connecting to 10.0.34.7:23080 {socket-connecting}  
S1521:34.45 sync: network: TLS is verifying the service  
S1521:34.47 sync: network: TLS domain ([a.notefile.net](http://a.notefile.net)) matches hub’s certificate (_.notefile.net) through wildcard  
S1521:35.70 sync: network: connected using TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256 {socket-tls-connected}  
S1521:35.70 hsm: secure element disabled  
S1521:35.71 sync: network: tls authenticated (sent:953 rcvd:2886) {socket-tls}  
S1521:35.71 sync: network: session opened {socket-opened-session}  
S1521:35.72 tower: req: 240,1,807,26352160,-64,9,-94,-13,lte,0,2,89011704274021110862,a-notehub.com.attz,10.68.62.102  
S1521:35.72 sync: notehub: opened notehub {notehub-connected}  
S1521:35.72 sync: sync triggered by explicit sync request (\_env.dbs)  
S1521:35.73 sync: work: begin (anything pending) {sync-begin}  
S1521:35.73 sync: request: get notebox change summary  
S1521:35.73 journey: unless we start moving, the journey will end in 264 secs  
S1521:36.24 tower: rsp: 9F7JXQ63+924W|SE|Europe/Stockholm|CEST|120|Skåne County  
S1521:36.24 399 req + 75 rsp = 474 byte network transaction  
S1521:36.24 sync: request: resetting all trackers because of session ID mismatch  
S1521:36.32 sync: work to be done:  
S1521:36.32 upload-notebox  
S1521:36.33 upload-notebox  
S1521:36.33 download-notebox  
S1521:36.34 upload \_env.dbs  
S1521:36.34 upload \_health.qo  
S1521:36.35 upload \_health\_host.qo  
S1521:36.36 upload \_log.qo  
S1521:36.36 upload \_temp.qo  
S1521:36.37 upload \_track.qo  
S1521:36.38 download \_env.dbs  
S1521:36.41 checkpointAllNoteboxes {checkpointed} \_log.qo  
I1521:36.41 inbound: listening for notehub changes  
S1521:36.64 checkpointAllNoteboxes {checkpointed} \_track.qo  
S1521:36.79 checkpointAllNoteboxes {checkpointed} \_notefiles.json  
S1521:36.91 checkpointAllNoteboxes {checkpointed} \_temp.qo  
S1521:37.04 checkpointAllNoteboxes {checkpointed} \_health\_host.qo  
S1521:37.16 checkpointAllNoteboxes {checkpointed} \_health.qo  
S1521:37.31 checkpointAllNoteboxes {checkpointed} \_env.dbs  
S1521:37.42 sync: work: upload-notebox (20 changes) {sync-get-local-changes}  
S1521:37.45 sync: request: merge notebox  
S1521:37.94 1130 req + 1 rsp = 1131 byte network transaction  
S1521:38.10 checkpointAllNoteboxes {checkpointed} \_notefiles.json  
S1521:38.21 sync: request: get notebox changes  
S1521:38.71 6 req + 1101 rsp = 1107 byte network transaction  
S1521:38.72 sync: work: download-notebox (20 changes) {sync-get-remote-changes}  
S1521:38.75 sync: request: update notebox change tracker  
S1521:39.09 10 req + 1 rsp = 11 byte network transaction  
S1521:39.14 sync: work: upload \_env.dbs (5 changes) {sync-get-local-changes}  
S1521:39.16 sync: request: merge notefile: \_env.dbs  
S1521:39.70 2124 req + 1 rsp = 2125 byte network transaction  
S1521:40.04 sync: request: get notefile changes: \_env.dbs  
S1521:40.65 16 req + 2202 rsp = 2218 byte network transaction  
S1521:40.65 sync: work: download \_env.dbs (5 changes) {sync-get-remote-changes}  
S1521:40.67 sync: request: update change tracker: \_env.dbs  
S1521:41.01 20 req + 1 rsp = 21 byte network transaction  
S1521:41.04 sync: work to be done:  
S1521:41.04 upload-notebox  
S1521:41.05 upload \_env.dbs  
S1521:41.05 upload \_health.qo  
S1521:41.06 upload \_health\_host.qo  
S1521:41.07 upload \_log.qo  
S1521:41.07 upload \_temp.qo  
S1521:41.08 upload \_track.qo  
S1521:41.09 download \_env.dbs  
S1521:41.25 sync: request: get notefile changes: \_env.dbs  
S1521:41.61 16 req + 26 rsp = 42 byte network transaction  
S1521:41.61 sync: work: completed {sync-end}  
S1521:41.61 sync: sync triggered by explicit sync request (\_env.dbs)  
S1521:41.62 sync: work: begin (anything pending) {sync-begin}  
S1521:41.62 sync: request: get notebox change summary  
S1521:41.98 18 req + 1 rsp = 19 byte network transaction  
S1521:42.03 checkpointAllNoteboxes {checkpointed} \_notefiles.json  
S1521:42.23 sync: work: completed (nothing was pending) {sync-end}  
S1521:42.24 sync: advancing last sync time from 14:51:01Z to 14:53:02Z  
S1521:42.71 sync: network: request socket shutdown {socket-disconnected}  
S1521:42.72 sync: network: session closed {socket-closed-session}  
S1521:42.72 sync: notehub: closed notehub {notehub-disconnected}  
S1521:42.72 lwip: sending RST to remote host packet:31707 ackno:1681068100  
S1521:43.25 lwip: closed  
S1521:43.25 sync: network: LWIP terminated (sent:74 rcvd:18) {socket-ip-term}  
S1521:43.26 lwip: tcp task deactivated (msgs:0 queues:1 sems:0 mutexes:1)  
S1521:43.26 sync: wireless: modem disconnect requested {cell-disconnect-begin}  
S1521:43.27 sync: wireless: idle {disconnecting} {transport}  
S1521:43.27 sync: wireless: idle {disconnected} {transport}  
S1521:43.71 modem: waiting for shutdown  
M1521:43.72 modem: wireless: idle {disconnecting} {transport}  
M1521:44.03 modem: powering down  
M1521:44.08 modem: waiting 5 secs for modem soft-powerdown quiescence  
M1521:49.08 usage: adding 7895+11151=19046 to sent+rcvd bytes [1902455/2125277]  
M1521:49.09 usage: adding 2+2=4 to TCP/TLS sessions [592/560]  
M1521:49.09 usage: adding 5+0=5 to sent+rcvd notes [1812/44]  
M1521:49.10 modem: wireless: modem now OFF {modem-off}  
M1521:49.10 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
M1521:49.11 modem: active for 46 sec  
M1521:49.11 modem: user tx+rx=total: 4219+3562=7781 (39.0% of total)  
M1521:49.11 modem: tls tx+rx=total: 6161+9348=15509 (overhead of 7728, 38.7% of total)  
M1521:49.12 modem: ppp tx+rx=total: 8388+11588=19976 (overhead of 4467, 22.4% of total)  
M1521:49.12 modem: ota tx+rx=total: 7895+11151=19046 (to/from tower, not to/from modem)  
M1521:49.13 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
**T1521:53.47 lwip: IP deactivated to conserve energy**  
**M1521:54.16 sync: wakeup: modem shutdown**  
M1521:54.27 modem: wireless: idle {disconnected} {transport}  
S1521:54.31 sync: wireless: modem disconnected {cell-disconnected}  
S1521:54.42 journey: unless we start moving, the journey will end in 245 secs  
S1521:54.93 sync: network: LWIP terminated (sent:0 rcvd:0) {socket-ip-term}  
S1521:54.95 transport: using celluar transport because GPS is needed  
S1521:54.96 sync: connect requested by GPS (GPS)  
S1521:54.97 connect: 4.70V 30.63C before comms power-on (2025-08-14T14:53:15Z UTC)  
S1521:54.97 transport: using celluar transport because GPS is needed  
S1521:54.98 apn: for [a.notefile.net](http://a.notefile.net) using apn a-notehub.com.attz  
S1521:54.98 sync: wireless: domain [a.notefile.net](http://a.notefile.net) using APN a-notehub.com.attz  
S1521:54.99 sync: wireless: starting communications {wait-module} {connecting} {transport}  
S1521:55.00 modem: beginning power-on sequence  
S1521:59.71 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* ON \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
S1521:59.72 sync: wireless: modem now ON {modem-on}  
S1522:09.38 journey: unless we start moving, the journey will end in 230 secs  
M1522:13.30 modem: suppressing registration  
M1522:17.23 gpsmax: modem powered up in gps mode  
M1522:17.29 \_log.qo: gpsmax: NMEA data being received  
M1522:17.29 GPS search (0 sec, 0/0 dB SNR, 0/0 sats, HDOP 0.00)  
M1522:17.31 modem: wireless: connected {connected-closed} {transport}  
M1522:17.31 \_log.qo: gpsmax: requesting GPS refresh: modem’s GPS is ready  
S1522:17.36 sync: next wake-up due in 15m 0s to check on journey’s progress  
M1522:22.99 GPS search (5 sec, 39/39 dB SNR, 0/1 sats, HDOP 0.00)  
G1522:26.70 journey: unless we start moving, the journey will end in 213 secs  
M1522:27.99 GPS search (10 sec, 40/40 dB SNR, 0/2 sats, HDOP 0.00)  
M1522:32.99 GPS search (15 sec, 39/40 dB SNR, 0/2 sats, HDOP 0.00)  
M1522:37.99 GPS search (20 sec, 40/40 dB SNR, 0/3 sats, HDOP 0.00)  
M1522:42.99 GPS search (25 sec, 40/40 dB SNR, 0/3 sats, HDOP 0.00)  
G1522:45.48 journey: unless we start moving, the journey will end in 194 secs  
M1522:47.99 GPS search (30 sec, 40/40 dB SNR, 0/3 sats, HDOP 0.00)  
M1522:52.99 GPS search (35 sec, 39/40 dB SNR, 0/5 sats, HDOP 0.00)  
M1522:58.01 GPS search (40 sec, 40/40 dB SNR, 0/5 sats, HDOP 0.00)  
M1523:03.87 GPS search (46 sec, 39/40 dB SNR, 0/6 sats, HDOP 0.00)  
G1523:04.25 journey: unless we start moving, the journey will end in 175 secs  
M1523:08.87 GPS search (51 sec, 39/40 dB SNR, 0/8 sats, HDOP 0.00)  
M1523:13.87 GPS search (56 sec, 39/40 dB SNR, 0/8 sats, HDOP 0.00)  
**M1523:16.88 \_log.qo: GPS updated to 9F7JXQ97+XVWG ($GPGGA, 2 sats, 39db)**  
**M1523:16.89 gps: adding track note**  
S1523:16.97 sync: next wake-up due in 15m 0s to check on journey’s progress  
M1523:17.00 track: 2025-08-14T14:54:37Z added note 1755182691:2 (4.61)  
M1523:17.01 sync: wakeup: gps update (no refresh needed)  
S1523:17.53 sync: network: LWIP terminated (sent:0 rcvd:0) {socket-ip-term}  
S1523:17.53 sync: wireless: modem disconnect requested {cell-disconnect-begin}  
S1523:17.54 sync: wireless: idle {disconnecting} {transport}  
S1523:17.54 sync: wireless: idle {disconnected} {transport}  
S1523:17.55 sync: wireless: idle {disconnecting} {transport}  
S1523:17.59 modem: waiting for shutdown  
M1523:17.69 gps: modem powering down  
M1523:17.74 modem: waiting 5 secs for modem soft-powerdown quiescence  
G1523:21.67 journey: unless we start moving, the journey will end in 158 secs  
M1523:22.75 modem: wireless: modem now OFF {modem-off}  
M1523:22.75 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
M1523:22.75 modem: active for 87 sec  
M1523:22.76 modem: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
M1523:27.80 sync: wakeup: modem shutdown  
M1523:27.90 modem: wireless: idle {disconnected} {transport}  
S1523:27.99 sync: wireless: modem disconnected {cell-disconnected}  
S1523:28.00 sync: next wake-up due in 15m 0s to check on journey’s progress  
G1524:24.32 journey: unless we start moving, the journey will end in 95 secs  
G1525:20.61 journey: unless we start moving, the journey will end in 39 secs  
G1526:16.88 journey: completed 1755183457 journey  
G1526:16.89 sync: wakeup: journey completed

---

<div class="post-metadata">

**Author:** ![tjvantoll](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tjvantoll/32/231_2.png) [@tjvantoll](https://discuss.blues.com/u/tjvantoll)\
**Post date:** [August 14, 2025, 7:43pm UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/12 "2025-08-14T19:43:06Z")

</div>

Hey @TobiasR,

Thanks for testing this so thoroughly. I tend to agree that if your device is reliably getting a position after a manual sync, then something else must be going on.

First, can you share the configuration you’re currently using for both `card.location.mode` and `card.location.track`? That’d be good to know as I look through these logs.

Second, if I have a few ideas you can try out.

1. Try disabling Wi-Fi with `{"req":"card.transport","method":"cell"}`. I doubt this is causing your problems, but we’ve had some issues in the past with people using Wi-Fi as a transport with GPS/GNSS enabled—and it’d be good to rule that out.

2. For testing purposes, update your Notecard to use the following config.

```json
{
  "req": "card.location.track",
  "start": true,
  "heartbeat": true,
  "sync": true,
  "hours": 1
}

```

By default, Notecard only take new tracking readings if the device has moved (as detected by its onboard accelerometer). By setting `heartbeat` and a low `hours` value you’ll get readings every hour even if the device is stationary. And by setting `sync: true` those readings will be immediately synchronized to Notehub.

Hopefully we can learn more about what’s going on with some of these config changes.

TJ

---

<div class="post-metadata">

**Author:** ![TobiasR](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tobiasr/32/1665_2.png) [@TobiasR](https://discuss.blues.com/u/TobiasR)\
**Post date:** [August 15, 2025, 10:51am UTC](https://discuss.blues.com/t/notecard-syncing-but-with-old-data/3248/13 "2025-08-15T10:51:28Z")

</div>

Thank you for your suggestions. Will have to come back in a few days when I have had time to look into it further.
