Getting Started With Integrations

Use this task entry page to identify an integration reference and prepare for site commissioning. This page does not define device-specific behavior.

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Find an Integration

Open the category that matches the device or service.
Prefer the device-specific integration page when the product, family, or model is listed. If it is not, review any generic protocol page and confirm that it covers the required operations.
Confirm the reference scope before using its configuration and feature guidance.

Caution

Do not assume that an unlisted device is supported or unsupported. A shared protocol does not make a device-specific integration interchangeable with a generic one. Check the exact product and operation against the page.

Request an Integration

An Integration Request asks Riedel to assess a device, service, or control capability that is not covered by an existing device-specific integration or a suitable generic protocol integration. Contact Riedel Customer Success through the Customer Portal on my.riedel.net and follow Customer Support for the required request details. Coordinate with the system integrator where applicable.

Include the vendor and product/model, firmware or software version, target hi version, protocol or API, required operations, network/deployment context, and available vendor documentation.

Information

A request is for assessment; it does not confirm support or commit Riedel to develop or deliver an integration.

How to Read a Device Page

Each device page describes the expected protocol, network model, required configuration, supported features, and known limitations that apply to the device.

The device page is the canonical public source for its ports, connection direction, authentication requirements, and required license. Category indexes provide generated summaries and links only.

Sections appear only when they apply. An omitted optional section does not mean that there are no configuration requirements, limitations, or compatibility constraints. Validate them during commissioning.

When a page includes Device Coverage, Tested With identifies the specific devices tested with hi. It does not extend the claim to unlisted models, firmware versions, or features. If Tested With is absent, the page does not list specific tested devices.

Where a device-specific integration page exists, use it instead of treating that product as a generic compatibility candidate. Potentially Compatible (Not Yet Verified) applies to candidates without a device-specific page; a shared protocol or connection method is not a supported-device claim. Validate those candidates during commissioning.

What the Catalog Does Not Assert

Firmware compatibility ranges unless the page lists them.
Device-side default ports unless specified.
Command-level feature coverage unless explicitly listed.
License availability for a specific deployment.

Commissioning Checklist

Confirm the device or service appears in the supported integration catalog.
If no suitable device-specific or generic page is listed, collect the details above and follow Customer Support to raise an Integration Request.
Validate the target device firmware and protocol options with the vendor documentation.
Confirm network reachability, credentials, firewall policy, and any multicast requirements in the deployment environment.
Confirm the required hi licenses before enabling the device in production.