· None of the above quite fits
· None of these quite match
· Numerous drop outs to one particular wired endpoint (Audio Pro C3).The endpoint has dual wired & wireless connections. Two other identical units working mostly fine.
· Fibre, 3x Eero 6+, wired backhaul, wired connection to AudioPro C3 speaker, via Netgear 5-port switch.
Hello @Hifipilot
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please disable the wireless connection, reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Hi @Vadim,
That’s the problem, I can’t! There is no option to select which network interface to use, and the manual says something like “your C3 will use the wired connection to support the wireless connection.” Goofy, huh?
Wi-fi strength is 100% for that unit, from the Audio Pro app. And obviously each interface has it’s own IP address.
Also, the Eero’s are set up as per Roon KB, with only one subnet.
Hi @Hifipilot,
Thank you for your post. We’ve gathered diagnostics and need a few key pieces of information in order to diagnose these dropouts precisely.
It looks like all C3 Zones are registered with Roon Server as Airplay Zones. We assume that’s the protocol with which you’re experiencing the dropouts?
Which is the Zone name of the C3 that has issues? We want to ensure we’re looking at the correct logs and not one of the functional endpoints.
Are you able to share the name of the track that was playing when you last experienced dropouts?
Lastly, does the Zone disappear from Roon entirely when these issues occur, or does playback simply pause? Is an error displayed in Roon?
We’ll watch for your reply and proceed from there. Thank you!
Hi Connor,
I believe Audio Pro can only use wireless for AirPlay.
The problem zone is ‘Kitchen’ (the other two Audio Pro’s are ‘Dining Room’ which is OK, and ‘Guest’ which is very good, almost never any issues, despite being the only non-wired one!). I’m aware there may be a bit of subjective bias: Kitchen on all day, the others, less so.
They’re mostly used for radio stations: LBC (frequent dropouts), BBC (a bit better) and Ibiza Global (excellent, can run for hours).
It was very bad this morning around 0910 GMT/1010 BST, none of the ‘soft resets’ worked and I had to reboot Roon Server. LBC was playing then. Also had one duplicate instance of Kitchen in the source list before and after reboot.
The Zone never disappears, but the connection is cut: progress bar continues, play symbol is replaced by stop symbol, but no audio. No error messages. Sometimes disabling/re-enabling the zone in Roon works, but not always. Usually have to reboot C3 and/or Roon Server.
Thanks to you!
Hi @Hifipilot,
As a quick test, please try playing the LBC browser player on any device that is connected to the same network. Do you encounter any dropouts from their live station URL outside Roon?
The duplication of the Kitchen Airplay Zone is something we can see in diagnostics on our end, and it’s part of what prompted the question in my previous response. Both of these endpoints share the same IP address from Roon’s perspective; Roon is receiving multiple mDNS announcements and inadvertently creating a second Zone for the same endpoint.
This shouldn’t be happening and we already have a ticket in the pipeline from previous reports of the same instance.
Do the affected Kitchen Zone C3 and the main Roon Server machine share an Eero node, or are they served by different mesh nodes?
The Airplay issues and the dropouts might have independent causes, however. We should be able to isolate both.
Thanks and we’ll stand by for your response.
Hi Connor,
No dropouts outside Roon using the LBC iOS app, which I often revert to if I don’t have time to reboot everything. They’re one of the UK’s largest networks, so I think their back-end is probably pretty robust.
Also, it’s been running fine on Kitchen for the last 4 hours or so, not sure if you’re already working some remote magic? 
Rock/NUC is wired into the unmanaged Netgear 8-port switch connected to the primary Eero which is connected directly to the fibre. The Kitchen is connected both wired and wifi, to a secondary Eero, which is backhauled to the primary.
We live in an old kind of long house, with thick stone walls, the primary Eero is in the middle, and the secondaries are at each end. Extremely robust performance for everything else, about 20 devices.
Thats great news @Hifipilot! I don’t believe we’ve shipped any updates on our end.
Feel free to share a fresh timestamp the next time you experience dropouts again and we’ll review a fresh diagnostic report.
Thank you
Hi @Hifipilot,
Just checking in on this. Were you able to grab a fresh timestamp the next time the dropouts came back so we can review a new diagnostic report? If the issue is still happening, send us that timing and we can take another look.
Please note, if we don’t hear back from you this thread may close automatically soon. If the thread auto-closes and you need further assistance, please submit a reopen support request via the technical support help form below and specify that the issue should be reopened. Thank you.
Hi Noris,
A few the last 24 hrs: 03/1110 BST
02/1240
02/1720?
Hi @Hifipilot,
Those timestamps confirmed what Connor suspected earlier in the thread.
Your Kitchen C3 is answering on two IP addresses at once, 192.yyy.x.4 and 192.yyy.x.28, both advertising the same AirPlay device ID. Roon opens the control session to one, but the speaker’s retransmit requests come from the other:
[airplay/clientV2] [192.yyy.y.4] resent packet to 192.yyy.y.28:58006Over 500 of these. That’s the wired and wireless interfaces each holding their own DHCP lease, with the AirPlay session split across both. It’s also why you’re seeing a duplicate Kitchen, the zone is rebuilt whenever the address flips.
Your Dining Room C3 shows the same split (.222 / .5). The Guest Room C3 answers on one address only and is noticeably more stable.
All three timestamps match this pattern: playback stops with no audio error, the speaker sends pause/suspend, and reconnects fail with RECORD failed: NetworkError, Connection reset by peer, or short read. At 03/1110 the zone was destroyed and recreated, reconnecting first at .4, then immediately at .28.
Worth ruling out explicitly: this isn’t bandwidth or LBC. Packet loss to the Kitchen over three days totals five packets, and the stream is arriving with 23x headroom right up to the moment audio stops. Every failure is on the AirPlay control channel.
Suggested next step: since the C3 won’t let you disable its wireless, the speaker needs to be reachable at one address rather than two.
Easiest test, unplug the Kitchen’s Ethernet for a day and run it wireless-only. If the address split disappears, so should the dropouts. We’ll review fresh logs afterwards and we’ll confirm. 
Hi Benjamin,
Many thanks for this, makes perfect sense. Guess the “wired upgrade” was actually nothing of the sort 
I implemented it pre-Eero, when we still had a flaky TP-Link mesh system that had poor coverage at that end of the house.
I’ll disconnect the wires, reboot everything, and report back. It probably doesn’t help that AudioPro’s networking approach is also quirky, from various reports around the net.
Which is a real shame. The reason I bought 2 more while I still could, was that they were a very rare bird: a portable, good-looking, compact, metal hi-fi speaker with AirPlay/ethernet…but too beautiful for this world I guess. 
Edit: Both Kitchen & Dining Room are now disconnected, and still showing 100% wifi. As they should, given they’re within a couple of metres of an Eero.
Thanks again
Hi @Hifipilot,
Many thanks for the update, and for testing this so thoroughly.
That gives us a much cleaner picture. Disconnecting the wires and seeing both the Kitchen and Dining Room stay at 100% Wi-Fi is exactly the kind of result we wanted to see here, given how close they are to the Eero.
Glad to hear the wired upgrade was not really an upgrade in practice, even if the speakers themselves are a bit of a rare find. Let us know how things behave from here, and we will keep an eye on the follow-up.
