Connect to a BluOS Device

HiFi Control connects directly to BluOS-enabled NAD and Bluesound players on your local network. No internet port forwarding is required.

Before You Start

1. Confirm that the BluOS player has joined the home network. On Bluesound players, a solid blue status light means the player is connected; indicators on other BluOS products vary by manufacturer.
2. Connect the Windows PC and player to the same trusted home LAN. Ethernet and Wi-Fi can be mixed, but avoid guest networks and isolated IoT networks.
3. Temporarily disconnect any VPN on the PC.
4. Install any available player firmware update from the BluOS Controller app.

Check the Player With the Official BluOS Controller App

The official BluOS Controller app is the best first test because it uses the local network and provides player diagnostics.

1. Open the BluOS Controller app on a phone, tablet, Windows PC, or Mac connected to the same home LAN.
2. Confirm that the player appears and test volume or playback.
3. Select the player, then open Help & Support → Diagnostics. Depending on the Controller version, this may be under Home → Settings or the desktop navigation drawer.
4. Note the player’s IP address, MAC address, Wi-Fi network, signal strength, and BluOS version. The official BluOS diagnostics guide describes the available information.

If the BluOS Controller cannot find the player, restart the player by unplugging it for 30 seconds, relaunch the Controller, and try a temporary Ethernet connection directly to the router. See BluOS’s missing-player troubleshooting.

If the BluOS Controller works but HiFi Control does not, focus on the Windows PC’s network profile, firewall, VPN, and the connection tests below.

Add the Player in HiFi Control

You can add a player during the Setup Wizard or from Settings → Favorite Devices.

1. Start device detection and wait for the scan to finish. BluOS discovery normally takes about 5 seconds.
2. Select each player you want to add.
3. If a player is not found, add it manually with the IPv4 address shown in BluOS Diagnostics.

Manual entry bypasses automatic discovery, but the PC must still be able to reach the player on TCP port 11000. Saving the detected MAC address lets HiFi Control recover the player if its address later changes.

Work Through Network Problems

Check these items in order:

1. Keep discovery on one LAN. BluOS uses mDNS/Bonjour, which is link-local and normally does not cross subnets. A guest SSID, isolated IoT VLAN, or client/AP isolation can block discovery even when both devices have internet access.
2. Allow multicast. The router, access point, switch, and security software must pass mDNS traffic. BluOS documents that a player can still answer a ping or open its web panel while blocked mDNS keeps it out of discovery results in its router guidance.
3. Disconnect VPN software. A VPN can change the preferred route or interfere with local multicast.
4. Check Wi-Fi strength. BluOS says signal below about -65 dBm can affect high-quality playback. If the value in Diagnostics is weaker, move the player or access point, reduce obstructions, or test with Ethernet. See BluOS signal-strength guidance.
5. Check the saved address. If the problem started after a router restart, select Start Discovery on the disconnected card or update the address in Settings → Favorite Devices.
6. Reserve the address. Create a DHCP reservation for the player in the router so its IP address stays stable.
7. Update and restart. Update the player through the BluOS Controller, then restart the router, wait for it to become ready, restart the player, and reopen HiFi Control.

A successful ping or player web page is useful but not conclusive. It proves direct IP reachability, not mDNS discovery.

Check the BluOS Connection Port

Open PowerShell on the PC and replace 192.168.1.50 with the IP address shown in BluOS Diagnostics:

Test-NetConnection 192.168.1.50 -Port 11000

TcpTestSucceeded : True confirms that the BluOS HTTP control service is reachable. You can also enter http://192.168.1.50/ in a browser to test the player’s built-in web panel, although web-panel access does not test port 11000 or multicast discovery.

If port 11000 succeeds but automatic detection fails, add the player by IP address and investigate mDNS rather than the control connection.

Check Windows Firewall

Keep the firewall enabled.

1. Open Windows Security → Firewall & network protection.
2. Confirm that the current home network uses the Private profile.
3. Open Allow an app through firewall and allow HiFiControl.exe on Private networks. If you create a custom rule instead, limit it to the Private profile and local subnet.
4. Check any third-party antivirus, endpoint-security, or firewall application for a separate local-network, multicast, or application rule.
5. Retry device detection and the port 11000 test.

For advanced firewall or VLAN configurations, BluOS uses the following local-network traffic:

Purpose	Traffic to allow
Automatic discovery	mDNS/DNS-SD on 224.0.0.251:5353 over UDP, advertising _musc._tcp.local.
BluOS control and live status	PC opens HTTP connections to device TCP port 11000
Play a file from the PC	The player connects back to a dynamic TCP port opened by HiFiControl.exe

Do not create an inbound Windows rule for port 11000. That port is on the BluOS player, not the PC. Do not forward these ports from the internet.

Common BluOS Problems

Symptom	What to do
BluOS Controller and HiFi Control both miss the player	Confirm the player’s network indicator, restart it, and temporarily connect it directly to the router with Ethernet
BluOS Controller works, but HiFi Control detection finds nothing	Check the PC’s Private profile, VPN, mDNS/UDP 5353, and network isolation
The player web panel opens, but discovery fails	Multicast discovery is blocked; check mDNS/Bonjour handling
The player is listed but will not connect	Check the saved IP address and TCP 11000
The player disappeared after a router restart	Use Start Discovery, update the saved address, and create a DHCP reservation
Playback pauses or the player disconnects on Wi-Fi	Check signal strength in BluOS Diagnostics; improve coverage or use Ethernet
The player shows Needs Setup or returns to hotspot mode	Reconnect it with the BluOS Controller; after a router change, a temporary wired setup is often the simplest route
Controls work, but a file selected on the PC will not play	Check the Private-profile application rule, client isolation, and device-to-PC traffic
BluOS works, but Dirac does not	Check device support and configured Dirac slots; Dirac uses the same host and TCP 11000 connection
Only a streaming service fails	Check the service account, internet access, and player firmware; the local BluOS connection may be healthy

Collect Diagnostics

If the connection still fails:

1. Record the player IP address, MAC address, signal strength, and BluOS version from the BluOS Controller’s Diagnostics page.
2. Open Settings → About in HiFi Control and enable Extended Logging.
3. Restart HiFi Control and reproduce the problem.
4. Check Settings → About → Issues → View recent issues.
5. Open the log folder from Settings → About → Logs → Open log folder.
6. Include the current log file and Installation ID when contacting support.

See Logging & Diagnostics for the complete log-sharing steps.