Roon Nucleus Acting strange after being moved to another room

Core Machine (Operating system/System info/Roon build number)

OS 1.7 Build #610

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Various Ubiquiti devices including a USG, switches of various models and a cloud key. Connection to Roon is Ethernet

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Large Mcintosh Sound system connected by

Description Of Issue

After moving the fully functioning Roon Nucleus from one room to another we have had issues with the Roon not showing up on the network for a time which we were able to fix. Now the Roon is asking us to log back into the account like its a new device BUT it is not accepting the correct account information.

Sounds like it’s not communicating with the roon servers properly.
Move it back to where it was and see if it wakes up.

Home seek maybe? :innocent:

Forgot to type the connection to the Mcintosh system is via USB.

Hi @Alexander_Spak,

Welcome to the forum!

Can you please be a bit more detailed as to how you had the Nucleus connected before and how it is connected now?

Are the switches running on the same subnet? Was the Nucleus connected to an unamanged switch before and is now being connected to a managed switch? Also, our Networking Best Practices Guide may be of help:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.