I'm using Thingy:91X devices with the Asset Tracker Template, connecting via CoAP over NB-IoT.
Device IDs:
- 5042394b-3538-43d8-807a-0e13e5435476 (original device)
- 5042394b-3538-424f-808b-140706280282 (second device, freshly flashed and claimed today for comparison testing)
On the original device, after a period where the connection appeared stuck (LTE connected, but no telemetry published for 3+ days), I performed a warm reboot via the serial shell. On reboot, the device successfully:
- Connected to LTE (~8 seconds)
- Established DTLS/CoAP session to nRF Cloud, JWT auth succeeded (Authorization result_code: 2.01)
- Reached state_connected_ready
- Sampled and published fresh environmental data (temperature, pressure, humidity) and battery level
The device shadow correctly showed this fresh data with a current timestamp immediately after.
However:
- The dashboard's "Last connected" field briefly shows "just now" right after a connection event, but reverts to stale data after refreshing the page
- Querying /v1/messages?deviceId={id}&pageLimit=100 still returns old data — no new messages appear despite the device actively sampling and sending (confirmed via serial logs)
I set up a second, brand new Thingy:91X today specifically to rule out a device-specific issue. On this second device, location data updated correctly and matched my actual physical location. However, I'm seeing the same pattern: data appears fresh momentarily, then reverts to stale/no-data after a browser refresh.
Since this is now reproduced across two separate devices on the same account, it points to an account/tenant-level issue on nRF Cloud's platform side rather than anything device or firmware-specific.
Has anyone else seen this? Is this a known issue currently being investigated?