Getting started with IoT Portal
You need to create your IoT Portal user account. Any users that are to have access to the IoT Portal a user account will need to be created. The IoT Portal account is generally created using the Management Portal. The Management Portal is a web-based application that contains the UI elements that enables interacting with the the IoT Portal.
If you are trying to create an account in the production environment (portal.telit.com, portal-de.telit.com or portal-jp.telit.com), then you need to request an admin user within your organization. An admin user of an organization, can invite users as needed. When inviting a user that does not have an account, an account will be created when signing in for the first time. If the user already has an account, the user will simply be added to the Organization. Be sure to create the proper Roles, for users. For more information on Roles, see Roles.This will ensure that the user will only be able to access what they need to have access to. For more information on inviting and adding a user, see Inviting a user.
If you are trying to create an account in the development environment (portal-dev.telit.com) then it is possible to create your own account while creating an account in the Dev portal. Follow the steps described in IoT Portal Part 1 - Creating your account to create your IoT Portal account (applies only if you using https://portal-dev.telit.com). If you already have your account go to step 2.
A Thing definitions allows you to define the characteristics of your Things. A Thing definition models the attributes,
alarms, properties, methods, tunnels, presentation
information, and other characteristics of a particular type
of item that is a portion of your IoT solution.
A Thing definitions allows you to define the characteristics of your Things. A Thing definition models the attributes, alarms, properties, methods, tunnels, presentation information, and other characteristics of a particular type of item that is a portion of your IoT solution.
The Thing definition is created and is attached to the Application Token. Step 3 explains about the Application Token. A Thing trying to auto register to the IoT Portal needs to authenticate with the Application Token. The Application Token then attaches the Thing to the respective Thing definition to which it is configured to. On the other hand when you are creating a Thing within the IoT Portal you need to attach a Thing definition.
When a Thing created in the IoT Portal is trying to connect it needs to authenticate with the Application Token. The Thing definition configured in Application Token must match with the Thing definition selected while creating the Thing. This ensures that the Thing gets connected to the IoT Portal
A Thing Definition will need to be utilized for any connected Thing on the IoT Portal including LWM2M. For more information on Thing definition, see IoT Portal Part 2 - Creating a Thing definition
To get connected to the IoT Portal you need a valid Applications. Application Token authenticates the Thing connecting to the portal and is not used for LWM2M.
Examples of applications includes Installing an Asset
Gateway and Installing an Enterprise
Gateway software products, external
applications using the IoT Portal API
For more information on Application Token, see IoT PortalPart 3 - Creating an Application token
A Things connects to the IoT Portal using the Application Token. The two most common way to communicate with the IoT Portal is TR50 and LWM2M.
A Thing is a digital representation of a physical device, an application, a logical entity, or a vehicle. Things are instances of a thing definition and inherit their characteristics. Things are the primary items that associate data with the items that make up your IoT solution (gateways, sensors, devices, assets, programs, cellular modules, and so on). A Thing can be something like a car, or it could be a component of a car like an engine, where a car is actually represented by multiple things.
The Thing Dashboard shows all the details of a Thing including its properties, alarms, attributes, tunnels and so on.
For more information on Creating and Connection your Things, see IoT Portal Part 4 - Connecting or Creating a Thing
After the Thing is connected to the IoT Portal, you will be able to view the real-time data from your Thing in the IoT Portal. Depending on the type of Thing you will see different tabs in the Management Portal that contains information about the Thing.
The different tabs in the top widget include:
- Overview - The overview tab shows the Thing definition, Key, Last seen time, Tags, Security Tags, Location, Identity, Storage, API counts month to date.
Gateway - The Gateway tab is available when viewing a Gateway Thing and provides Product, Platform, Version, App Version, and Remote Shell availability status. It is possible to Generate diagnostic file and Launch workbench for the gateway you are viewing.
- Details - The details tab provides the Created by, Created on, Last updated by and Last updated on details.
- Attributes - The Attributes tab provides attributes of the Thing with the values.
- Sharing - The Sharing tab provides the Orgs to which the Thing is shared to and the history of the sharing and unsharing of the Thing.
- Events - The Events tab is available when you have permission to view the logs and will show you five of the most recent events.
- Files - The Files contains the files associated with the Thing.
- Connection - The Connection tab is available when a Thing has a cellular data plan.
- Methods - The Methods tab is available if the Thing has methods defined. Clicking on the methods named button will open a form to accept values you want to execute the method with.
- API Usage - The API Usage tab shows a graph with the API usage for the last 30 days
- Tunnels - The Tunnels tab is available if the Thing has tunnels defined in the Thing definition.
For more information on Viewing a Thing, see IoT Portal Part 5 - Viewing a Thing
There are different ways to interact with the data coming from your Thing. Trigger or Campaigns are not confined to a Thing. For example, a Campaign is run on all the Things to assign a tag.
- There exists various Trigger events in the IoT Portal that will listen to a magnitude number of events happening in the connected Things. For example: A geofence event is setup to trigger an event when a Thing enters or leaves a particular area
- Triggers are a convenient way of monitoring the device for any abnormal events. The Triggers constantly listens to the incoming data and performs necessary actions to counter act the events. There are third party Trigger action available that allows you to communicate the data to a third party service.
- Campaigns allows you to perform certain action on Things without an event to Trigger the action. For example, it is possible to update the firmware of all the connected Things using a Campaign.
- Build custom dashboards and view the widgets you want to see.
For more information on interacting with a Thing, see IoT Portal Part 6 - Interacting with the Thing