WiiM not showing up on list of DLNA…

rarewolf

Member
Joined
Jan 1, 2023
Messages
15
I use my WiiM Pro for communication between my headphones DAC/Amp stack and my JRiver Media Center server. That is, I rely on the WiiM showing up on a list of “zones” for the JRiver smartphone app (JRemote), for selecting music from the library and having the WiiM send it out its coax to the DAC.

However, and as of the last 2 weeks, the WiiM has fallen off the list of zones. I’m not sure of the comm protocol used by the WiiM, possibly DLNA, but for example, the WiiM is showing up on list of available Airplay/Bluetooth devices, but not DLNA (UPnP?).

I’m not claiming it’s the fault of the WiiM, but JRiver hasn’t been any help, and resetting my wifi mesh didn’t help either. However, the available wifi devices (e.g., our smart Tv) do show up on my Windows 11 computer (JRiver server), but they do not show up as a list of zones available to the Media Center software. So, I am here desperately looking for someone familiar with the possible causes of the problem…(?)

Cheers from the Avalon…
 
and resetting my wifi mesh didn’t help either.
I would check the IP addresses of your Wiim and PC.
Mesh networks can be problematic if the nodes are each acting as DHCP servers to your network
Is IPv6 enabled in the Network status of your Wiim ?
If so, disable it and report back
 
I would check the IP addresses of your Wiim and PC.
Mesh networks can be problematic if the nodes are each acting as DHCP servers to your network
Is IPv6 enabled in the Network status of your Wiim ?
If so, disable it and report back
Thanks for your response!

Re… the IP addresses… they’re on the same subnet as provided my my LAN wifi, if that’s what you mean…(?)

Re… IPv6… I had enabled it for troubleshooting, but it’s disabled now. I’m not sure if any changes would be immediate, but nothing has changed thus far…

Re… my wifi mesh and DHCP… I am unfamiliar with how to investigate this. My mesh is Google Wifi…
 
I have a similar problem with my Amp. The device is only recognized as a UPnP device shortly after a restart. Then it disappears from the UPnP list. My Mini and my Pro don't have any problems in the same network. I've been testing the Amp on WiFi for a few minutes. Here the device remains available as a UPnP device. Strange...
 
Thanks for your response!

Re… the IP addresses… they’re on the same subnet as provided my my LAN wifi, if that’s what you mean…(?)

Re… IPv6… I had enabled it for troubleshooting, but it’s disabled now. I’m not sure if any changes would be immediate, but nothing has changed thus far…

Re… my wifi mesh and DHCP… I am unfamiliar with how to investigate this. My mesh is Google Wifi…
ok,
Have you rebooted everything after disabling IPv6 to force rediscovery ?
Can you describe your network setup ?
Is your ISP device in modem mode ?
I assume your primary Google Wifi point is wired to your ISP modem ?
Are the Wiim and PC both close to the same Google Wifi point ?
 
ok,
Have you rebooted everything after disabling IPv6 to force rediscovery ?
Can you describe your network setup ?
Is your ISP device in modem mode ?
I assume your primary Google Wifi point is wired to your ISP modem ?
Are the Wiim and PC both close to the same Google Wifi point ?

All rebooted. No improvements yet, but wiil confirm later if anything changes.

Before I describe my setup let me 1st make the point that this has been working over the years perfectly. However, within the last month, I have upgraded the media computer from Win10 to Win11 Pro, and installed an update version of JRiver. All connections same as before, and I swear this new setup had also been working until ~10 days ago, when the WiiM didn’t show up as a zone.

Media computer connected directly to local Google Wifi mesh node, which is the primary node, which is connected directly to ISP modem. The wifi mesh provides a subnet different from the ISP modem, which everyone/everything connects to, including WiiM, smartphones, DAPs. My WiiM is upstairs from the media computer and hard connected to a mesh node. It is configured for ethernet input and coax output. The JRemote app connects to the media computer JR server, and is supposed to find the WiiM as a “zone” to output to.

Nothing has changed with the ISP modem, and should be in modem mode

Yes… primary mesh node connected directly to ISP modem

No… WiiM and media computer are upstairs vs downstairs, respectively…

A friend has a WiiM Mini he’s not using. Do you believe it can be used in any way for troubleshooting?
 
Can you ping the Wiim from your media PC ?
Can you see the Wiim as media device when you browse the network in file explorere on the PC ?
You may need to enable DLNA on the PC ?
When DLNA is enabled Windows Media Player should be able to see the Wiim as a device to cast to.
1741523549289.png1741523496514.png
 
Can you ping the Wiim from your media PC ?
Can you see the Wiim as media device when you browse the network in file explorere on the PC ?
You may need to enable DLNA on the PC ?
When DLNA is enabled Windows Media Player should be able to see the Wiim as a device to cast to.

Yes… I can ping the WiiM…

No… the WiiM, along with other wifi devices, are not showing up with Windows Explorer. I’ll look further into how this… along with DLNA being enabled, how can this be?

Yes… I have already enabled DLNA, and the WiiM shows up on the list. In fact, two days agoI had noticed that it had not been enabled, and I enabled it to find the WiiM finally showing up, which was quite the “AHA!” moment for me. But alas… it didn’t help…

The big mystery to me is how Jriver isn’t seeing the wifi devices, while Windows can(?) On the other hand, Explorer isn’t recognizing them either.
 


The big mystery to me is how Jriver isn’t seeing the wifi devices, while Windows can(?) On the other hand, Explorer isn’t recognizing them either.

As it turns out, it’s a Jriver problem. I rolled back my version of Media Center to the last trusted version before this all began, and now everything is working as it should (… except of course, not using Jr’s current version…)
 
I am using .71 - the latest public version and it sees my Mini and Pro. You might want to re-install that and see how it works. It might have been something about the installation.
 
Back
Top