# Repaired Nucleus No Longer Recognizes NAD M33 as Roon Ready

**URL:** <https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271>\
**Category:** Nucleus Support\
**Created:** [December 18, 2021, 9:58pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271 "2021-12-18T21:58:16Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Fink](https://community.roonlabs.com/letter_avatar/mark_fink/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Fink](https://community.roonlabs.com/u/Mark_Fink)\
**Post date:** [December 18, 2021, 9:58pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/1 "2021-12-18T21:58:16Z")

</div>

Nucleus -Rev B (Serial #54B2038B9DA2)  
Connected directly to Orbi Mesh Router via ethernet  
approximately 20,000 songs on internal storage  
connected wirelessly to NAD M33, Bluesound Pulse Bar, Bluesound Node 2

I just received a Nucleus that was repaired after some problems with its Roon Server. I connected the repaired unit to my system, and it updated its software, however, the Roon software no longer recognizes my NAD M33 amplifier as ROON Ready. Roon will no longer play on this device except through Airplay. How do I fix this? [@support](https://community.roonlabs.com/groups/support)

---

<div class="post-metadata">

**Author:** ![Jim\_F](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jim_f/32/306918_2.png) [@Jim\_F](https://community.roonlabs.com/u/Jim_F)\
**Post date:** [December 18, 2021, 10:11pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/2 "2021-12-18T22:11:41Z")

</div>

Is that device on the current Roon list of Roon Ready devices?

---

<div class="post-metadata">

**Author:** ![Mark\_Fink](https://community.roonlabs.com/letter_avatar/mark_fink/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Fink](https://community.roonlabs.com/u/Mark_Fink)\
**Post date:** [December 18, 2021, 10:39pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/3 "2021-12-18T22:39:21Z")

</div>

Yes. It was fully functional when I sent the Nucleus in for repair.

---

<div class="post-metadata">

**Author:** ![AceRimmer](https://community.roonlabs.com/user_avatar/community.roonlabs.com/acerimmer/32/367705_2.png) [@AceRimmer](https://community.roonlabs.com/u/AceRimmer)\
**Post date:** [December 18, 2021, 11:26pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/4 "2021-12-18T23:26:15Z")

</div>

Is it possible it now shows up as a different device in settings:audio and needs enabling now?  
Could you post a screenshot of your settings: audio page?

---

<div class="post-metadata">

**Author:** ![Jim\_F](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jim_f/32/306918_2.png) [@Jim\_F](https://community.roonlabs.com/u/Jim_F)\
**Post date:** [December 18, 2021, 11:45pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/5 "2021-12-18T23:45:51Z")

</div>

I was thinking about this. Was this resolved?

[https://community.roonlabs.com/t/nad-m33-certification/125789?page=2](https://community.roonlabs.com/t/nad-m33-certification/125789?page=2)

---

<div class="post-metadata">

**Author:** ![Mark\_Fink](https://community.roonlabs.com/letter_avatar/mark_fink/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Fink](https://community.roonlabs.com/u/Mark_Fink)\
**Post date:** [December 18, 2021, 11:47pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/6 "2021-12-18T23:47:11Z")

</div>

Does not show up as a new device. I have a screenshot of the audio settings below.

 ![image](https://roon-community-uploads.s3.amazonaws.com/original/3X/b/d/bdb5c925d5929a87aa72e173cf2fe1c4f9e80bd1.png)

---

<div class="post-metadata">

**Author:** ![Mark\_Fink](https://community.roonlabs.com/letter_avatar/mark_fink/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Fink](https://community.roonlabs.com/u/Mark_Fink)\
**Post date:** [December 18, 2021, 11:49pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/7 "2021-12-18T23:49:26Z")

</div>

![image](https://roon-community-uploads.s3.amazonaws.com/original/3X/d/3/d3d363d399ab443771ce570b831a860dc511632c.png)

---

<div class="post-metadata">

**Author:** ![AceRimmer](https://community.roonlabs.com/user_avatar/community.roonlabs.com/acerimmer/32/367705_2.png) [@AceRimmer](https://community.roonlabs.com/u/AceRimmer)\
**Post date:** [December 18, 2021, 11:55pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/8 "2021-12-18T23:55:59Z")

</div>

Have you tried a reboot of the NAD?  
Not many ideas after that I am afraid though.  
How are you connected to the M33?  
Is it just on the network or did you use HDMI from the nucleus to it?

If on the network, can you " see" the M33 via a browser if you type in it’s IP address?

---

<div class="post-metadata">

**Author:** ![Jim\_F](https://community.roonlabs.com/user_avatar/community.roonlabs.com/jim_f/32/306918_2.png) [@Jim\_F](https://community.roonlabs.com/u/Jim_F)\
**Post date:** [December 18, 2021, 11:57pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/9 "2021-12-18T23:57:13Z")

</div>

I’m just wondering if this was one of the devices that lost it’s “Roon Ready” status because it wasn’t yet actually “Roon Ready.” Some of those devices continued to work until a Roon update was done.

I may be confusing the issue, but just raising that as a possible reason for your issue. Maybe it’s been resolved by now. IDK.

---

<div class="post-metadata">

**Author:** ![Mark\_Fink](https://community.roonlabs.com/letter_avatar/mark_fink/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Fink](https://community.roonlabs.com/u/Mark_Fink)\
**Post date:** [December 19, 2021, 12:32am UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/10 "2021-12-19T00:32:40Z")

</div>

I rebooted the NAD and the device appeared in the Roon Ready category of the Audio section. I enabled it and the amplifier is working fine with Roon. Thank you @The Hammer for the advice.

---

<div class="post-metadata">

**Author:** ![Mark\_Fink](https://community.roonlabs.com/letter_avatar/mark_fink/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Fink](https://community.roonlabs.com/u/Mark_Fink)\
**Post date:** [December 19, 2021, 12:39am UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/11 "2021-12-19T00:39:38Z")

</div>

@Jim_F This was originally a unit that was decertified during the “great decertification”. Since I had bought the unit before the decertification date, I was allowed to continue to use Roon as a developer. Eventually, when the unit was granted its eventual certification, a software update granted its ultimate status. I don’t think that this was the issue with this case. It appears that the reboot of the NAD reestablished a “handshake” with the Roon Core.

---

<div class="post-metadata">

**Author:** ![AceRimmer](https://community.roonlabs.com/user_avatar/community.roonlabs.com/acerimmer/32/367705_2.png) [@AceRimmer](https://community.roonlabs.com/u/AceRimmer)\
**Post date:** [December 19, 2021, 12:39am UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/12 "2021-12-19T00:39:41Z")

</div>

Excellent news!  
Enjoy your music now!  
👍

---

<div class="post-metadata">

**Author:** ![system](https://roon-community-uploads.s3.amazonaws.com/original/3X/d/e/deefbd9083c99c82bbf2dd3f873f52a49f5db881.png) [@system](https://community.roonlabs.com/u/system)\
**Post date:** [December 22, 2021, 5:38pm UTC](https://community.roonlabs.com/t/repaired-nucleus-no-longer-recognizes-nad-m33-as-roon-ready/182271/13 "2021-12-22T17:38:30Z")

</div>

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