When opening the device page there are multiple sub pages:
-
-
- Overview -
- Device Data -
- Uplinks -
- Downlinks -
- Config -
- Settings -
- Security +
- Overview +
- Device Data +
- Uplinks +
- Downlinks +
- Config +
- Settings +
- Security
Overview​
Device Properties​
@@ -35,8 +35,12 @@LocationDevice Data​
Device data lists all data records returned from the Parser.
The table is configured via the "Data Table Config" in the "Device Type".
-Uplinks & "Parser returned nil"​
-Uplinks are raw sent messages from a device that were received and tried to be processed by the parser to create parsed records ("Device Data"). Not all uplinks return a good data result, then the parser result is "Parser returned nil". This is not a general error, but a hint that no device data could be extracted from the uplink. Often this happens with status uplinks that do not contain user data but can be processed by the parser for meta information, e.g. battery voltage, that are shown under "Device Properties".
+Uplinks​
+Uplinks are raw sent messages from a device that were received and tried to be processed by the parser to create parsed records ("Device Data").
+Parser returned nil
Not all uplinks return a good data result, then the parser result is "Parser returned nil". +This is not a general error, but a hint that no device data could be extracted from the uplink. +Often this happens with status uplinks that do not contain user data but can be processed by the parser for meta information, +e.g. battery voltage, that are shown under "Device Properties".
Simulate Uplinks​
For test purposes, it may be useful to simulate uplinks through the platform and let the parser process them again. For this purpose, the "data" part of a past upload can be used, as shown in the highlighted part below.
Simulate Up
Downlinks​
A list of queued and sent downlinks.
-Config (optional)​
+Config​
Requires Trait:
The config tab is only displayed when the Device Type has the Trait "Remote Config Update"
@@ -86,6 +90,13 @@Device TagsTags on device level are meant to group devices inside an organisation. Use cases can can be external ID's, Installation location, data export targets, etc.
Some future plans are to filter by tag in integrations, display tags in the device table and use them for search, grouping, etc.
Currently the most important difference to device properties (where you can also story lists) is, that the parser has no write access to tags.
-Also a device with too many tags might get less handy, where device properties can be added as needed.
+Also a device with too many tags might get less handy, where device properties can be added as needed.
+Security​
+On the Security tab, all security related information about the device and it's connection can be found.
+You can find information like:
+
+- If DTLS is enabled for the device
+- Certificate fingerprint of the device
+
-Also a device with too many tags might get less handy, where device properties can be added as needed.