Normally: Ubiquiti UniFi setup, core via Ethernet and endpoints via Ethernet & WiFi
At time of issue: Virgin Media Superhub 3 in default mode. Core and main endpoints directly connected via ethernet. Other devices and APs via an unmanaged POE switch.
Connected Audio Devices
iPhone => Dragonfly Cobalt => Sonos Fives in stereo
ATV => TV => Topping D30 DAC => Cyrus Pre Amp & Cyrus power amps/Speakers - none currently choosing next purchase
Number of Tracks in Library
Stream from Tidal
Description of Issue
Due to building work and I think a fault with the Virgin Media Superhub 3 I had to revert back to using my ISP supplied one box wonder and reset it to default modem/router/switch mode. It works but isn’t great. I have disabled its internal WiFi and use my UniFi APs instead. This ISP wonder doesn’t want to work in modem mode. Waiting for Virgin Media to get back to me on this as the modem section on the PCB is the same regardless of the mode you’re in.
My IP range is all the same and port forwarding setup for Room Arc.
After finishing sorting my network out I opened Room Remote and and verified Room Arc was working under settings. I did not however open the Arc app.
Left work this morning and opened the Arc app to find;
Well it will depend if you can be sure you have port forwarding open on the virgin box. Your description is a little confusing but it sounds like you have a Unifi router usually but modem only mode on the virgin is not working so you have put the virgin back to hub mode.
So did you then go into the hub and set up port forwarding?
because you will have changed routing its very likely parameters on your network will have changed, including the network IP of your core, have you taken this into account?
My superhub 3 used to not change had to reboot it to get it to work sometimes. If you rebooted the hub at any point it may have updated the ip address of your home connection. They are not fixed on virgin but dhcp and can change. So maybe best reset arc and resestablish connection. Changing your router will also change internal routing so it’s likely got its knickers in a twist.
OK, but is your core a fixed IP if its not then it almost certainly will have received a different IP from the diferent router.
i.e does your port forward equate to the new IP, or were you using memory for the old IP?
IN principle as long as you are logged into the ARK app, it should be able to find the core. I know this is true because I am turning on the forward port on my UDM when out and about rather than have it running all the time.
I also have a ‘superhub 3’ and have already raised a problem during testing that if I happen to reboot the SH3, then I need to manually restart the core afterwards before ARC will work again - this is because the port forwarding stops working (verified by checking the ARC settings in Roon).
I can’t answer your question regarding needing to ARC app itself, but I suspect that as soon as the SH is rebooted connectivity is lost, so even if you open the app at this point it probably won’t connect