My Roon was working fine this morning but I needed to restart my wireless router this morning for an unrelated reason. After the router came back up, I opened Roon and it’s been stuck on “Remote Connection. Waiting for remote core…” for hours.
I have cycled the Nucleus on and off several times.
The Nucleus+ is connected to my router via ethernet. I have confirmed that the the cable works.
All of my endpoints are Bluesound and are connected to the same wireless router via wifi.
All of my devices I use to control Roon are on the same wifi as the endpoints and the Nucleus+ is hardwired to.
I have connected a monitor to the Nucleus+ with a tested HDMI cable and there is no signal from the N+ detected by the monitor.
Please let me know what other information I can provide.
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
6
Can you actually find the N+ on your network?
Using fing or similar so we know the ip address is correct.
As this started after a router restart I wonder if it assigned a different IP address or something else odd?
I cannot find it on my network. I have use the same ethernet cable to attach a different device and it has appeared on the network. I am only a novice when it comes to networking stuff…but I can follow directions if there is a way to discover if it has generate a different IP Address. (I’m guessing when/if I do get it back up I should create a Static IP Address for the Nucleus+?)
What I mean to say above is that the N+ is not showing up in a browser using the last IP address generated and the device is not showing up as connected to router to which it is physically connected.
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
8
The latter part is a little worrying that it’s not seen at all by the network.
Maybe you already tried this but can you connect a monitor to the N+ via HDMI, reboot the N+ and see what it shows on the monitor?
A picture of that screen on reboot would be great.
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
13
Well it’s obviously in warranty and the best place to have bought it from.
I’m going to ping @noris for you.
I think it needs to go back.
Hopefully he can get to it fairly soon.
We’re very grateful that you’ve let us know of the issue that you’re facing in the wake of the latest build release. We’re so sorry and would really love to make things right.
Morning. “in the wake of…” makes me think that you are taking a stand that your latest build release broke my Nucleus+. This is a fresh take on my problem. Are you suggesting that my N+ is not in need of warranty repair…unlike what was suggested yesterday?
Additionally, how do I search for something that is not attached to network? I can’t “grab a set of logs” from a device I can’t access, right (my N+)?
Yes, you are correct, if the unit can’t boot there would be no way to get logs from the unit and no HDMI output sounds like the unit is not booting properly.
Since the unit is still under warranty, it would be best if we send the unit to our repair center for further evaluation. I don’t believe the issue is related to the recent update, but it could have been a coincidence.
We will private message you to get RMA information, thank you.
