# Device being seen by gateway but not updating status/data **URL:** \ **Category:** How to get started\ **Created:** [February 11, 2020, 9:53pm UTC](https://www.thethingsnetwork.org/forum/t/device-being-seen-by-gateway-but-not-updating-status-data/34303 "2020-02-11T21:53:42Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\ **Post date:** [February 11, 2020, 11:57pm UTC](https://www.thethingsnetwork.org/forum/t/device-being-seen-by-gateway-but-not-updating-status-data/34303/7 "2020-02-11T23:57:16Z")
To see/confirm that the device has exceeded the limits of a 16 bits uplink frame count (65,536), one can paste a Base-64 encoded payload from the gateway’s Traffic page into [an online decoder](https://runkit.io/avbentem/lorawan-packet-decoder/branches/master), and then also specify the AppSKey and NwkSKey. Using those secrets, the decoder will show the MSB of the frame count (which is not in the packet itself, but needs to be determined by the server, for which a real LoRaWAN server then assumes the counters are not too far out of sync). See [After resetting frame counters, payload is shown on gateway traffic but not in application](https://www.thethingsnetwork.org/forum/t/after-resetting-frame-counters-payload-is-shown-on-gateway-traffic-but-not-in-application/19331/12) to re-sync the uplink frame count in TTN and the device. That won’t work for the downlink counter though, so simply restarting the devices is surely easier, but maybe you want to know what’s happened. --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/device-being-seen-by-gateway-but-not-updating-status-data/34303)._