Collect — Data Collection Overview

ControlCom Connect collects data via three paths: the Edge Server (a containerized application you deploy locally), direct MQTT (custom code that talks to the platform's broker), and direct HTTP (a REST endpoint for scheduled or batch uploads). All three speak the same back-end protocols — the choice is who writes the code.

Overview

The Collect stage sits between Connect (provisioning Devices in the platform) and Store (the Timescale-backed time-series store). The Edge Server is the no-code path: deploy a Docker container on your network, point your Devices at it, and the container handles MQTT, auth, buffering, and reconnection on your behalf. MQTT and HTTP are the developer paths — you implement the protocol yourself.

Collection Methods

ControlCom Connect offers flexible data collection options to fit your technical requirements and development preferences:

ControlCom Edge Server (Recommended for Most Users)

The Edge Server is a containerized application that runs locally on your network and handles all the complexity of device communication for you. It uses MQTT and HTTP protocols under the hood to communicate with ControlCom Connect, but you don't need to write any custom code.

What It Does:

• Automatically connects your devices to ControlCom Connect
• Handles all protocol communication (MQTT/HTTP) transparently
• Provides a web interface for device configuration
• Manages authentication, encryption, and reconnection logic
• Buffers data locally during internet outages
• Aggregates and processes data before sending to the cloud

Perfect For:

• Users who want a turnkey solution without custom development
• Organizations with multiple devices on a local network
• Deployments requiring local data processing and offline capabilities
• Teams without embedded development resources
• Systems that need centralized device management
• Reducing cloud bandwidth through local data aggregation

Technical Level Required: Basic (Docker deployment only)

Learn more about Edge Server →

MQTT Protocol (Direct Integration)

For developers who want full control, you can write custom applications that connect directly to ControlCom Connect using the MQTT protocol. This is the same protocol the Edge Server uses, but you implement it yourself.

What You Build:

• Custom device firmware or applications
• Direct MQTT broker connection to ControlCom Connect
• Your own authentication and connection management
• Custom data formatting and transmission logic
• Application-specific error handling and retry logic

Perfect For:

• Custom device firmware development
• Developers who need full protocol control
• Real-time bidirectional communication requirements
• Embedded systems with custom communication patterns
• Integration with existing MQTT-based infrastructure
• Resource-constrained devices where Edge Server overhead isn't desired

Technical Level Required: Advanced (MQTT protocol knowledge, custom development)

Learn more about MQTT →

HTTP API (Direct Integration)

Write custom applications that send data to ControlCom Connect using standard HTTP POST requests. Simple REST API integration for developers who prefer HTTP over MQTT.

What You Build:

• Custom applications or scripts
• HTTP client code for your devices
• Authentication header management
• Request formatting and error handling
• Retry logic for failed requests

Perfect For:

• Custom web application integration
• Scheduled data uploads and batch processing
• Developers who prefer REST APIs over MQTT
• Devices connecting intermittently rather than maintaining persistent connections
• Systems behind firewalls that block MQTT ports
• Simple integrations where real-time updates aren't critical

Technical Level Required: Intermediate (HTTP/REST API knowledge, basic development)

Learn more about HTTP API →

Edge Server vs. Direct Integration

The key difference is who writes the code:

Edge Server:

• ControlCom provides the complete application
• You just deploy it and configure devices through the web UI
• No custom development required
• Best for most users and organizations

Direct MQTT/HTTP:

• You write custom applications/firmware
• Full control over implementation details
• Requires development expertise
• Best for specialized requirements or existing custom systems

Choosing a Method

Quick Decision Guide

Start with Edge Server if:

• You want the easiest deployment with no custom coding
• You have devices on a local network
• You don't have embedded development expertise
• You need local data processing or offline capabilities
• You want ControlCom to handle all the protocol details

Use Direct MQTT if:

• You're writing custom device firmware
• You need complete control over the MQTT implementation
• You have existing MQTT infrastructure to integrate with
• Your devices are too resource-constrained for Edge Server
• You're an experienced IoT developer building custom solutions

Direct HTTP if you're integrating from a web/server application, you prefer REST, your Devices send data on a schedule rather than continuously, or MQTT ports are blocked by firewall policy.

Hybrid is common: Edge Server for the bulk of on-site Devices, plus HTTP for third-party integrations and scripted ingest.

Getting Started

To begin collecting data with ControlCom Connect:

Step 1: Choose Your Collection Method

Based on the guidance above, select the method (or methods) that fit your requirements.

Step 2: Set Up Your Collection Infrastructure

Follow the detailed setup guide for your chosen method:

• Edge Server: Getting Started with Edge Server
• MQTT: MQTT Protocol Guide
• HTTP API: HTTP API Guide

Step 3: Configure Your Devices

Configure your devices or integration to send data using your selected method. Each guide provides:

• Authentication and credential setup
• Payload format specifications
• Code examples in multiple languages
• Best practices and troubleshooting

Step 4: Verify Data Collection

Once configured, verify data is being collected:

• Check device status in the ControlCom Connect dashboard
• View incoming variable data
• Monitor connection health and data freshness

Prerequisites

Before collecting data, ensure you have:

• Connected your organization and devices to ControlCom Connect
• Created device records in the platform
• Obtained necessary authentication credentials
• Network connectivity from your devices to ControlCom Connect (or to your Edge Server)

Next Steps in the Workflow

After collecting data, you can move to subsequent stages:

• Store: Your data is automatically stored in the Timescale database
• Analyze: Use Platform Explorer to query and analyze collected data
• Visualize: Create dashboards and diagrams to visualize your data
• Report: Generate compliance reports from collected data
• Integrate: Connect to external systems via API and webhooks

Start collecting data today by exploring the detailed guides for your chosen collection method.