Lumin T3 not detected by Nucleus on same subnet

Audio Gear Talk Lumin
1

Hi All

I suspect this is a Lumin issue rather than a Roon one, but I thought I’d post here and see if anyone spots anything I’ve missed :slight_smile:

I have a ~2022 Lumin T3 that I have been very happy with, and have had no issues until last week, when it stopped being detected by both Roon Nucleus and the Lumin App. The issue started out with intermittent / slow track updates (which I had initially blamed on a 1900 track playlist that was added to Roon at the same time the issues started - that’s another rabbit hole that I will go down separately…) ; however the issue has got steadily worse and the device is no longer detected at all by Roon, so I’m suspecting the T3 at this point.

The T3 iand Nucleus are both assigned a fixed IP address by a Unifi UDM Pro server on the same subnet as the iPad running the Lumin app; both show as connected with their respective IP addresses when I check the network dashboard, but the T3 is not detected by either the app or Nucleus, and does not respond to a ping command from both Macs and PCs on the same subnet. . The Nucleus talks fine to the IPAD, Mac Studio and a node 2i that I dragged out of the cupboard to test a non-airplay endpoint. .

The system used to work just fine with an aggregation switch, 2.5G rack switch, and a cheap 1G endpoint switch connecting both the devices together; I’ve since tried it with both a direct connection to the UDM controller and via a 10G L3 switch, but cannot get any response from the T3; the Nucleus works fine on all setups when playing to other endpoints.

Resetting the T3 requests a USB stick (which it does not detect) then appears to power up to some unknown state. The instructions make no mention of USB request step and I’ve not found any info of a download for a reset file to put on the usb stick. After all the messing around the front panel says ‘Ready for Music’ with the network cable attached, and correctly requests a network cable check when it’s disconnected, but is not reachable by and external devices.

At this point I’m suspecting a hardware issue with the T3, but would welcome any advice as to anything else to try before going back to the dealer.

Thanks in advance

David

.

2

Power cycle the whole network of devices starting from the router, including all switches.

Please try a different network cable to a different switch (or router).

Perform the hardware reset : power down the unit. Remove all USB connections. Use a pin to press and hold the reset button at the back while you power it on . Keep holding it for no less than 15 seconds, then release it.

It should not ask for USB media.

3

Hi Peter

Thank you very much for the prompt reply. To clarify my original comments, the USB file request seems to be part of a startup sequence that scrolls across the bottom of the display on the T3 during the boot process - there is no direct user prompt per se. I had already tried multiple combinations of router, switch and cables as well as rebooting all linked components in sequence.

Keeping the reset button pressed for 15 seconds was long enough to trigger a second reboot, which did fix the issue.

Best regards

It might be helpful to describe in the instructions whether this second reboot is part of the restore process, or whether there is a ‘safe’ point to release the reset button based on the info on the screen - now that it’s working again I am not keen on experimenting any further.

Thanks again for the follow up, and glad I can return the Node to the cupboard - I’d forgotten how much better the Lumin sounded :).

Best regards

David