Generic Ember+ Compatible Router Integration Configuration

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.

Configuration Overview

The generic Ember+ integration has one configuration. hi discovers the matrices in the Ember+ tree of the provider, so the provider decides what hi sees.

Configuration	What hi Sees	Use When
Ember+ Provider	The matrices that the provider publishes in the top four levels of its tree, and the Parameters that it publishes.	The device has no dedicated hi integration and publishes a matrix over Ember+.

Caution

Use a dedicated integration when one exists for the device. The generic integration infers video, audio, GPIO, or data from the identifier and description of the matrix and the name of its parent, and it does not offer a setting to point it at a specific matrix.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Use the vendor configuration tool of the device to read the Ember+ provider address and Port. An Ember+ viewer helps to confirm where the matrix sits in the tree.
Confirm that the Ember+ provider publishes the matrix that hi must control.
Confirm the network access in Network Requirements.
Ember+ has no authentication. Anyone who can reach the Port can route. Keep the provider on a routing-control network.

Configure Ember+ Provider

Device Configuration

Confirm with the device vendor how to enable the Ember+ provider and which TCP Port it uses. 9000 is common but not fixed.
Confirm that the provider publishes at least one matrix in the top four levels of its tree.

hi Configuration

Add the Ember+ Compatible Router integration (manufacturer Generic) in Inventory.
Enter the provider address. The template default Port is 9000. Enter the Port that the provider uses when it differs.
Create the Node. No additional matrix-selection settings are required when creating this Node. It searches the top four levels of the tree for matrices and creates the Sources and Destinations from them.
After the Node is created, the Operations group shows Reinitialize Router, Reinitialize Parameters, and Clear Parameter Cache. Reinitialize Router disconnects the routing control connection and restarts initialization.

Settings Summary

Setting	Device Side	hi Side
Address	Ember+ provider address	Provider address
Port	Ember+ provider Port	Port default `9000`

Common Checks

Symptom	Check
The Node does not connect, or it disconnects every few seconds.	Confirm the Port, and confirm that the provider answers Ember+ keep-alive requests. hi disconnects when no answer arrives within 10 seconds.
Discovery does not start.	Confirm that the Ember+ provider is enabled on the device, then check the network path from the hi server to the provider.
No matrix appears.	Confirm with an Ember+ viewer that the matrix sits in the top four levels of the tree.
A matrix appears with the wrong signal type.	hi infers video, audio, GPIO, or data from the identifier and description of the matrix and the name of its parent. Check those names in the provider.
A Parameter change from hi has no effect.	Confirm that the provider marks the Parameter as writable, then read the value back. A provider can ignore a write without an error.
Sources or Destinations are out of date after a provider change.	Select Reinitialize Router in the Operations group.

Verify the Configuration

Wait for hi to discover the Ember+ provider tree. Compare the discovered Sources, Destinations, and several Crosspoints with the provider in an Ember+ viewer. Route a noncritical Destination from hi and confirm the change in the viewer. Then change a Crosspoint from another Ember+ consumer and confirm that hi shows it without a restart, because hi subscribes to Crosspoint changes.