After 8/18 firmware update, ethernet connection cancels connection to Roon

[Exile72]

After updating my firware on 8/18, any ethernet cable connected to my Wiim Ultra will cause Roon to no longer see any connections with the Wiim ultra. Disconnect the ethernet cable and Roon sees the Wiim just fine. Any ideas as to why?

 

[adias]

After updating my firware on 8/18, any ethernet cable connected to my Wiim Ultra will cause Roon to no longer see any connections with the Wiim ultra. Disconnect the ethernet cable and Roon sees the Wiim just fine. Any ideas as to why?

Have you power-cycled the device? Off/On?

 

[Exile72]

Yes, power cycled, changed ports, reloaded Roon server. This appears to be a problem with the latest Wiim firmware update. If I connect an ethernet cable into my Wiim it will disconnect any wifi connection including Chromecast and Airplay. Basically an ethernet connection on the Wiim renders the Wiim unusable.

 

[adias]

Yes, power cycled, changed ports, reloaded Roon server. This appears to be a problem with the latest Wiim firmware update. If I connect an ethernet cable into my Wiim it will disconnect any wifi connection including Chromecast and Airplay. Basically an ethernet connection on the Wiim renders the Wiim unusable.

You probbaly sent WHA feedback, so soon you will hear back from @WiiM Support.

 

[hgo58]

Yes, power cycled, changed ports, reloaded Roon server. This appears to be a problem with the latest Wiim firmware update. If I connect an ethernet cable into my Wiim it will disconnect any wifi connection including Chromecast and Airplay. Basically an ethernet connection on the Wiim renders the Wiim unusable.

When connecting using Ethernet to your local network the WiiM has always disconnected the WiFi. Chromecast and other services just need to be on the same network. The connection method, Ethernet or WiFi, don't matter as long as it is to same logical network.

 

[Exile72]

When connecting using Ethernet to your local network the WiiM has always disconnected the WiFi. Chromecast and other services just need to be on the same network. The connection method, Ethernet or WiFi, don't matter as long as it is to same logical network.

In Roon, if things are working correctly, I can be connected via ethernet but Roon also sees the Chromecast and airplay options from the Wiim. Currently, connecting via ethernet kills all connections.

 

[hgo58]

In Roon, if things are working correctly, I can be connected via ethernet but Roon also sees the Chromecast and airplay options from the Wiim. Currently, connecting via ethernet kills all connections.

Your WiM Ethernet connection is properly not to the same local network as your Roon server and the WiiMs WiFi setup.

Can you still control the WiiM from the WiiM Home App on a phone?

 

[Exile72]

Yes, the Wiim works perfectly in the Wiim app. It seems as though Roon's latest software update has killed the ability to use the ethernet port on Wiim Pros.

 

[hgo58]

Yes, the Wiim works perfectly in the Wiim app. It seems as though Roon's latest software update has killed the ability to use the ethernet port on Wiim Pros.

The connection method don't matter. It is just different ways to connect to the network. The services on other devices cannot see how a device is connected.

It looks like your connections don't go to the same network.

 

[Exile72]

No, this setup has worked flawlessly for years. Roon has been very consistent. The ethernet connection from the Wiim into my network hasn't changed at all. The problem started after I updated both Roon and Wiim.

 

[hgo58]

No, this setup has worked flawlessly for years. Roon has been very consistent. The ethernet connection from the Wiim into my network hasn't changed at all. The problem started after I updated both Roon and Wiim.

Ok. But has nothing to do with WiiM is disconnecting the WiFi. That has always been like that. Only one network connection is active at the same time.

 

[Exile72]

to clarify, when the ethernet cable is connected to the Wiim, Roon no longer is able to see the Wiim. Roon can only see the wiim if it's connected via wifi.

 

[hgo58]

to clarify, when the ethernet cable is connected to the Wiim, Roon no longer is able to see the Wiim. Roon can only see the wiim if it's connected via wifi.

So the WiiM is connected to different networks depending on if it is Ethernet or WiFi. Roon havde no way to see how the WiiM is connected. It can just see it on the same network or not.

It may have been like that all the time and Roon havde been connected to two different networks. That is possible. With the Roon update that may have changed?

 

[Exile72]

Not sure what you're trying to say. I have four Wiim's and they're all on one network-both the wifi wiims and a ethernet connected wiim. The network never changes. They're always connected to only one network.
Roon has the ability to see all possible streaming options to a connected Wiim. So Roon can connect to a Wiim that's ethernet connected but at the same time, Roon can see that the Ethernet connected Wiim also can be streamed via Chromecast or Airplay.

 

[hgo58]

Not sure what you're trying to say. I have four Wiim's and they're all on one network-both the wifi wiims and a ethernet connected wiim. The network never changes. They're always connected to only one network.
Roon has the ability to see all possible streaming options to a connected Wiim. So Roon can connect to a Wiim that's ethernet connected but at the same time, Roon can see that the Ethernet connected Wiim also can be streamed via Chromecast or Airplay.

Sorry, I don't get that. Just saying that the connection method don't matter.

It do however look like you have more than one logical network in your physical network.

What are the IP addresses used by WiiM and Roon? Are they on the same logical network?

 

[Exile72]

Roon is the music server. All playback of the Wiim's is controlled through Roon. All on the same network.

 

[hgo58]

Roon is the music server. All playback of the Wiim's is controlled through Roon. All on the same network.

So WiiM is on 192.168.9.166 now. Do that matches the IP address you can see for the Ethernet connection or for the WiFi connection?

The WiiM may have different IP addresses for Ethernet and WiFi.

 

[harkpabst]

So Roon can connect to a Wiim that's ethernet connected but at the same time, Roon can see that the Ethernet connected Wiim also can be streamed via Chromecast or Airplay.

Honestly, I don't get this part. The WiiM Ultra doesn't support AirPlay and it never did with any production firmware. Maybe I got that wrong? I'm not a Roon user

It's understood that as soon as you connect your Ultra via Ethernet it no longer works with Room while it does when using the Wi-Fi connection. With an Ethernet cable connected the Ultra's Wi-Fi is (and always has been) turned off. That's normal and it's unrelated.

If I connect an ethernet cable into my Wiim it will disconnect any wifi connection including Chromecast and Airplay.

I cannot make sense of this section. As per above, the Ultra does not support AirPlay. Chromecast is supported but does not (and never did) require a direct Wi-Fi connection from your phone to your Ultra. It does require a Wi-Fi connection from your smartphone to your Wi-Fi access point (most likely integrated into your router) and any network connection from your router to the Ultra, be it Wi-Fi or Ethernet.

The only precondition for Chromecast is that your smartphone and your Ultra must be on the same logical network (which is not the same as all cables go to the same router) and all the protocols and ports required by Chromecast are not blocked.

Are you saying that - independent of Room - Chromecast from your phone to your Ultra no longer works with the ethernet cable connected? If so, then this is the proof of a network related issue.

 

[Exile72]

I've posted this issue on the Wiim support site as well as Roon support which is actively working on determining if it's a Roon issue.

 

[hgo58]

I've posted this issue on the Wiim support site as well as Roon support which is actively working on determining if it's a Roon issue.

Ok. Still think it's a network configuration issue. Maybe in Roon?