Can I group NAD speakers with other brands in Home Assistant?

In many cases, yes. Home Assistant supports multi-room audio grouping across compatible platforms. However, cross-brand grouping often has sync limitations. A managed setup tests and tunes speaker groups to minimize audible delay.

Can Home Assistant play announcements through NAD speakers?

Yes. Home Assistant can send TTS (text-to-speech) announcements to NAD speakers, including the ability to duck current music, play the announcement, and resume. This works for doorbell alerts, security warnings, or custom notifications.

Will NAD still work with its native app alongside Home Assistant?

Yes. Most media integrations coexist with the manufacturer's app. You can start music from the NAD app and Home Assistant will still see the playback state. However, simultaneous control from both can sometimes cause conflicts.

NAD & Home Assistant

Audio & Media

Home Assistant reaches NAD gear two different ways, and which one applies depends on the model. This NAD integration is a YAML-configured media_player platform for classic NAD receivers, talking to them over an RS232 serial link or Telnet. It has no discovery and no config flow.

NAD’s network audio is separate. NAD is a Lenbrook brand, so its streaming components run on BluOS, the same platform as Bluesound, and are controlled through the shared bluesound integration . Every BluOS-Enabled NAD component (M10, M33, C 700, M66) is discovered locally there and exposed as a media_player with no cloud account required.

BluOS-Ready NAD amplifiers such as the C 399 and C 3050 add streaming once NAD’s optional MDC2 BluOS-D module is fitted. Until then they have no BluOS media_player entity. See the bluesound integration page for the discovery, grouping, and firmware guidance that applies to the whole BluOS lineup.

Local control No cloud required

Selora NAD devices NAD

Visit NAD

HA Documentation

How NAD Works with Home Assistant

Getting NAD connected to Home Assistant and running reliably.

1

Discover & connect

Home Assistant discovers NAD media devices on your network automatically. Add them to see playback controls, volume, source selection, and grouping options.

2

Multi-room audio

Group NAD speakers with devices from other brands for synchronized whole-home audio. Control each room independently or as zones.

3

Event-driven media

Build automations that play specific audio based on events — doorbell rings, morning alarms, or custom announcements. Route different media to different rooms.

Common NAD Issues

The problems installers run into with NAD and Home Assistant — and how a managed setup prevents them.

Picking the right integration for the model

This NAD integration only covers receivers wired over RS232 or reachable by Telnet, and is set up in YAML. BluOS streaming components are not added here at all. They are discovered and controlled by the shared bluesound integration, added from Settings > Devices & services exactly like a Bluesound player.

BluOS-Ready models need the MDC2 module

The C 389, C 399, and C 3050 are BluOS-Ready. They only stream once the paid optional MDC2 BluOS-D module is installed, and have no media_player entity without it. The M10, M33, C 700, and M66 are BluOS-Enabled and work out of the box.

State updates lag on local polling

Like all BluOS devices, NAD components are read by local polling, so playback state appears in Home Assistant after a short interval rather than instantly.

Why installers choose managed NAD BluOS systems

BluOS-Ready amplifiers specified with the MDC2 BluOS-D module so streaming is present from day one
Discovery and mDNS reflection configured through the shared bluesound integration
Dirac Live room correction and BluOS firmware maintained across the system
Multiroom groups pre-built with the bluesound.join and bluesound.unjoin services

Learn How We Manage NAD