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

Set it up

1

Get the player on your network

Wired Ethernet is most reliable for fixed players. Reserve its IP in the router.

2

Install Remote97 on the same LAN

Download from the download page.

3

Discover or add the IP

The directed 11000 probe finds BluOS players; manual add works when multicast or scanning is restricted.

4

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.

Note: multi-room grouping behaviour depends on the BluOS firmware version. Older players may need a firmware update before group commands are accepted.

Troubleshooting