A paired Bridge — what you should see

Once the codes are confirmed, the Bridge lands on Console and shows what it is now doing:

• Paired scene — the scene name, the browser and the account.

• DMX scope and Universes — taken from the scene itself. You do not configure universes in the Bridge; the scene's patch decides what it listens for.

• Network and Input — the interface in use, and whether input is healthy.

• Disconnect from this scene ends the pairing.

The last step is approval: when a console first appears on the network, the Bridge asks whether that source may drive the rig — Allow this console? · Art-Net · 192.168.0.101. Until you approve it, its frames are ignored. That is deliberate: on a busy network there is usually more than one thing sending, and admitting a sender automatically is a security judgement the Bridge does not make on your behalf.

A sender that never announced itself gets the same question rather than being dropped in silence, so a desk that starts sending DMX without a prior discovery reply still reaches you as a prompt.

Back in the browser, the toolbar walks the same states: No console → Waiting for Bridge → the pairing code → `Live DMX` once the desk is feeding the rig.