IoT Hub Connection

Goal: Connect production devices using OpenIndustrial's managed IoT Hub.


How It Works

OpenIndustrial provides managed IoT infrastructure:

What You GetWhat You Don't Need
Device connection stringsAzure subscription
SAS tokens for authenticationIoT Hub provisioning
MQTT connection detailsInfrastructure management
Automatic device registrationManual Azure configuration

This is infrastructure-as-a-service for IoT. You focus on your devices and data - we handle the cloud infrastructure.


Creating a Connection

Option A: Using the Canvas

  1. Drag Connection node onto workspace canvas
  2. Name it (e.g., "factory-sensors")
  3. Open the Inspector panel
Connection Inspector showing Settings tab with Connection ID field.

Option B: Ask Azi


Connection Info Tab

After creating a connection, select it and open the Inspector → Connection Info tab to access all device information.

Connection Info tab showing IoT Hub details and device status.

Overview

Real-time health monitoring for your connection:

FieldDescription
HealthCurrent connection health (Healthy, Degraded, Unhealthy)
Last ReceivedTimestamp of the most recent telemetry message

Identity

Device identification and IoT Hub details:

FieldDescription
CloudCloud provider (Azure)
IoTHubManaged IoT Hub name
HostNameFull IoT Hub hostname for connections
DeviceIDUnique device identifier
StatusConnection state (Connected, Disconnected)
AuthTypeAuthentication method (symmetricKey)

Device Access

Expand the Device Access section to reveal connection credentials:

Device Access section showing connection strings, SAS tokens, and MQTT details.
CredentialDescription
Device ConnStr (primary)Primary connection string for SDK-based connections
Device ConnStr (secondary)Secondary connection string for key rotation
Device SAS (primary, 1h)Primary SAS token with 1-hour expiration
Device SAS (secondary, 1h)Secondary SAS token with 1-hour expiration
MQTT HostIoT Hub hostname for MQTT connections
MQTT PortMQTT port (8883 with TLS)

Configuring Physical Devices

Use the credentials from the Inspector to configure your devices.

Connection String Method

Most Azure IoT SDKs accept a connection string:

HostName=<iot-hub>.azure-devices.net;DeviceId=<device-id>;SharedAccessKey=<key>

Copy the full connection string from Device Access → Device ConnStr.

MQTT Direct

For devices using MQTT directly:

SettingValue
HostFrom Device Access → MQTT Host
Port8883 (TLS required)
Client IDFrom Device Access → MQTT ClientId
Username{iothub-host}/{device-id}/?api-version=2021-04-12
PasswordSAS token from Device Access
Thinking Tip:

SAS tokens expire. For long-running devices, use the connection string with an SDK that handles token refresh automatically.


Supported Protocols

ProtocolPortUse Case
MQTT8883Most devices, lowest overhead
AMQP5671Enterprise messaging
HTTPS443Firewall-friendly, higher latency

Verifying Data Flow

Once your device is configured:

  1. Power on the device
  2. Select the connection node in the canvas
  3. Open Inspector → check for incoming impulses
  4. The status should show "Connected"
Thinking Tip:

No data after 30 seconds? Verify your device is using the correct connection string and can reach the IoT Hub endpoint.


Security Best Practices

Treat connection strings like passwords. Never commit them to source control or expose them in client-side code.

  • Store credentials securely on devices
  • Use the secondary connection string for key rotation
  • Monitor connection status in the Inspector
  • Regenerate credentials if compromised

Enterprise: Custom IoT Hub

Need dedicated infrastructure? OpenIndustrial supports custom-deployed IoT Hub for enterprise customers.

Contact Fathym for:

  • Dedicated IoT Hub instances
  • Custom scaling requirements
  • Compliance-specific deployments
  • VNet integration

Next Steps

If you want to...Go to...
Access more device detailsDevice Credentials →
Route data to queriesSurfaces Guide →
Test with simulated dataSimulator Guide →
On this page