I use wired Ethernet with my RS130. I just discovered that if my wired connection drops and then is restored, the RS130 will not reacquire its assigned static IP address. I have to go into the RS130 Ethernet Settings and toggle the Ethernet to OFF and then back ON. Is this a known bug?
1 Like
Is this the same phenomenon as the community issue below?
https://community.roseaudio.kr/t/missing-lan-connection/15474
Unfortunately, we are unable to reproduce this issue with the routers we currently have, so we would appreciate your assistance.
Could you please provide the following information?
Requested Information:
- Router details (Brand and model)
- Did this issue occur immediately after the update (version 5.11.03)? Did it work properly before the update?
- Frequency and specific details or scenarios when it occurs.
- Does the issue persist even after changing the setting from DHCP to Static IP? (Path: Settings > Ethernet > Gear icon > Change DHCP to Static IP)
(*) Please send the details to shim1691@citech.kr. After reviewing your reply, we will provide further guidance via email.
From the description in the other thread, no I don’t think this is the same problem. My issue occurred when I momentarily lost the Ethernet connection to the RS130. When it recovered, the RS130 did not reacquire its static IP. I will email with the details shortly.
Yeah, exactly the same thing happens to me. Every time there’s a software update for the router, when it restarts the RS 130 indicates it’s attached to the network via fibre ethernet, but the rose app won’t connect to it, even though it knows it’s there. Like you, I have to go into the settings and toggle ethernet off and on again.
1 Like
Are you setting the static IP thru your router? The router sees the mac address and assigns the IP address, rather than the static ip address is set up on the Rose device itself?
Oh no, I don’t set a static IP address.
Ok, so does the ip address change?
Also within the Rose One app, you have the ability to scan the local network looking for your device. Have you tried that?
When I first got my RS520, I had some issues here until I switched over and set up a static IP address. Then everything worked. I’d recommend that you think about setting static IP addresses for key stuff that you attach on your network.
Okay so,
No the IP address stays the same, and strangely the RS 130 is even listed as connected in the router settings. However, stranger still the RS130 disappears from roon audio devices and the rose one app cannot connected to it. But as you say, when the app can’t connect to the RS 130 it gives you the option to scan the network, but when I do it won’t find it. Strangers still, the app even shows the RS 130, but when I select it the app revert back to the cannot find your device page again.
It’s very strange, the only way to reconnect it is to restart the rs 130. Which is fine but I am paralysed from the neck down and don’t always have my PA by my side, being as independent as possible is important to me. But it doesn’t happen very often so, I’m not too bothered.
I set my Roon server on a static IP address, so maybe I’ll try the 120 also, thanks for the advice.
Sorry there’s quite a few mistakes in the last message, but hopefully you get the point. I have to use voice control on an iPad and there are a few compatibility issues. It seems with leaving messages on the forum. Anyway, in the previous message I meant the only way to fix it is to restart the RS 130 directly from the device, which I need assistance for.
Ok… that’s kinda weird.
This did happen to me a while back but switching to a static IP address solved it. And I think it was fixed in the software as well. Maybe others can share their experiences.
@Rose_love , could there be an issue when restarting the network connection from suspend?
I would be curious if you could as a feature, keep the network alive while you go into sleep / suspend like you do for the USB ports?
@Smegel
Even when entering power-saving mode, network settings remain unchanged and the previously configured connection is maintained
Sorry,
I think you misunderstood…
I was asking that the network connection remain active when in suspend mode.
(It already is… because you can wake the unit up from sleep.)
The issue that some are facing is if they power down the unit and then use DHCP to get the network configuration. The weird thing is that they indicate that they still have the same ethernet address, yet other devices can’t see or ping the Rose unit. (Even though the unit is up and the router can see it. )
As if the network connection didn’t come up cleanly.
1 Like
That’s the other thread, Mike. I started this thread because the RS130 will not reacquire its static IP address if the network connection to the ‘130 happens not to be there when the ‘130 is powered up. When the network does come up after that, the unit shows 0.0.0.0 until the Ethernet widget is toggled.
1 Like
Exactly the same thing happens if the RS 130 is on or in standby, when the network is restarted after an updated. The Rose One app cannot connect to it and the ethernet connection on the RS 130 settings just has zeros. Like you say, you have to turn the ethernet off then on again to reconnect.
However, the interesting thing is in the EERO app for my network, RS 130 is still listed as connected, very bizarre.
1 Like
Ok so there’s a couple of things…
- The device isn’t getting its IP address properly.
OR - The device gets its IP address, but the service that monitors the specific port that allows your apps to connect to the device are not working properly, so there’s nothing to connect to…
OR - There is a firewall on the device and somehow in the last release the port isn’t open so all the connections fail. (which wouldn’t make sense because if you do a hard power reboot, the device works.)
Based on @Quark 's comment… I’d say that there’s something wrong with the app that listens to the network port(s) used by external apps.
But I’m just guessing and this is something Rose can test for.
1 Like
Not just the rose one app, also the RS 130 disappears from Roon audio devices. Even though my network app still shows the RS 130 IP address and, even in the rose one app shows it’s on the network but won’t attach to it until we go into the settings of the device and turn off ethernet and turn it back on.
It’s very strange and probably needs some kind of network expert to figure it out
Not just the rose one app, also the RS 130 disappears from Roon audio devices. Even though my network app still shows the RS 130 IP address and, even in the rose one app shows it’s on the network but won’t attach to it until we go into the settings of the device and turn off ethernet and turn it back on.
It’s very strange and probably needs some kind of network expert to figure it out.
I have a RS130 connected to a Arris cable router (i use Comcast) model Surf Board SBG7580-AC via WiFi. If my internet goes down and my RS130 is off, when I turn it back on I have to toggle the WiFi setting on the RS130 off and then back on again. I have not had moment where I lost internet connect while the RS130 was on or in use. So, I can’t say what happens under that specific circumstance.
The latest firmware update was suppose to fix this issue. Maybe it has? I don’t know since my internet connection hasn’t failed since the update.
I believe both apps would hit the same port(s) but I could be wrong.
I’m just thinking thru the issue.
It can’t be the firewall (assuming that they have one inside the Rose OS) because if you restart ethernet then the firewall would be there.
If the router can see the device… then ethernet is up so then it would fall to something in the app causing this.
But again, its a guess.
Looking at @Sumi 's comment… it would point to something in the network configuration.
Definitely weird.
It sounds like you have a IP address conflict were the RS130 has a set static IP address, and the router is assigning the same address to another device on your network.
Set the RS130 to Dynamic IP address and set your router to assign the RS130 a static IP address this will take care of the address conflict. It took care of the problem for me.