Following a brief power failure…now the Roon Remote app can’t find the Roon Core. How do I know where the problem is? …with the Roon Core?, the Network? the remote access devices? No changes made to network devices or settings before/after outage. Network has come back up and all other (non-Roon) devices, computer, TV, etc. are all working normally. I tried powering off then on both the Roon Nucleus and my router…returns to the same state. I looked at the back of the Nucleus. Power white light is on. At the ethernet connection, there is an orange light glowing below/left, and a green light flashing below/right. The Roon Nucleus is plugged in to a surge protector. I have no reason to think the Nucleus was hit with any kind of electrical surge.
Describe your network setup
NBN fire to home then Ethernet connections to all relevant devices including Roon nucleus
Try a cold startup, power everything down , WAIT then restart the network WAIT (get the idea) until the internet connection is showing a steady light . Then restart the server
It may help.
We used to have twice daily power outages , server starts up much quicker than the network, so Roon looks for a connection to 'Home" Before you have a stable network connection.
My NUC restarts on power on , so I saw this routinely. Normally I just restart the server software from the web admin page
We haven’t seen a response yet on this thread, and our diagnostic servers don’t see any activity associated with the unit in question for the last several weeks.
At this point, it’s worth connecting the HDMI output of the Nucleus to a monitor. This will outprint a diagnostic screen indicating if there are any hardware-level errors with the unit. Please share a photo or briefly describe the output of that screen here.
Please also attempt to access the WebUI of the Nucleus using a browser on another device. Share a screenshot if you see the interface at all.
Thanks Mike, Alex and Conner and apologies for the delay in updating. I tried the suggestions to no avail.
When I connected the HDMI to my Denon 4520 AVR the TV comes on and the Denon defaults to Roon (HDMI input 5) but no screen readouts appear. In the past if I was patient (as Mike suggested) text would appear and scroll and I would be connected. I totally shut down and restarted in an order that worked in the past allowing time between each step but no success.
Today I connected my work laptop to the HDMI but could not get access to the Roon on my laptop directory.
My next step will be to ask my work IT guru to have a look at it to see if he can find it on my system.
I shall persevere because Roon is an amazing product which I enjoy immensely. My workaround for streaming music is Sonos and while I have access to Qobuz, Tidal and Spotify it is not nearly as rich or easy experience.
My Roon outputs by usb to a reclocker then into a Devialet Expert Pro 1000 driving Paradigm Persona 7Fs in bi-amp configuration. It also outputs by USB to a Topping D10 DAC then RCA to Zen Taboo headphone amplifier.
I used to also connect Roon by HDMI to AVR and then by RCA to the Devialet Expert Pro but this was not as good sound as the USB via reclocker to Devialet Expert Pro and then I had intermittent issues with AVR switching on so I stopped the GAdMI connection.
I live in Darwin, Australia, a tropical part of the world and we are currently have a cyclone nearby and warnings in place. Who knows, we may (likely) lose phaser and on a restart I might fluke a stable connection again! Which would be a silver lining.
Thank you for the detailed update, and no worries about the delay — we appreciate the additional context.
Since the Nucleus isn’t showing the expected diagnostic text over HDMI and isn’t appearing on the network, we need to determine whether it’s failing to boot at all or simply failing to reach your LAN.
Could you please try the following and let us know the results:
Connect the Nucleus directly to a standard computer monitor or TV, avoiding the AVR entirely.
Some AVRs don’t pass through the low-resolution diagnostic output correctly.
Power the Nucleus on while directly connected and observe whether any text appears on the screen.
If you see text, please send us a photo.
If the screen remains completely blank, that points to a hardware-level boot failure.
If you haven’t already, please try accessing the WebUI once more from another device on your network: http://nucleus.local/
or
the last known IP (if available).
Given the recent power instability and the fact that the Nucleus hasn’t checked in with our servers for several weeks, the HDMI output is our most reliable way to determine what’s happening internally.
Please share a photo or description of whatever appears on the screen after following the steps above — even “no signal” is useful information
We’re here and will continue investigating with you.
Cyclone passed and power on after 2 days. No magic working when everything restarted.
Today my IT guy tried to locate the Roon Nucleus + on my system and could not find it anywhere.
He then connected Roon by HDMI to monitor and no response at all, blank screen.
Looked inside and disconnected and reconnected flash RAM (?) and still nothing.
My IT guys firmly believes the main part of Roon is dead though interface with ethernet still has the lights showing when plugged in.
I have had this Roon Nucleus + from March 2021. My first Roon Nucleus I had from Jan 2019 to Feb 2021 (when it stopped working), before that I started with Roon on my home computer. I treat all of my equipment well and they are in ventilated spaces.
While I am disappointed in the hardware performance of the 2 x Nucleus, the Roon software is fantastic.
I am going to give the Roon One a go. I don’t believe my uses justify the jump to Roon Titan though I don’t like the idea of a fan.
Thanks for the report, and I’m sorry to hear you’ve hit some hardware issues with your Nucleus. The best next step here is to get in touch with our RMA department directly, as they’re in charge of all hardware-related Nucleus issues. To do so, open the Typeform link below and select ‘Other’ followed by 'This issue is related to a physical component".
