Connecting to a Registry lets Buttons see every node that registry already knows about in one place, then adopt only the ones you actually want to control: instead of waiting for each node to announce itself directly or adding them one at a time.
This is the right approach when nodes are already registering into a registry (Buttons' own built-in one, or a separate registry appliance) and you want deliberate control over which of its nodes become Buttons connections.
Before you begin#
You need:
- The NMOS feature enabled (on by default).
- Access to create NMOS connections.
- The registry's reachable address, unless you're relying on discovery to find it.
Create the Registry connection#
- Open Connection → NMOS.
- Select Manual Add.
- Select Registry.
- Enter a Label.
- Leave IS-04 set to Auto unless the registry requires a specific supported version.
- Add one or more Registry endpoints. The lowest priority value is tried first; if it's unreachable, the next endpoint is used.
- Select Create.
Buttons confirms with Created NMOS Registry Connection! and adds the connection to the NMOS connection list.
Confirm the registry is reachable#
Open the new connection and its Registry tab. Registry reachability shows a live status dot, and each configured endpoint shows its own probe result: Reachable, Unreachable, or Probing registry endpoint... while a check is in progress.
Two further settings on this tab shape how the connection stays matched to the right registry:
- Connection Mode: UUID follows a matching discovered registry automatically; Static endpoints uses only the endpoints you entered, ignoring discovery.
- Registry UUIDs from Discovery Records: an allow-list of specific registry UUIDs this connection should follow, useful when more than one registry advertises on the network and you need to pin this connection to a particular one.
Choose what happens to nodes automatically#
Still on the Registry tab:
- Node adoption: Manual leaves every node for you to adopt individually on the All Nodes tab; Adopt All adopts every node the registry reports automatically.
- When a Node disappears: choose Do Nothing, Disable Node Connection, or Delete Node Connection for what happens to a connection that was created automatically for a node the registry no longer reports.
Browse and adopt nodes#
- Open the All Nodes tab.
- Review each node's API column to confirm its IS-04 version.
- Select Adopt on a single row, or select several rows and choose the batch Adopt action.
A successful adoption shows Node adopted!, and the node's status changes to Adopted. Adopted nodes also appear on the Adopted Nodes tab and in the main NMOS connection list, where you can open each one's own Node, Ports and Bundles, and Behaviors tabs the same way as a peer-to-peer node.
Set connection-scoped behaviors#
The
Behaviors tab on a Registry connection uses the same behavior settings described in
Configure NMOS connections, scoped to this registry connection instead of the whole system. Leave
Inherit behaviors on to keep following the system-wide configuration, or turn it off to set different behaviors for every node this registry connection adopts.
If you get stuck#
What you see | What to try |
|---|
The connection can't reach any endpoint. | Confirm the registry's address and port, and that Buttons' network can reach it. Check whether the registry itself is running. |
A node the registry reports never becomes adoptable. | Confirm Node adoption isn't set in a way that excludes it, and that the node's own registration is current. |
An adopted node's connection was unexpectedly disabled or deleted. | Check When a Node disappears: a node the registry stopped reporting is affected by whichever behavior is configured here. |
Two registries keep competing for the same connection. | Use Registry UUIDs from Discovery Records to pin this connection to the intended registry, or switch Connection Mode to Static endpoints. |
Where to go next#
