Connection and Identity

Connection & Identity is the first section on the Connections tab. It controls how the controller is named, found, secured, and connected.

UI path

1. Open Configuration.
2. Select Connections.
3. Expand Connection & Identity.
4. Edit identity, network, MQTT, or admin fields.
5. Click Save & Connect.
6. Reconnect to the controller if the hostname, IP, Wi-Fi, or Ethernet settings changed.

Controls

Control	What it does	Details
Device name	Names this physical controller in discovery, browser UI, logs, and integrations	This will be used as the hostname on your network. It needs to be unique per-device and navigating to devicename.local in a browser can usually get you to the operator page without needing to use Nexus Controller Manager
Room name	Groups controllers that belong to the same installation or experience
Wi-Fi SSID/password	Joins a wireless network
DHCP/static IP fields	Chooses automatic or manual network addressing	Most users won’t need to set this. DHCP should be used unless you know that it shouldn’t
Ethernet settings	Configures wired network access when available
Hide AP SSID	Hides the setup access point during normal operation	If you are not planning to connect the controller to your network then it is suggested to turn this on so the setup network doesn’t always publish itself for people to connect to. A power cycle of the controller will make it visible again so you can connect to it if you need to make changes
MQTT broker fields	Sets broker host, credentials, and room/topic prefix
Admin password	Protects the full Configuration UI	Your network itself is the first line of security but this password can help avoid users within your network from making accidental edits. If you lose this you will need to reset your controller to get access again and will lose your settings in the process, take backups.

Review checklist

1. Use a final prop-specific Device name before building integrations.
2. Use the same Room name across controllers in one room.
3. Prefer DHCP plus router reservation unless static IPs are required.
4. Save a recoverable admin password.
5. Use Identify after reconnecting to confirm the physical controller.