Hey @ambetts, welcome to the community, thanks for reaching out about the Node disappearing after the update.
To get a clearer picture, a few things would help:
Is the Bluesound Node still visible anywhere in your network or Bluesound app, or is it missing there as well?
Are both the PC running Roon and the Node on the same wired network, with no separate VLANs, guest WiFi, or mesh node isolation in play?
Since this is a discovery issue, please also check whether the Node and your Roon Server are on the same subnet or IP range. We have a short guide that shows how to verify that here: How do I know my devices are on the same subnet/IP range?
With that, we’ll also want to review a fresh Roon Server diagnostic report, if you could please bring your server back online and we’ll enable auto-diagnostics. Thank you!
We have been through your server logs and there is some progress to report, though we need you to check one thing before we can call it fixed.
Your Node stopped appearing to Roon on 4 August, which lines up with the update you installed that afternoon. Since 16:27 on Friday 8 August it has been appearing again, and Roon has connected to it successfully every day since, most recently on 11 August. So the part you reported, that Roon could not see it at all, has cleared.
What we cannot tell you is whether it plays, because according to your logs nothing has been played to the Node since the end of March.
So please do this and tell us what happens: open Settings, then Audio, and confirm the Node is listed there. Then play something to it. If it plays, we are done. If it appears but will not play, tell us and we will look at that specifically, because it is a different problem from the one you reported and we would want fresh logs from the attempt.
One detail worth asking about: the Node was using a different network port when it came back, which means it had been restarted at some point. Did you reboot it, or did it take a BluOS update, around Friday 8 August? We can see that it recovered but not what fixed it, and knowing would help the next person with the same problem.
Glad to hear it, and thank you for coming back with the answer about the BluOS update. That was the missing piece: the Node picked up new firmware and restarted, which is what brought it back and why we could see it on a different network port. Useful to have confirmed, since it will help the next person who reports the same thing after an update.
The gap in playback since March is explained too, so nothing to chase there.
We will close this one off here. If the Node goes missing again, please start a new thread and link back to this one so we have the history.