Endpoint No Longer Shows In Settings > Audio

Hi all,

I am just back from a 2 week vacation during which I had my 2 endpoints powered down. When I powered them up I got an update notice and installed the update. Now one of the endpoints (“monk.local”) is no longer available in Settings > Audio. It continues to show up in Settings > About though (see screenshots)

Things I tried:

  1. Re-build database (by removing the “Roon” folder and restarting)
  2. Restart Roon, the Mini, the router and the endpoints
  3. Turn “Local Network” off and back on

Core:

  • Mac Mini M1 (2020)
  • Mac OS Sequoia 15.1.1
  • Roon 2.0 (build 1496)

Remotes:

Endpoint “Monk”:

  • RoPieee 2025.01 (2077) STABLE
  • Running on Raspberry Pi 4 Model B Rev 1.4#
  • With HiFiBerry Digi2 Pro hat
  • Wired ethernet connection to TP-Link AV2000 Powerline Adapter
  • http://monk.local
  • Static IP

Endpoint “Evans”:

  • RoPieee 2025.01 (2077) STABLE
  • Running on Raspberry Pi 4 Model B Rev 1.2#
  • with HiFiBerry Digi+ Pro hat
  • Wired ethernet connection to TP-Link AXE5400 Tri-Band WiFi 6E Router
  • http://evans.local
  • Static IP

Network:

  • TP-Link AXE5400 Tri-Band WiFi 6E Router

Library:

  • Tidal

Can you send me feedback of Monk?

8e951e3aab843d17

One other thing to note that may or may not be related:
For the last 6 months or so, “monk.local” web UI was only reachable using the IP (instead of the domain name). All my attempts to fix this didn’t work but the endpoint otherwise worked fine so I moved on. After the last 2 weeks powered down and the update I can reach it again using “monk.local”

Your logs show a problem with initialising the HAT. That results in the endpoint not showing up in Roon.

Can you make sure the physical connection is ok?

Thank you. I disconnected my endpoint, opened the case, ensured that the hat was seated properly (it was), re-connected everything and the problem persists. Can this sort of error be caused by something other than hardware problems?

Were software is involved it can always be software as well :wink:

But on a more serious note: if that’s the case then it’s in the kernel (driver) and the responsibility of the hardware vendor in question (Hifiberry in your case).

I did a quick internet search, and upon this error message in the past the Hifiberry response was: “send us the device because we think something is wrong”.

Could you please send me the exact error message and whatever else I might want to pass along to HifiBerry - thank you!

I replaced my HifiBerry Digi2 Pro hat and now the endpoint is working again. Apparently the old hat had died.

Cheers & thanks for your help!
Ingo

1 Like