I’ve seen an occasional problem where an endpoint doesn’t show up in roon after a power off / on cycle.
I saw one on my Pi2Design AES endpoint this morning.
This is feedback from when it didn’t show up: b0e5f5044d05aeb8
And after a reboot when it did: 378853596dad6adf
My Ropieee devices are attached to a remote controlled power switch which switches them off overnight (and when we’re out), and power them on in the morning (and when we get home).
@spockfish you’re likely buried with other things - but would be very grateful for you thoughts when you get some time!
Another case in case it’s helpful - 0b09e37588bfa628
Does the endpoint come up with an IP, but not detect a DAC (which means it doesn’t show up in Roon)¿
Yes, ropieee is fine - but roon doesn’t find the HAT / endpoint.
A reboot fixes it.
In the Ropieee endpoint, if you go to the audio tab it will tell you what USB device is detected (if any). I’m not sure if it tells you anything about the HAT detection though (i.e. I think it just shows the configuration not the success/failure).
My guess is that the DAC takes a bit longer to wake (on a cold start) than the newer low-latency kernels used by ropieee. But that’s a total guess.
I’m pretty sure that’s pure ‘luck’.
Your logs show the HAT initialized, but RAAT (Roon) shows an error when accessing it.
On RoPieee the ‘hifiberry’ HAT is configured when selecting the Pi2Design AES. I also see people using the ‘Allo Digione’ as HAT. Can you try that?
Thanks
Thanks @spockfish - will try that.
Hi @spockfish I changed the driver to the Allo one as you suggested - but just had another case of the pi2AES endpoint not comming up in roon.
Feedback is here: b20adadca1540fe2
As before a reboot appears to fix it.
Same story: Roon can’t open the device. I’m slowly starting to suspect the HAT…
Do you think it could be some sort of timing race condition?
I can work round it if needed. My endpoints are turned on via home assistant - so I can turn them off and on again if they don’t come up properly in roon.
Well, on software level not. The HAT is actually recognized, it’s just that there’s an error message when opening the device.
One more thing: probably unrelated, but I also see some network issues and timeouts occurring. Does that ring a bell?
The endpoint is connected over Ethernet to a switch, and core is connected to a router attached to the same switch. So I wouldn’t expect to see lan issues between the two.
Internet / DNS is via a wifi mesh - so that isn’t 100% reliable.
@spockfish just noticed what looks like the same issue with a different zone.
This one has a DigiOne HAT
This is from when the roon zone didn’t appear.
5f09d3aa895df7d8
And this is after a reboot when it showed up fine
8d09736f8237d1a3
I should perhaps say I’m likely stress testing this code because I turn all my Ropieee zones off overnight / when no-one is in the house, and turn then on in the morning / when people get home.
I would not call that stressing… It should just work.
The logs show the same: when it does not work there’s an error in RAAT (Roon) saying that it can’t open the device. However, the audio device is properly initialized and present.
There is one thing I noticed however… I looked only into the audio stuff, but this time I spend a little bit more time in comparing the logs. And I’ve noticed that you, next to a wired connection, also have wireless enabled. The unit is however not capable of building up a wireless connection (don’t know why exactly).
Just to be sure and rule out anything else: can you please disable wireless on the unit?
If this results in the same error again I think we need to discuss this with the Roon team as it is RAAT that reports an error (and also does not try again, which I find strange as well).
Thanks
Thanks for your help.
Have disabled WiFi (and checked the rest of my endpoints have it disabled).
@spockfish this went wrong quite quickly - the endpoint didn’t come up after a reboot. There was a ‘device not found’ error showing in soon (I hadn’t noticed this before - will check next time). So looks like it doesn’t need a cold reboot to reproduce (assuming it’s the same issue).
As usual a reboot brought it back.
This is before 36d8083466b30f6e
And this is after c64b65b3699e5fa1
@spockfish please discuss the problem with the Roon team. It’s not resolved for the long time and was reported several times.
Excuse me? Are you going to tell me how I should spend my time?
Of course not! How you choose to spend your time is entirely up to you. I kindly ask you to fix a repeatedly reported issue. It seems to me that, as the author of the software, you are the right person to address this. Error-free software is more likely to receive funding.