Features & Limitations


The device inspector overview provides a list of all customer devices. The list can be filtered by ICCID to search for a specific device. To see more information of a certain device, a single device can be select it in the list.

Device Inspector overview

Device Inspector overview

The details will provide more specific information.


Device state for UDP, CoAP or LwM2M messages.

  • UDP or CoAP . Last message received from the device is stored in the state. By default, the portal tries to convert Base64 messages to JSON format. If the received content is not valid JSON, the portal will display the original message as Base64.
    If the user has enabled the energy saver feature with a valid template for transforming payload into JSON, the portal will display message as a JSON and, if the message is not tranformable with the existing energy saver template, there will be an admin log created with the error message.
    For CoAP messages, the topic is also stored in the device state.

  • LwM2M. Digital representation from the device is stored in state according to OMA specifications.

Device Inspector Details

Device State for CoAP


Whenever messages (UDP, CoAP or LwM2M) from a device are sent to the 1NCE OS endpoint(s) those are stored for 7 days.
More details in Historian Web Interface or Historian API Examples.


If the device is utilizing Device Locator, then a location will be pinpointed on a map.

Device Inspector Details. Map

Device location on map


  • We only show history of the device from the last 7 days, but device state is stored permanently.
  • History of device is not supporting messages bigger than 2048 bytes.
  • Maximum state size for each protocol (UDP, CoAP and LwM2M) is 8192 bytes.
  • A summary of the location of the device is shown, containing the first position, the last position and some positions inbetween (more data available via the API).
  • The current digital state representation of a SIM device can be updated up to 20 times per second. Therefore, if a given device sends messages at a higher frequency, it would cause a throttling issue resulting in the state not being updated. That is noticeable by the existence of DeviceShadowUpdater[ThrottlingIssue] logs in the 1NCE OS Portal Administrator Logs page.
  • A different issue can happen if a device sends multiple messages in a short interval. That would result in a digital state version conflict and only one of the states will be actually persisted. The existence of DeviceShadowUpdater[VersionConflict] represents that situation.