Connect a device and explore its first signals

Worked example

One device, two useful signals

Use Equipment simulator for OPC UA or Equipment JSON sample for MQTT. The recipes have optional manufacturing references, so they do not require installing a manufacturing package. They still require a real existing target Object ID.

Procedure

Follow the task in order

1. 1
   Prepare the source and RuntimeComplete Runtime setup and sign in with the required bridge and UNS permissions. Install and start the appropriate reviewed-device capable bridge through the normal service workflow. For history, QuestDB, UNS Archiver and UNS API Global must be available. Check Services health. Ensure the source is reachable from the controller that runs the bridge, not just from your browser.
2. 2
   Prepare a concrete machine identityIn Unified namespace choose or create the required namespace hierarchy and target Object ID. A Schema definition describes a reusable type; it does not create that live target. Give the second device a separate identity. The sample recipes publish temperature and status Data attributes.
3. 3
   Open Set up device and choose the recipeOpen Services, then OPC UA Bridge or MQTT Bridge, and choose Set up device. Select Equipment simulator or Equipment JSON sample in Recipe catalog, or use Load device recipe with the matching JSON download below. Read required versus optional references. Manufacturing equipment additionally requires the exact active manufacturing definitions pinned in its recipe; it does not install them.
4. 4
   Enter only the local parametersUse a unique new connection name. For OPC UA enter the source endpoint and adapt source NodeIds. For MQTT enter the local broker address, exact device source prefix and optional unique client ID. Select the UNS target Object ID. Choose local credential references when needed. Anonymous/None sample settings are for an isolated test source; production settings must match the source security policy.
5. 5
   Review the proposed mappingsUse Next to reach Review mappings. Confirm included attributes, NodeIds or topic filters, extraction rules and UNS destination. Click Review device and resolve any conflict or missing required reference. Cancel leaves the runtime unchanged. If another operator changes runtime configuration, refresh/review the current draft rather than replacing an existing connection.
6. 6
   Create, then start deliberatelyCreate device saves a stopped connection with its mappings. It does not start ingestion. Inspect the created entry, then Start the connection from the bridge page. Confirm the source is connected and publishing. Stop preserves configuration and published metadata; it is not deletion.
7. 7
   Verify temperature and status in the namespaceWith the saved connection selected on the bridge page, choose View values. One configured UNS target opens directly; multiple targets show their complete identity paths for selection. The existing Object ID snapshot shows latest values and age and lets you open Explore or compare selected signals. You can also find the target in Unified namespace. Check that temperature is numeric and status is a string, with current values and useful timestamps. A running bridge is not proof of data delivery. If the target is unavailable, check that it exists and is accessible to your account. If values are missing, inspect source connection health, NodeIds/filter and JSON extraction, then verify permissions and target selection. Stopped connections can still have last-known values; inspect their timestamps.
8. 8
   Explore live values and historical sourcesOpen Explore for temperature and add status. Numeric charts use sampled history with the selected aggregation; strings use raw transition lanes. Select the correct History sources when more than one retained publisher/table exists. A live value without history is a separate archival/API readiness issue, not evidence that the source connection failed.
9. 9
   Save a repeatable analysisChoose a fixed time window, meaningful series labels and the intended historical sources, then save the chart view. Reopen it and verify those selections. Add the saved view to a dashboard if needed. Dashboard table cells request raw rows; Explore tables follow the chart query mode.
10. 10
    Export and reuse for a second deviceExport data to Excel with Raw when you need source observations. Check the wide and long sheets and metadata for history source, query mode and truncation. Export this recipe or download the same version, then repeat setup with a new source prefix/NodeIds, unique connection name and a second Object ID. Do not copy local endpoints, actual passwords or the first device identity into a shared recipe.

Expected result

What you should have

Boundaries

Important boundaries

• The bridges have public 2.0.1 releases. The downloadable recipe collection remains a preview kit; adapt its source parameters and verify the workflow with your own device and compatible Runtime.
• An imported recipe identity is a publisher claim. SHA-256 checksums identify bytes; they are not signatures or trusted publisher approval.
• Recipe imports, package checks and bridge writes are separate operations. Recipes do not create a saved view/dashboard or activate schema packages. Optional view references are recommendations.
• Controller-specific credentials stay local, including when Infisical supplies the same values to several controllers. Provision secret references before migration or Start.
• Deleting a bridge connection removes its publisher configuration. Existing UNS objects and archived history have their own lifecycle and are not automatically deleted. Remove an unwanted UNS object separately, and use explicit history retention actions when required.
• Same-timestamp rows align by occurrence, not causal relationship. Raw exports retain observations, but backend limits still apply. Check truncation metadata; Excel Date cells have millisecond precision.
• MQTT JSON recipes do not import Ignition UDTs or decode Sparkplug B. Physical-device and independent first-time-user timing remain to be validated.

FAQ

Common questions

Related guides

Continue from here