Wiim Ultra missing in Roon ready

[Claudiu]

Hi,

Wiim Ultra appears as chromecast device in Roon, but does not appear in the Roon Ready section. What could be the cause of it?

Thanks!

 

[r5yk5]

Hi,

Wiim Ultra appears as chromecast device in Roon, but does not appear in the Roon Ready section. What could be the cause of it?

Thanks!

You don't have roon ready switched on maybe?

 

[Claudiu]

It's been always switched on.

 

[Burnside]

Power cycle (I.e. remove from power, wait a few moments then power up again) your router, Roon core and Ultra.

 

[Claudiu]

Thanks, but this did not work...

 

[Burnside]

I don’t have Roon personally, but if I have it enabled selecting Roon Ready on the browse tab in the WiiM home app attempts to open the Roon app and connect to the Roon core. What happens if you try that? Also, do the Ultra and Roon share the same network?

 

[Claudiu]

The roon server is in a different VLAN than wiim ultr. Then again, wiim is detected as chromecast audio output. Only Wiim Roon Ready is missing. Why would one work, but not the other. If roon sees wiim, it should see it entirely.

 

[Burnside]

I'm not that network savvy, but this is what Gemini AI says:

" While Roon officially states that it does not support VLAN-separated environments and requires all components (Core, Remotes, and Outputs) to reside on the same Layer 2 broadcast domain, it is technically possible to have Roon Ready devices on a different VLAN than the Core, but it requires advanced network configuration.
Key Considerations for VLAN Separation:

• Discovery Limitation: Roon relies heavily on UDP broadcast and multicast messages for device discovery, which do not normally cross subnet boundaries.
• Required Configuration: To make this work, your router/firewall must be configured to pass multicast traffic between VLANs, specifically by enabling an mDNS bridge/repeater (such as Avahi).
• Firewall Rules: You must ensure that necessary ports are opened between the VLANs, as Roon uses specific, high-frequency communication that can be blocked by restrictive VLAN security settings.
• Performance: While it can work, separating VLANs can sometimes result in "flaky" connections or failed device discovery (especially for remote controls).

Best Practice Recommendation:
For the most stable, "plug-and-play" experience, Roon recommends placing all Roon-related devices (Core, endpoints, and controllers) on the same VLAN/subnet.
If you must separate them for security (e.g., IoT VLAN), ensure your network allows mDNS across the VLANs, but prepare for potential troubleshooting. "

 

[Claudiu]

My network is already configured that way, because I have other devices that function similarly.

 

[GeeTee]

I'm not that network savvy, but this is what Gemini AI says:

" While Roon officially states that it does not support VLAN-separated environments and requires all components (Core, Remotes, and Outputs) to reside on the same Layer 2 broadcast domain, it is technically possible to have Roon Ready devices on a different VLAN than the Core, but it requires advanced network configuration.
Key Considerations for VLAN Separation:

• Discovery Limitation: Roon relies heavily on UDP broadcast and multicast messages for device discovery, which do not normally cross subnet boundaries.
• Required Configuration: To make this work, your router/firewall must be configured to pass multicast traffic between VLANs, specifically by enabling an mDNS bridge/repeater (such as Avahi).
• Firewall Rules: You must ensure that necessary ports are opened between the VLANs, as Roon uses specific, high-frequency communication that can be blocked by restrictive VLAN security settings.
• Performance: While it can work, separating VLANs can sometimes result in "flaky" connections or failed device discovery (especially for remote controls).

Best Practice Recommendation:
For the most stable, "plug-and-play" experience, Roon recommends placing all Roon-related devices (Core, endpoints, and controllers) on the same VLAN/subnet.
If you must separate them for security (e.g., IoT VLAN), ensure your network allows mDNS across the VLANs, but prepare for potential troubleshooting. "

I know nothing about networks, but this sounds like a very impressive Ai reply, with full explanation and solutions ..
could this be the end of 'the Forum' .. ( only joking ) .. ( or is it )

 

[Burnside]

In that case, I suggest you raise a ticket to WiiM via the more/ feedback section in the WiiM Home app so they can inspect your device logs. I'd also give them as much detail as you can about your network setup as I've a gut feeling that's where the issue might lie.

 

[Burnside]

I know nothing about networks, but this sounds like a very impressive Ai reply, with full explanation and solutions ..
could this be the end of 'the Forum' .. ( only joking ) .. ( or is it )

It's the answer of last resort for me, trust me

 

[Claudiu]

In that case, I suggest you raise a ticket to WiiM

I suppose it's the remaining step to take.

Thanks!