On the ARTIK cloud services ecosystem, IoT device and application developers can discover each other and quickly build sophisticated solutions together.
This article is written for device developers. It outlines the key elements of a working ARTIK cloud services device.
Also see Applications.
Create a device type
Each device on ARTIK cloud services corresponds to a device type. A device type has a unique Manifest that describes the data sent by the device and any commands it can receive. The Manifest is how ARTIK cloud services accept data from any source and enables true interoperability.
To create a device type:
- Use our web tools to create a device type.
- Create a Manifest using the same interface.
- Publish the device type to allow other developers to discover and work with it.
Some devices are already designed to send data to an external cloud. You can connect external clouds to ARTIK cloud services by creating a Cloud Connector device type, which allows ARTIK cloud services to treat an external cloud as a device. Here is how to get started with this key feature on ARTIK cloud services.
Connect a device
Any source of data in ARTIK cloud services is called a device. Devices range in size from wearables to smart-city applications and can include sensors, appliances, services, and more.
An ARTIK cloud services device serves as an instance of its device type. The device sends and receives messages using the format specified in its device type Manifest.
To connect a device, you can:
- Use our web tools to create a device and then obtain the device token.
- Use REST APIs to create a device and then obtain the device token.
Learn about typical flows for onboarding physical devices.
A device can send a data message to ARTIK cloud services using one of the below protocols:
- REST: POST
- WebSocket: Send via device channel WebSocket
- MQTT: Establish a session, then publish
- CoAP: POST
Actions are messages that send a command to a device, such as
setOff. A device must establish a persistent connection with ARTIK cloud services in order to receive Actions in near real-time.
- WebSocket: Receive via device channel WebSocket
- MQTT: Establish a session, subscribe and then receive
- CoAP: Establish an observe connection then receive
If a persistent connection is not possible, a device can make a REST call to pull the last Action sent to it.
Rules enable smart interactions between all devices in the ecosystem. A data message from one device can trigger an Action on another device. Because data on ARTIK cloud services is brokered via device type Manifests, Rules bypass data silos and make devices fully interoperable.
We highly recommend keeping your devices secure. Learn how to create a secure device type, connect a secure device, and send and receive messages/Actions at a higher level of security.
Manage your devices
You can organize and manage a fleet of devices with the Device Mirror and device management features. These features allow you to perform tasks such as OTA (over-the-air) updates for device types without requiring end user interaction.
Once you understand the above concepts, you can quickly take your device from prototyping to production.
You might eventually develop applications for your devices. Get started with the basics!