Running allo USBridge sig. with RoPieee 2024.11 (1896) [BETA]
Everything is running fine. Thank you for your work!
1 Like
So. Yes it had shutdown instead of restarting like every other update I have done.
I put the beta on a RPi3B with a HiFiBerry DAC 2 HD HAT to get Spotify on it for my wife. Spotify connects and disconnects immediately.
If I change anything in Roon like changing the volume control from fixed to device the Pi becomes unavailable in Roon and I have to reboot it. Just opening the audio settings in Roon and cancelling make it unavailable.
Playing a song on Roon gives a ‘Failed to open the Audio device error’.
This setup was working with the stable release prior to switching it to beta. I will try a usb dac later to E it out just an issue with the hat.
Thanks
RoPieee 2024.11 (1894) [BETA]
Hardware: Raspberry Pi 4 Model B Rev 1.4; 4GB RAM, 16GB disk
Network: wired ethernet
Audio: USB DAC (TEAC) — Roon RAAT, Spotify Connect, Squeezelite
Display: no
Remote: Flirc
1 Like
Upgraded 3 x RPI3 and 2 x RPI4 to the Beta 2024.11. No issue encountered.
Thanks Harry for the updates.
Kind regards, Frank.
1 Like
DAC2HD HAT shows up in Roon but fails to play
DAC+ HAT does not show up in Roon
USB DAC works in Roon and Spotify
Dear @spockfish:
I updated RoPieee on my Pi Zero 2 W to 2024.11 (1893) [BETA] this evening, and the update appears stable for me. Listed below is what I tested.
Raspberry Pi Zero 2 W Rev 1.0
RoPieee 2024.11 (1893) [BETA]
Internal Wi-Fi
Apple, Inc. USB-C to 3.5mm Headphone Jack A
Roon 2.0.43, Plexamp, AirPlay 1 (Forced)
Please let me know if you would like me to test something for you.
Best regards,
RU
1 Like
Hi @spockfish
All well here and specifically I had been having problems on the last few betas with the connectivity on startup and this is cured in this version (your bullet point improvement 5)
My set up
Raspberry Pi 4 Model B Rev 1.5
Memory 1gb
Storage 16gb
RoPieee 2024.11 (1894) [BETA]
IQaudIO Pi-DigiAMP+
Internal Wi-Fi
Display yes
Remote OSMC
1 Like
My Unit:
Hardware: Raspberry Pi 4 Model B Rev 1.5 - 4 GB RAM - 32GB microSD
Network: WiFi
Audio: USB DAC Yamaha R-N1000
Display: No
Remote: OSMC
I had problem with update my device. Green led blinking and wrapping msg are still active without effect. So I use brute force, turn off/on the power and still nothing. I must back to last stable version.
Please send me link to Beta image. Maybe this is problem with autoupdate function?
Second think I use old etcher software from February 2024 and when I try manage stable version to sd card RoPieee starts only configuration mode. Add my WiFi and password and can’t connect to my wifi. I get last version of Etcher software from web and try again make image of stable version. Right now everything works perfect. I don’t know what is it. But now stable version works well.
There is none. If you need to reinstall then just use a stable release.
There is not, but don’t use ‘autoupdate’ when doing beta testing. It makes stuff literally ‘invisible’ and defeats the purpose of testing the installation procedure itself as well.
We misunderstood each other, I meant updating via GUI, not updating via etcher + image. I always consciously update RoPieee by GUI manual. Something went wrong here.
Harry (@spockfish), fyi - NAA 5.1.0 was recently released
edit: NAA 5.1.1 now out, with fix for some regressions.
1 Like
Hi, all works fine after update with BETA this weekend except that I had to cold restart my Raspberry Pi. After that the update finished completed nicely.
Config: Raspberry Pi 4 release B, Chord TT2 via USB. No additional board
@spockfish I will try update beta again 
Update: Ropieee dosen’t connect to WiFi and LAN after wraping. Still the same problem. What we should do with this problem?
@spockfish works well on my rpi4, i use just as NAA…Good job, as always.
1 Like
Hi,
I’ve pushed out another beta build… probably the last one before we release.
Anyways, besides an update of NAA, I’ve added functionality to the display with respect to error handling.
So, there are 2 error states possible with each having it’s own screen:
- Communication Failure
this screen is being shown if RoPieee can’t find the Roon Core server or the extension is not enabled. You can now ‘cycle through’ that screen (as with other screens) by pressing it. - Zone Not Found
this screen is being shown if everything is OK, except RoPieee cannot find the Roon zone being configured. You can now also ‘cycle through’ this screen as well, but furthermore, if RoPieee can’t find the configured zone but sees more Roon zones, it will show the possibility to select another zone. That looks like this:
So please test, and if everything is OK whe can release.
Thanks!
1 Like
There should be a new release that will fix something in a couple of days
1 Like
@spockfish
I upgraded to (1908) [BETA], and I tried the new “Zone Not Found”-screen. It works correctly here. The only minor issue is, that if one changes to a new zone, but if the new zone is not playing, the display stays on the same “Zone Not Found”-screen. Only when starting to play the new zone (not possible via the RoPieee-screen), then the screen really shows the new zone. I don’t know if it would be possible to already show the screen of the new zone, even when it is not playing already.
Thanks for this nice new feature.
Kind regards, Frank.
That’s how it supposed to work, and how it works for me …
Can you send me feedback?
@spockfish
Hi Harry.
Feedback: 9c052e0cbc1753b9
I was listening to “Living”, when , as a test, I powered of the DAC. So “Living” gave the new “Zone Not Found” screen.
Then I selected “Bureautje” as the new zone, where nothing was playing. The screen kept on the “Zone Not Found”-screen.
Kind regards, Frank.