Cloud Template Device

Cloud Template Device

A Cloud Template Device (CTD) lets you connect and test a device in /IOTCONNECT™ without creating a template first. Just send data — the platform automatically learns the data structure, lets you fine-tune it, and when you’re ready, converts it into a full device template. It’s the fastest way to prototype, validate, and migrate IoT devices.

What is a Cloud Template Device?

On most IoT platforms, every device must be tied to a template before it can send data. A template describes the device’s attributes (the sensor fields), their data types, and its behavior. Creating that template up front is extra work — especially early in development when you’re still experimenting.

A Cloud Template Device (CTD) removes that step. You connect the device with no predefined template, point it at /IOTCONNECT™, and start sending data. The platform then learns and adapts to whatever data structure arrives, so you can validate your device immediately.

Think of it as a “draft” device: perfect for trying things out quickly, and easy to promote into a proper, fully-featured device once you’re happy with the data.

How It Works

Cloud Template Device Flow

A Cloud Template Device moves through a simple lifecycle — from connecting with no setup, to becoming a full device:

1. Connect the device: Register it as a Cloud Template Device — no template required.

2. Send data: The device publishes its sensor data straight to /IOTCONNECT™.

3. The platform learns: /IOTCONNECT™ automatically detects the attributes in the incoming data — you don’t define them by hand.

4. Review and tune: Check the attributes the platform discovered, rename them to friendly names, and set their data types.

5. Convert to a template: When the data looks right, convert the CTD into a real device template with one action.

6. Use it as a normal device: The device now has the full platform feature set — rules, dashboards, commands, storage, and more.

Why Use It?

Cloud Template Device is built for speed and flexibility during development:

Accelerate prototyping: Connect devices instantly without waiting for template setup.

Simplify testing: Quickly validate new sensors, payloads, or firmware updates.

Stay flexible: The platform learns from incoming data and adapts its structure — no rigid template to fight against.

Reduce overhead: Skip the repetitive task of creating multiple templates for rapid iterations.

What You Can Do with a CTD

A Cloud Template Device serves several purposes across the IoT development lifecycle:

Data validation: Confirm your device is sending sensor data to /IOTCONNECT™ exactly as you expect.

Template generation: Automatically create a device template based on the real data patterns received from the device.

Development flexibility: Adjust data types, attributes, and device behavior without being locked into a template.

Streamlined deployment: Convert CTDs into normal devices once the data patterns are validated and the template is optimized.

Easy Device Migration

Moving devices from another platform to /IOTCONNECT™ is usually painful — but CTD makes it simple. With only minimal changes, you point your device at the /IOTCONNECT™ broker, and a Cloud Template Device captures its data and builds a template on the fly.

There’s no need to recreate every template by hand before you can connect. You get up and running immediately, then take full advantage of all the platform’s features — without disruption to your devices.

ⓘ NOTE

A Cloud Template Device is meant for prototyping, testing, and migration — it learns your data automatically so you can start fast. Once the attributes and data types look right, convert it into a standard device template to unlock the full feature set (rules, dashboards, commands, and storage).