BluOS is the platform shared by Bluesound, NAD, DALI and Monitor Audio network players. Its control API is plain HTTP GET on port 11000 with query parameters, returning UTF-8 XML status documents. Remote97 parses that status to show what is actually playing, then sends commands such as play, pause, volume and group changes.
BluOS players do not consistently advertise a standard SSDP/mDNS service, so discovery uses a directed probe on 11000 plus manual IP add. The app also checks the response before classifying a device, so an unrelated web server on the same port is not mistaken for a player.
What you can control
- Playback — play / pause / stop / skip and current track status.
- Volume and mute — per-player and, where available, per-group.
- Grouping — join players into a multi-room group or ungroup them.
- Presets and sources — recall presets and switch inputs / streaming sources.
- One screen for everything — combine BluOS with Sonos, WiiM, an AVR and a TV in a custom control panel.
Set it up
Get the player on your network
Wired Ethernet is most reliable for fixed players. Reserve its IP in the router.
Install Remote97 on the same LAN
Download from the download page.
Discover or add the IP
The directed 11000 probe finds BluOS players; manual add works when multicast or scanning is restricted.
Control one player or the group
Group commands are sent to the group coordinator, matching how BluOS itself behaves.
Why local control matters here
Streaming services already run in the cloud, but your remote should not need to. A LAN round-trip for volume or grouping is near-instant and keeps working if the internet drops — you can still control local files, line-in and radio presets. There is also no account to create inside Remote97 and no subscription tier for basic transport controls. See why local IP control beats cloud hubs.
Troubleshooting
- Player not found: add the IP manually and confirm nothing else on the network is occupying 11000.
- Status never updates: the player's XML status endpoint may be blocked by a firewall or guest-network isolation.
- Group commands ignored: send them to the group coordinator, not an arbitrary member; update BluOS firmware if behaviour differs.
