Integrations
The Supported Integration Catalog routes system integrators to available device, service, and protocol guidance for hi human interface v3.0.0.
Start Here
-
Prepare an Integration before adding a supported device or service.
-
If a device is not listed, use the preparation page to identify the required protocol and connection details before requesting integration guidance.
Common Tasks
-
Add your first device after confirming that its integration is available.
-
Review Network and Firewall Ports before commissioning network connections.
-
Confirm Licensing before enabling an integration in production.
-
Review each device page's Known Limitations and What's Not Supported sections before commissioning.
Device Categories
Open a category, then select the device reference for its requirements and supported workflows.
-
Getting Started With Integrations Learn about Getting Started With Integrations.
-
Audio Consoles Learn about Audio Consoles.
-
Audio / Video Gateways Learn about Audio / Video Gateways.
-
Audio / Video Routers Learn about Audio / Video Routers.
-
Camera Integrations Learn about Camera Integrations.
-
Glue Learn about Glue.
-
GPIO and Tally Learn about GPIO and Tally.
-
Hardware Panels Learn about Hardware Panels.
-
IP Integrations Learn about IP Integrations.
-
Miscellaneous Integrations Learn about Miscellaneous Integrations.
-
Multiviewers Learn about Multiviewers.
-
Network Controllers Learn about Network Controllers.
-
SRT Compatible Devices Learn about SRT Compatible Devices.
-
Video Servers Learn about Video Servers.
-
Video Switchers Learn about Video Switchers.
Catalog Status
|
Status |
Meaning |
|---|---|
|
Available |
The integration is included in hi human interface v3.0.0. Firmware, licensing, and deployment-specific configuration still require commissioning validation. |
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.
Third-party product firmware and software compatibility is published only after Riedel approval.
Driver Maturity
Driver Maturity communicates the overall confidence and recommended use of an integration. It considers implementation completeness, interoperability testing, field validation, deployment experience, known limitations, and general confidence.
|
Maturity |
Meaning |
Intended Usage |
|---|---|---|
|
Production |
Established integration with high confidence and meaningful production deployment experience. |
Recommended for normal production use. |
|
Validated |
Tested against representative real-world systems and considered suitable for production use, with less deployment history than a Production driver. |
Suitable for production use. |
|
Preview |
Functional integration available while broader validation and field experience continue. |
Evaluation and non-live testing only. Not production-ready. Not recommended for live use. |
|
Experimental |
Early-stage integration where functionality, compatibility, or behavior is still being established. |
Development and lab use only. Not production-ready. Not recommended for live use. |
Maturity does not replace deployment-specific validation of firmware, licensing, network policy, credentials, supported features, or Known Limitations.
Related Documentation and Support
-
Software User Manual - Find current concepts, tasks, and reference guidance.
-
System Requirements - Review server, client, and deployment requirements.
-
Troubleshooting and FAQ - Diagnose an integration or commissioning problem.
-
Hardware User Manual - Review current Hardware Panel documentation.
Trademarks
Note
hi human interface is a trademark of RIEDEL Communications GmbH.
All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.