Roon not discovering all Loxone Airplay 2 endpoints due to multiplexing [Fix released]

[vadim]

Hello @Nik_Van_Looy

Thank you for the update.

We forwarded the fresh diagnostic data to the R&D team

[Atif]

Hi @Nik_Van_Looy Can you please also share more screenshots from the discovery app i.e. all the airplay zones that are discovered, and details of each Airplay endpoint of Loxone audio server? There is some mdns information that’s in your original screenshot but we’re not seeing it in logs, so want to investigate it further e.g. pk value in your discovery app is unique for each Loxone airplay endpoint, but we’re only see one pk value in logs.

More specifically, we seen mdns packets for Keuken AirPlay endpoint but not for Badkamer AirPlay endpoint.

[Nik_Van_Looy]

Here are the screenshots, PS: a new Loxone zone was added this week: Bureau.This is also not visible in Roon, just like Badkamer.

[benjamin]

Thank you @Nik_Van_Looy! We’ll follow up with more information as soon as possible.

[connor]

Hi @Nik_Van_Looy,

We’ve reached out via PM with some next steps. Thanks!

[connor]

To keep the thread apprised, @Nik_Van_Looy graciously agreed to test an experimental fix for Roon’s mDNS discovery and multiplexed Airplay2 endpoints (endpoints that share an IP address).

By all indications so far, this fix has been successful, which means it will be included in an upcoming Roon #earlyaccess build for broader testing, and then continue into a regular Roon release from there.

We will post here as soon as we have a timeline for release from engineering. Thank you again to @Nik_Van_Looy for patiently undertaking this test.

[Nik_Van_Looy]

Any news on the release schedule guys?

[noris]

Hello @Nik_Van_Looy ,

Thanks for your interest into this issue. We are checking with the team to see the current status of the fix.

[Nik_Van_Looy]

Hi, still no update?

[connor]

Hi @Nik_Van_Looy,

Thank you for your patience. The fix is included in the current Early Access release. We anticipate including this fix in the next production release, but we will confirm that here.

If you wish to test the fix in the meantime, you can follow these instructions to migrate your server and remotes to the Early Access branch.

Should you experience any problems with the fix or with the Early Access build, simply create an #earlyaccess thread and our team will investigate promptly.

Thank you!

[noris]

Hello @Nik_Van_Looy ,

The fix for this issue should have been released in one of our recent Roon updates. Can you please confirm if you are still seeing this issue, or there have been impvoements on your end? Thanks!

[Nik_Van_Looy]

Hi,

I am indeed using the release version of Roon now and it works!

Thanks!

Grts
Nik

[noris]

Hello @Nik_Van_Looy ,

Glad to hear that the fix helped! I’ll go ahead and mark your thread for closure, thanks again for your patience as we addressed this behavior.