Skip to main content

Checking the device history

This page describes how to view the history of the last packets exchanged between the device and the network; as well as the location history of your device if it is geolocated by ThingPark.

Viewing the packet history

You can see the history of the last 10 uplink/downlink packets exchanged between the device and the network from the detailed page of each device. Additionally, you can see the decoded payloads of your application data in this same view.

The list is ordered by descending timestamp, latest packets are displayed on top.

note

The list may be empty if the device has not exchanged any packets with ThingPark over the past days.

  1. From the left pane, select Devices, then search for the device you want to view or edit.

  2. Go to LAST 10 PACKETS.

    -> The last 10 uplink/downlink frame sequence is displayed as per the following example:

  3. In the UL/DL and Content columns, you can see a graphical representation of the packet type and content. Hover your mouse on each badge to get more details on the displayed value. To learn more, see Uplink LoRaWAN® packets and Downlink LoRaWAN® unicast packets.

    tip

    To learn more about RSSI, SNR, and ESP, see LoRaWAN radio metrics. The related color codes are described here.

  4. You may select which columns are displayed or hidden, by clicking the button at the top-right of the widget. You can also refresh the list by clicking and export it by clicking .

  5. If the packet contains DATA, click to view the data payload.
    The driver metadata shows the protocol identifier associated with the device when the payload was received and the driver identifier of the selected driver (system or custom). To learn more about driver metadata, see Device attributes.

    You may encounter one of the following situations:

    • There is no protocol identifier for this packet: no driver can be selected for payload decoding. The display looks like this:

      For more information, see Troubleshooting payload decoding issue.

    • There is a protocol identifier for this packet: a payload driver exists for the corresponding device and the payload has been decoded. The default display looks like this:

      The PREVIEW mode shows the JSON document in tree view (collapsed by default).

      Clicking RAW opens the raw view of the decoded payload. This looks like this:

      Switching between the RAW and PREVIEW modes is stored in the local storage of the browser and is automatically selected for all packets.

      note

      When exporting the packet list in csv format, the driver metadata is included but the payload is not decoded in the export file.

  6. To view more packets than the last 10 packets displayed in this widget, click SHOW ALL at the bottom of the widget.

    -> This takes you to the Wireless Logger application to view the entire traffic history and get additional details.

Checking the location history

note

This task applies only to the case when the location mode of your device is set to Network Geolocation.

If your device is successfully geolocated by the network, the location history is traced on the map of the Location widget.

  • The last known location is pointed with a marker. Clicking the marker reveals the location details.

  • The last location precision is displayed with a circle around the marker.

  • The traced location history can be modified using the clock icon on the right side of the widget.

    By default, "no history" is selected. Only the last 1000 locations reported on the requested period can be displayed on the map.

  • You can also view all location details for the seven days preceding the last reported location. To do this, click the icon on the right side of the Location widget.

    A new window opens, showing the location history as per the following example: