A business or student can register for a Free Account and prototype deploy and manage up to 10 devices with an aggregate amount of free storage up to 1GB per month and up to 1GB of free traffic per month.
Free Accounts are valid for a period of 6 months. After this period they must be converted into Business Accounts
Businesses may use the free service for their own internal use, but not to offer commercial services to other individuals or businesses.
If you need more devices, storage or traffic you can register for a Business Account.
With CloudPlugs, you can have either a Free account or a Business account.
The Free Account allows 10 devices total (Prototypes, controllers and production things are considered devices) that can store up to 100MB per month and use up to 100MB of traffic each per month.
The Business Account allows you to use as many devices as and as much bandwidth and storage as needed. Device licenses are annual and pricing varies based on whether the device is a single device or a gateway, and whether its application is for residential, commercial or industrial use.
Each device includes 100MB of traffic and 100MB of storage per month. The monthly storage and bandwidth allowance is the product of the number of devices licensed and 100MB, respectively. Excess storage and bandwidth use above the allowance is billed in 100MB increments.
For more information, please contact us.
Managing a device requires:
- Connecting the device to the CloudPlugs IoT service using Edge One™, a SmartPlug™ agent, a PicoPlug™ or a connection library.
- Developing or configuring the device application, Edge One™ or SmartPlug™ will publish and subscribe to channels in CloudPlugs IoT.
- Developing a control application or dashboard to receive data and issue commands to the device
- A CloudPlugs account to access the CloudPlugs IoT service platform.
- A controller board, or Linux gateway for your Thing. A list of supported boards and gateways can be found here.
- A SmartPlug™, Edge One™, PicoPlug™ or a software library that you will download and integrate with your controller firmware. Supported libraries can be found here.
Our libraries include examples and have all the necessary functions to connect your Things to CloudPlugs.
- Register to create a CloudPlugs account.
- Login to your account.
- Click on the Get Started icon and follow the instructions to connect your device with a SmartPlug™ agent, with Edge One™ or with a connection library.
- Create a specific class or model of Things that will be taken into production.
- Assign the enrollment credentials to your devices.
- Set any specific triggers, additional properties, SmartPlug applications or Containers for a class production Things.
- When properties, triggers or applications are added, deleted or changed in a Production template, its corresponding Production Things are automatically updated.
Once you have a desired template, you simple click on Provision Things and the platform will be ready to accept connections from Things that enroll with the proper credentials.
Wildcards are powerful special characters which allow you to subscribe to multiple channels at once and perform operations across multiple channels with one command.
The channel level separator is used to introduce structure into the channel, and can therefore be specified within the channel for that purpose. The multi-level wildcard and single-level wildcard can be used for subscriptions, but they cannot be used within a channel by the publisher of a message.
Channel level separator
The forward slash (/) is used to separate each level within a channel tree and provide a hierarchical structure to the channel space. The use of the channel level separator is significant when the two wildcard characters are encountered in channels specified by subscribers. Multiple channel separators are not allowed; therefore, a channel description such as //sensor///temperature is not valid.
The number sign (#) is a wildcard character that matches any number of levels within a channel. For example, if you subscribe to sensor/temperature/fridge/#, you receive messages on these channels:
The multi-level wildcard can represent zero or more levels. Therefore, fridge/# can also match the singular fridge, where # represents zero levels. The channel level separator is meaningless in this context, because there are no levels to separate.
The multi-level wildcard can be specified only on its own or next to the channel level separator character. Therefore, # and temperature/# are both valid, but temperature# is not valid. The multi-level wildcard must be the last character used within the channel tree. For example, temperature/# is valid but temperature/#/reading is not valid.
The plus sign (+) is a wildcard character that matches only one channel level. For example, sensor/temperature/+ matches sensor/temperature/fridge and sensor/temperature/cooler, but not sensor/temperature/fridge/freezer. Also, because the single-level wildcard matches only a single level, sensor/+ does not match sensor.
The single-level wildcard can be used at any level in the channel tree, and in conjunction with the multilevel wildcard. It must be used next to the channel level separator, except when it is specified on its own. Therefore, + and sensor/+ are both valid, but sensor+ is not valid. The single-level wildcard can be used at the end of the channel tree or within the channel tree. For example, sensor/+ and sensor/+/fridge are both valid.
For more details about wildcards, please consult the Knowledge Base.
CloudPlugs IoT offers maximum flexibility. You do not need to delete and re-create channels when you want to modify the behavior of your existing channels. Simply modify the data structure and the channel will start transporting the new data published by your Things.
Access Control Lists (ACL) can be set for individual devices or for group of devices. ACLs include read-only, read-write and deny or no-access permissions to govern how devices and applications interact with each other.
For more details please consult the Knowledge Base Production Template and Things documentation.