@DrCWO wish you a great showing.
Is it safe to assume that Spotify implementation is no longer happening?
If so I will reorient myself yo using a separate rpi for playback.
Hi all and @DrCWO
I have been stuck for half a day now, as my ADI 2 DAC is no longer seen as an audio device on Roon.
My setup:
- RoonCore on a NAS Synology
- A Raspberry PI4 with rooExtend connected to my router in LAN mode, an external HDMI screen, rooADI and rooAIDJ purchased extensions.
- I usually control Roon from my MacBook through WIFI.
All was good until I removed the SD card to use another one for another purpose (not an audio purpose).
Then, starting again the PI4 with the rooExtend card that was working properly, my ADI 2 DAC is no longer seen in audio settings.
Here is what I have done so far:
- Restarting Roon no effect
- Turning RME off and on and unplugging then plugging the USB from the PI4 both have no effect.
- After revoking all my licenses, I flashed again a card with the original rooExtend image and reinstalled it.
- Significant improvement, as I now see, but only briefly, my DAC as below:
But the DAC never gets enabled and disappears after a few seconds, just before I get the Roon logo on my external screen. At this stage, switching off-on and/or disconnecting/reconnecting the DAC through USB never makes it appear again, even for a second. I need to reboot the PI4 to see it again, but just for a few seconds.
Then, in order to further investigate, I prepared a fresh SD card with ropieee (my previous system), booted from it, and then… without having to restart either Roon or the RME, the DAC appears and is enabled as usual as follows.
I would be more than happy if someone could give me some insight, as I don’t have any other idea to solve the issue for the time being.
Thanks, all !
Edit: Just install DietPi as well, and all is fine, without any restart, reboot, and so on.
Really speechless about what’s happening… 
Edit 2 May 18 th
I just restarted my PI 4 two days later, and it suggests my ADI DAC and activates it as it should have done before, even though no settings in my configuration have been changed. I don’t know why.
So I’m wondering if there’s an interaction between the rooExtend extensions during the connection process, which could result in an inability to connect to my RME DAC.
Since my PI4 sometimes has to be used for other functions with a different SD card, this is annoying.
If there is a specific procedure to follow in this case, I’d like to know what to do.
Thanks 
Edit 3 May 21st
Troubles are back again
I had to use my PI 4 for other work (boot on a separate SD card), and when back to the rooExtend SD card and booted, no more ADI DAC was enabled. Same as above.
I post a screenshot of the last logs I can see on the screen before it moves to the Roon logo.
Hope it can help to solve the issue. DietPi and ropieee are still working fine.
In addition to that I checked that moving RoonCore from my NAS to another device (Mac Desktop, MacBook or Windows) does not change anything.
Edit 4 May 22nd
Although I am not a Linux expert, I tried to look at the log provided through rooExtend at 192.168.1.xxx from my Mac but seemingly there is no useful info there.
And connecting to the Raspberry through SSH to eventually retrieve some log files obviously requires a password and is therefore not possible 
Edit 5 May 24th
Last attempt, before giving up and waiting for support after the end of Munich High End Show.
Starting again from a scratch install with a fresh new install from the Gmail repository.
I notice that the initial boot of the rooExtend is in version 3.4.0. Forcing an update, through the web interface “upgrades,” to 3.3.1 with rooExtend being stopped. After a restart and a new forced upgrade, we finally reach the latest available version, 3.4.3, but we need a manual restart as the second update does not stop rooExtend.
As far as the DAC ADI is concerned still no improvement; it is seen by Roon but fails to be enabled and then disappears from the available audio in the Roon interface.
Mac
Hi @DrCWO
I know you were busy at the Munich exhibition, but it has now been 10 days that I can’t use my rooADI extension. Could please review my post above and drive me to the solution
Thanks for your help !
Mac
I’m still in holidays in Italy. I’ll be back on Monday and get back to you.
Best DrCWO
I think I have found a line of investigation…
As I had no answer because you were busy, I switched back to ropieee for almost a month and then tried back to rooExtend this morning. And guess what? Instant connection and DAC enabled without doing anything, just booting on the SD card.
This confirms what happened in my previous attempts. (see Edits above)
So it seems there’s a minimum time during which it’s no longer possible to activate the DAC on rooExtend if you use the PI 4 for other activities and then return to RooExtend with the original SD card. I have no explanation for this, of course.
For now, I’m staying with rooExtend while waiting for further explanations/investigations.
I am not the mood to even switch the PI 4 off then on to see whether it still works and I just pray for no electricity cut
Thanks for your insight !
Hi @MacArthur,
I’m happily back from Italy holidays now.
I read all your posts with interest but it is difficult for me to diagnose without any log information. What I guess is that using the Pi with a different SD-Card will result getting a different IP and this causes the issue going back to rooExtend.
You reported that you can’t access the rooExtend Service Page with the browser any more. This means rooExtend seams to crash after booting for what reason ever.
Until now I had no customer like you using the Pi for different purposes. Believe me I’m willing to help as this may improve rooExtend. But no chance without the log. I can supply credentials for SSH access if you are educated to use it. With this I can advise you how to get the necessary log information for me.
An other strategy will be to get a second Pi for a few $$ and save your time. But please feel free to proceed how you think it’s best for you. I will try to help in any case.
Best DrCWO
A second PI 4 is already on the way, as I don’t want to fight again with my DAC connection
Maybe there was a slight misunderstanding regarding the logs. Even when enabling the DAC fails, I am still able to see the web GUI through 192.168.1.xxx. It happens that the local address changes, but I still can see everything. My comment was about the fact that no info provided by these buttons is helpful. I guess the interesting log info is somewhere else.
I would be happy to get info (PM?) on how to retrieve the useful log file(s) and return it to you.
I’ll do this as soon as I get my 2nd Pi 4, as I don’t want to jeopardize my working system for the time being.
I guess it might be useful for the community.
Thanks again for your support.
Mac
The “Show System Log” will give me the information I need.
Please try to send it to me if you encouter issues be e-mail to info@definiteaudio.de
Best DrCWO
Hi @DrCWO
Any news on when you will start work on rooIR ?
I have rooDial and rooMax, but without rooIR, I have no volume control!
As everything runs through a preamp.
We’re half way though 2025 now, so I thought I’d remind you.
I’m hoping you can find some time for this 
Let me know if you want a beta tester !
Good you remind me
This is still on my list and hopefully will come 2025. I moved last year back to Fürth and had a lot of things to do in this time.
I currently work on an update for rooPlay also affecting rooMax. This will be released next. After that rooSpot will come to finally use Roon with Spotify. I also plan to update rooDial and after all the rooIR is on my list.
Best DrCWO
Ok, thanks for the update.
Is the 2.3.2 image supposed to work on the RPi model 2B v1.1 still? The 3.4.0 is for the Model 2B V1.2 so I was thinking the 2.3.2 should work on the 1.1 but it does not. It shows up on the network but the frontend doesn’t. I tested it on two identical Model 2B v1.1 RPi’s.
I thought I’d SSH into the thing but the credentials I was suggested by our not-so-all-knowing chatGPT and Google do not work. I do like to use one of these old Pi’s for it though so … here I am asking 
Hi @M_Polak,
Raspberry 2B v1.1 has ARM v7 so the 2.3.2 should work on it. As I don’t have a 2B v1.1 I never tested but I know it works on Pi Zero W that also has ARMv7.
Please watch the LEDs after boot. What did you see?
If you mail me at info@definiteaudio.de I am willing to share the credentials but not here in the forum 
Best DrCWO
EDIT:
Just discovered that I own a Pi2B v1.1. I will check and report back 
1 Like
Ok I checked and there i an issue in the code discovering Pi B v1.1. This lead to the unpleasant situation that rooExtend did not start up 
This is not good but as I saw I had to put a lot of effort in fixing this which makes no sense for a deprecated release. It will cost me hours to fix and build a patched release.
On the other side it will cost you 50€ for e new Raspberry Pi4.
Please understand that fixing this makes no sense for me. Sorry.
Best DrCWO.
1 Like
I have to reflash rooExtend every few weeks to my RPi to use rooDial. It does not matter which RPi hardware version I use. After some weeks the software gets corrupted somehow and rooExtend do not pop up in Roon anymore. The Raspberries are always on although I do not like that at all.
Has somebody the same or similar experiences?
Did you ever try to use a new fresh SD-Card. Those cards wear out. If the Pi’s are always on this should never happen as nothing but the license cheack date is written on the SD Card.
Please nute the IPs of you PI’s and try to hoen the IP with http://[ip of rooExtend]. If this still works try to get the system log and mail it to info@definiteaudio.de
In my listening room I ran a rooExtend-Box for years and never encountered any trouble 
Best DrCWO
Unfortunately the Raspberries, it does not matter if Zero 2 W over wifi or 4 over cabled connection, disappear from network after some weeks, so there are no logs available. I have no problems with my network so far, only rooExtend is affected.
You wrote you did re-flash right?
A power on/off cycle of the Pi did not work right?
Do you run one or more rooExtend instances?
Did you ever try to use a new fresh SD-Card?
Please also send me your License keys so I can check.
Best DrCWO
Yes, reflashed several times.
A power on/off cycle helped sometimes, but at the end the extension and the PI´s network is no more working.
There is only one instance running.
I checked this with 2 SD cards.
My Ubuntu Server (Intel NUC) always shuts down at night and starts in the morning. Maybe this could be the cause for the behaviour. Maybe the Pi sends pings and freezes because it gets no response after some time. In the past I powered off the rooExtend Pi too but then the experience was even worse so it runs 24/7 now.
I would appreciate it if rooExtend could run directly on the NUC.
May come some day but not on ROCK.
I wonder if this may be the reason why. rooExtend connects to my Server checking for updates at night.
I never encountered such an issue. My rooExtend in the living room runs for a very long time now (always on) but my roon Core on a Win11 is also always on…
I fear I can’t help any more if I can’t reproduce it.