Assets are active components that hold value about a measure, either in physical or virtual space.
Most important physical assets are sensors and actuators.
Since id and name are unique identifiers, you can not change them.
You can have an asset with the same name on different devices. For example if you have 5 weather station devices, each with a temperature sensor, they can all have their own temperature asset.
There are 4 supported asset types, each with several fields you can set on the asset detail page
When manually creating an asset, the default profile is of type
string, using a default labelcontrol. Always make sure the used control matches the profile.
For more information on controls and profiles, please check the corresponding pages.
To manually create an asset
When creating an asset for a LoRa device, there are some restrictions in asset naming. Please check the info below to make sure you use a correct name.
For LoRaWAN, the name of your asset has to match the integer number of the data container it will be used for.
An overview of these numbers and their corresponding data containers can be found here.
The data rate and maximum packet size for the application payload roughly depend on the distance to the nearest gateway and the type of data to be sent, and are also defined in the specification for each region.
For the European 863-870MHz band, the application packet size varies between 51 bytes for the slowest data rate, and 222 bytes for faster rates.
Beware that the LoRaWAN protocol adds at least 13 bytes to the application payload.
To facilitate your LoRa project, we have created a LoRAWAN library which takes of the data rate and constructing the application payload and converting back the payload message into understandable information for AllThingsTalk Maker. The LoRaWAN library supports a container structure for various type of sensors to make it easy for you to write your first programs.
A simple instruction such as
Device.Send(val, LOUDNESS_SENSOR); will send data towards AllThinsgTalk Maker representing data for a loudness sensor.
More information about the container structure can be found here.
To visualize the sensor data in an asset, specify the container number in the Name field when creating the asset.