Generic Ember+ Compatible Router

Driver Maturity

Production

Recommended for normal production use.

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.

Minimum hi Version: v2.0.0

Overview

This integration connects to an Ember+ provider. It discovers the published tree and exposes matrices, parameters, and subscriptions.

Network Requirements

Allow outbound TCP from hi to the Ember+ provider on Port 9000 by default.
The provider Port is configurable and may differ from the template default.
No callback or inbound connection to hi is used.
Keep the plaintext connection on a trusted management network.

Standards Conformance

Standard	Conformance	Notes
Ember+ (Lawo)	Glow DTD parameter tree per Ember+ spec	Open community specification used as a de facto standard widely adopted

Operator Workflow

UI Surface in hi: Routing Matrix, Inventory, and Parameter Control
Layers Controlled: Matrices and parameters published by the provider
Routing Semantics: hi exposes the Sources, Destinations, and Crosspoints published in the matrices that hi discovers.
Notes for Operators Familiar with the Vendor's Own Tooling: hi exposes only the matrices and parameters published in the provider's Ember+ tree.

Connection Details

Property	Value
Protocol	Ember+ (S101 framing Glow DTD)
Transport	TCP
Default Port	9000 (template default device-configurable)
Authentication	No credentials are configured in hi for the Ember+ connection
Encryption in Transit	Not provided by Ember+
Connection Model	Persistent TCP with asynchronous subscription-based updates
Required License	hiBase
Traffic Flow	Outbound from hi

Required Configuration

Parameter	Description	Default
Host / IP Address	IP address of the Ember+ provider device	-
Port	TCP port for the Ember+ provider	9000
Reinitialize Router	Operations button that disconnects the routing control connection and restarts initialization available at runtime	-

Device-Side Setup

Follow Generic Ember+ Compatible Router Integration Configuration for the device-side and hi-side configuration steps.

Supported Features

Feature	Access	Exposed Operation and Scope
Provider Tree and Values	Read-only	Discover exposed nodes, Parameters, matrices, and current values.
Parameter Values	Per-parameter access	Write only Parameters whose Ember+ access metadata permits writes.
Crosspoint State and Subscriptions	Read-only updates	Read and subscribe to exposed Crosspoint/state changes.
Crosspoint Routing	Read/write	Set routes only on matrices and Crosspoints exposed for control by the provider.

Device Coverage

Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies compatibility candidates that use the same protocol or connection method. Device-specific configuration, firmware, and feature support can affect results.

Use the device-specific integrations for DirectOut PRODIGY Series, Ereca Stage Racer, Lawo mc² Series, Lawo mc² UHD Series, Lawo crystal Series, Nevion VideoIPath, Riedel MediorNet TDM, and STAGETEC Audio Console.

For Lawo V__link4 and V__pro8 Parameter Control, use the Lawo Ember+ Parameter Controllable Device reference and follow its feature scope. For STAGETEC audio consoles, use the STAGETEC Audio Console reference. Use this generic router reference only when the required matrix-routing operations are published by the provider.

Tested With

Calrec ImPulse
Lawo HOME
Lawo V__link4
Lawo V__pro8

Potentially Compatible (Not Yet Verified)

Other Ember+ providers that expose a matrix with writable Crosspoints.

Known Limitations

Ember+ does not define authentication or TLS. Keep the control connection on a trusted management network.
Ember+ providers choose their own TCP Port. 9000 is common but not fixed. Use the Port that the provider configures.
Ember+ providers choose which parameters, matrices, and functions they expose, and which are writable. Two providers that both implement Ember+ can present different trees; compare the discovered Ports and Crosspoints with the device before routing.
A provider can ignore a request that it cannot satisfy, for example a write to a read-only Parameter, without an error response. Confirm a changed value by reading it back.
Devices with very large Ember+ trees may experience slower initial discovery times.
Non-standard or proprietary Ember+ tree layouts may not be discovered. hi searches only the top four levels of the tree for matrices, and it infers video, audio, GPIO, or data from the identifier and description of the matrix and the name of its parent. An unmatched matrix uses the default type. hi does not offer a setting to point it at a specific matrix.
hi sends an Ember+ keep-alive request every 5 seconds, and it disconnects when the provider does not answer within 10 seconds. hi requires the provider to answer keep-alive requests.

What's Not Supported

Engineering-level configuration (level naming, port labels, redundancy setup) - use the vendor's native router-control tool.
Firmware updates - use the vendor's native update utility.
Hardware diagnostics and SFP-level health - surfaced by the device's own management plane, not this integration.
Ember+ Functions, including Qualified Functions, and function invocation. The Ember+ specification defines them from Glow 2.20, and hi never sends an Invoke command.
Ember+ Templates, including Qualified Templates, and template references. The specification defines them from Glow 2.40. hi requests all fields of each element, and it does not resolve template references.

Trademarks

Note

Ember+ is an open protocol originally developed by Lawo.