AirPlay Sending and Receiving
Sending music from ECHO to a speaker and receiving audio from a phone or Mac into ECHO are separate paths. Receiver controls and protocol options depend on platform, channel, and installed build.
Choose the direction
Section titled “Choose the direction”| Goal | Entry and scope | Confirmation |
|---|---|---|
| ECHO → speaker or receiver | Connect AirPlay sending, maintained as AirPlay 1 / RAOP compatibility | Connect, check state, and hear actual output |
| Phone / Mac → ECHO | AirPlay Receiver in Connect on builds containing that implementation | Enable it and select ECHO from the sender’s audio-output picker |
| Experimental AirPlay 2 receiving | Receiver protocol option requiring a compatible native component | Verify discovery, pairing, session setup, incoming audio, and local output separately |
Experimental AirPlay 2 receiving does not establish AirPlay 2 speaker sending, multi-room synchronization, or compatibility with every Apple device. Older “AirPlay 1 only” guidance describes the sending path.
Send to an AirPlay 1 device
Section titled “Send to an AirPlay 1 device”- Use the same LAN and enable an AirPlay 1 / RAOP-compatible receiver mode.
- Refresh Connect and select the device.
- Try an ordinary MP3 or FLAC; inspect connection state and actual output.
- A receiver requiring AirPlay 2 may not work through this sending path.
See Connect and LAN requirements.
Receive phone or Mac audio
Section titled “Receive phone or Mac audio”- Open AirPlay Receiver in Connect; check receiver name and local output device.
- Start with the classic protocol. Test an experimental option separately when your build provides it.
- Choose ECHO from the iPhone, iPad, or Mac audio-output picker. Screen Mirroring is a different feature and is not implemented by this receiver.
- Start playback on the sender and check receiver state and desktop volume. Discovery alone does not prove audio reception.
- Stop sending and disable the receiver when finished if desired.
Sender application policies, OS versions, and content rights still apply. Receiving does not bypass accounts, DRM, or platform access controls, and is not a compatibility guarantee for every sender.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Check |
|---|---|
| ECHO or speaker missing | Enabled service, same subnet, guest isolation, VPN, firewall |
| Discovered but pairing/session fails | Protocol, both versions, native component, displayed error; reconnect after changing protocol |
| Connected but silent | Sender playback, incoming audio, local output, volume |
| Receiver component unavailable | Platform/build packaging; see Windows startup |
| Need HomePod multi-room or screen mirroring | Outside the currently established complete support scope |
Reports should identify sending or receiving, ECHO version, sender OS, device, protocol, and whether failure occurs during discovery, pairing, or playback. For local WASAPI / ASIO problems, use Audio Output.