Understand and manage One-Links

What a One-Link does

A One-Link is the connection used to connect devices or services to One-Home. It supplies the devices and their capabilities to Core. You then use those devices through Devices, their room or your selection in One-Views.

A visible brand name does not tell you which functions every device supports. Always check the controls of the device actually connected. For example, a light without colour capabilities does not receive colour controls merely because it uses the same One-Link as a colour light.

Distinguish preparation from a connection

In the demo, One-Links > Add One-Link > Prepare One-Link lets you save a name, connection preference and notes. Prepare One-Link saves that preparation on this device. It does not connect real devices or run a network scan for your Core.

Sample statuses and sample devices also belong to the demo. A saved local or cloud preference does not change an existing connection. For real equipment, open the app on your own Core and sign in there with your Core account.

1. Use the demo to check what you want to connect.
2. Choose Connect Core and open your own Core.
3. Check for Connected to Core before setting up a physical connection.

Open the correct management environment

In Core v0.37.0, Philips Hue has its own pairing procedure in the new interface. HEOS, EasyControl and Mitsubishi retain their existing connections. Manage other One-Links through the existing Core environment; the new interface does not automatically include every management function.

1. Open One-Links on your connected Core.
2. For Hue, use One-Links > Philips Hue > Pair Bridge.
3. For other connections, use the Core management link at the bottom of the page. Administrators can also use Connection > Open Core management.
4. Open the existing One-Links there and follow the instructions for the relevant connection.

Prepare a real connection

First check that the device works in its manufacturer’s app or controls. Identify the Bridge, controller or connection you want to use. For local connections, have the correct local address ready and check reachability from Core.

Ask the administrator to establish whether the required One-Link is present on this installation. A catalogue example is not evidence of an installed driver. Then follow the specific pairing procedure; each connection may have different requirements. Do not put passwords or secret pairing keys in notes.

Check more than the connection message

A connection becomes useful in practice when you can find the correct device and confirm its available controls. Start with one device so that an incorrect name or assignment is immediately apparent.

1. After pairing, check which devices were retrieved.
2. Assign one device to a recognisable room.
3. Open Devices and find that device.
4. Perform a supported action and wait for confirmation.
5. Compare the real state and check the name and room on a second signed-in screen.

Manage access and removal deliberately

Only administrators pair a Hue Bridge. Residents see and operate only devices within their permitted rooms. View permission does not grant control permission, and selecting a device in One-Views does not expand that access.

Disconnect an active connection through Core management. In the demo, you can remove an unused preparation; this removes its saved name, preferences and notes on that screen. It does not disconnect a real Bridge. Always check the environment and which devices depend on the connection.

Look for the cause in the right place

If nothing in the home works, check the connection to Core first. If devices from one One-Link fail, check that connection and its network or service. If only one device is missing, check power, room assignment and permissions.

For Hue, use Check connection to retrieve lights again. A changed Bridge identity or revoked access may require pairing again with the physical button. For other problems, record the One-Link, Core version, affected devices and exact error message for the administrator.