...
The table is configured via the "Data Table Config" in the "Device Type".
Uplinks & "Parser returned nil"
Uplinks are raw Uplink sent messages from the a device that will were received and tried to be processed by the parser to create Device Data records.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".
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.
The copied data can then be pasted in under the "Settings" Tab and send to the platform again for processing with a click on "Send Data". This data then appears again under "Uplinks" with "http" as datasource. Downstream processing, including any integrations, is then just as if the data had been sent from a physical device.
Downlinks
A list of queued and sent downlinks.
...
- Name - User friendly display name
- Address - used to identify the device when receiving Incoming data
- Serial - Serial number, provided in device import
- Device Tags - see below
- Description - User friendly description of the device
- Device Type
- App -
Deprecated - Datasource - allows to assign additional Pull or MQTT based datasources
- Parser - Parser to handle uplinks and generate device data
Organisation
Each device belongs to a zero or one Organisation. There are multiple ways to move the device to another organisation.
| Info |
|---|
Role: admin, org-admin org-admin can move the device between different Sub Organisations in his Organisation tree. |
Single Device
Go to: Configuration → Hardware → Find and open the Device Page
Change the Organisation
Press Save
Bulk Operation
Go to: Configuration → Hardware
Select multiple devices
Click "Bulk Operations"
Change the Organisation and press "Bulk Update"
Device Tags
Tags 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.