AirPlay 2 Troubleshooting
AirPlay 2 speaker does not appear in iOS
| Symptom | Likely cause | Resolution |
|---|---|---|
| Room does not appear anywhere in the iOS AirPlay list | iPhone and Control4 device are on different network segments, or device discovery is blocked | Confirm the iPhone is connected to the same network as the AirPlay 2 device. On managed or segmented networks, confirm that mDNS or Bonjour forwarding is enabled between VLANs. |
| Room appears briefly and then disappears | Device IP address is changing or Wi‑Fi signal is unstable | Assign a fixed IP address or DHCP reservation for the device. Verify Wi‑Fi signal strength or connect the device to Ethernet. |
| Room appears but does not play audio | No Auto-Play room is currently assigned | If Direct mode is expected, verify the audio connection in Composer Pro. If using Stream mode, assign an Auto-Play room using the Control4 app. |
| Room name is incorrect or outdated | Speaker name was not updated after project changes | Rename the speaker using the Control4 app. Inform the customer that renaming will disconnect any active AirPlay session. |
| Secondary CORE controller does not show AirPlay 2 | Controller may lack the Apple security chip | Escalate to confirm whether the unit is from the affected hardware batch. This issue cannot be resolved through software updates. |
| Primary CORE controller does not appear for AirPlay 2 | Primary controller runs HomeKit and does not support AirPlay 2 | This is expected behavior. Direct AirPlay usage to secondary controllers or Ryff-enabled audio devices. |
Audio and synchronization issues
| Symptom | Likely cause | Resolution |
|---|---|---|
| No audio when AirPlay starts | Zone is disabled or Auto-Play room is not set | Verify that the AirPlay 2 zone is enabled in the driver and that an Auto-Play room is assigned. Manually turn on the room using a Control4 interface if needed. |
| Starting AirPlay stops music that was already playing | AirPlay takes control of the Auto-Play room | This behavior is expected. Explain that starting AirPlay always replaces the current audio in that room. |
| Control4 rooms are out of sync with HomePods | Audio is routed using Stream mode | Reconfigure the primary room using Direct mode in Composer Pro. This reduces latency and restores synchronization with Apple devices. |
| Audio is not synchronized with video on the television | Stream mode introduces processing delay | Use Direct mode for rooms with televisions to minimize audio delay. |
| Multiple rooms drift out of sync | Customer selected multiple AirPlay speakers in iOS | Recommend using a single AirPlay speaker with multiple Auto-Play rooms or adding rooms through the Control4 session interface. |
| Audio stutters or cuts out | Weak or unstable Wi‑Fi connection | Connect the device via Ethernet if possible. If Wi‑Fi is required, confirm signal strength and minimize interference. |
| iOS volume control does not affect room volume | Internal messaging connection has dropped | Check the MQTT broker status in the AirPlay 2 Multizone Driver. Power cycle the AirPlay 2 device to restore connectivity. |
Known issues
Music service icons missing after adding a service
After adding a new music service such as TIDAL, icons may not appear in the Ryff app or may show as blank tiles.
To resolve this, open the Ryff app, navigate to Settings, select Support, then Support Settings, and choose Sync my device. Icons should appear within one minute.
Play or pause restarts the current track
Pressing play or pause on a Control4 interface may cause the currently playing track to restart. This is a known issue in the current driver version.
No workaround is available at this time. Customers should use playback controls within the streaming app on their Apple device.
Multiple SA1 devices appear with the same name during setup
During initial OvrC setup, multiple SA1 devices may default to the same name. This can make device identification difficult in later steps.
Rename each device during the setup process. If setup has already progressed, rename devices directly in OvrC before continuing.
Network requirements
AirPlay 2 relies on multicast discovery and low-latency network communication. Many professional and managed home networks block these features by default.
Required network behavior
- Enable mDNS or Bonjour forwarding between the network used by Apple devices and the network used by Control4 devices.
- Allow multicast traffic between VLANs. Do not suppress or filter multicast packets.
- Allow TCP port 7000 for AirPlay audio traffic.
- Allow UDP ports 319 and 320 for clock synchronization.
- Assign fixed IP addresses or DHCP reservations to all AirPlay 2 devices.
Network validation tip
To quickly isolate network issues, connect the customer’s iPhone to the same network segment as the AirPlay 2 device. If the speaker appears immediately, the issue is related to network segmentation or multicast filtering.