OK, I’m lost. This device will never be used with WiFi. Why are we looking at wireless settings at all? I read that enabling Apple AirPlay on my source machine will allow me to stream to this device, but have yet to enable AirPlay on my Mac mini (where the Roon core resides). I’ve tried to follow a half-dozen sets of instructions from Google on how to enable AirPlay, but none works with my machine. I’ve an M2 Mac mini with 8Gb RAM and a 500Gb HDD. I’m running macOS Sonoma 14.5.
Thanks - Glenn
It was a typo, I am sorry. “Networking”
Edit: the issue is almost certainly networking-related, based on my understanding of the evidence.
Have you checked the webUi for the RPi to see if it is actually running RoPieee?
You can get to the WebUi by entering the IP of the device in your browser.
You can find the IP by looking in your router or by using an App like “Fing” to see what devices are on your network.
The ropieee webui looks like this:
I would check to see what version of RoPieee is running and that the Hat is selected on the Audio tab.
Also, double check the IP of the server (your MAC) and the RPi to make sure they are on the same subnet.
Thank God! We’re back to English again - LOL.
I will do two things in the morning:
Then I’ll share all with you. Thanks most kindly for the help!
It could come dislodged during transit and need reseating – this happenned to me recently. But, as I said earlier, confirm if Roon Bridge is shown under Settings > About. If it’s not, then most likely network related.
Do you mean re-flash the microSD card or something else?
Also - I’ve tried unplugging everything from the Ropieee - then attaching an HDMI cable to my TV - and then plugging the power cable into the Ropieee. Results: Absolutely nothing - no video from the Ropieee at all. Not even Linux error messages! Any ideas?
Plan B - I just plugged in an Apple TV3 to the network. Result? Seen IMMEDIATELY by Roon as a destination! Since the Apple TV-3 has an optical TOSLINK output, I’ve now got 44/16 stereo audio (all I’m really looking for). Adios, Ropieee!
This also means that ANY contemporary AVR will work fine since all of them have optical inputs!
As far as I know hdmi out is disabled in RoPieee
Can you see the power status light on the RPi (it should be on the opposite end of the device from where the ethernet connection is)? If so, when you plug in the power what does it do?
What “should” happen is the red light comes on, and the green light goes through a series of flashes while it boots up, when it is fully booted up and ropieee is running the red light should be solid and the green light should be flashing once a second.
Also, what light are showing on the ethernet connection?
Roon Bridge isn’t listed, so this indicates that the Raspberry Pi is either offline or on another subnet. Focus on resolving a networking issue.
If it were online, you’d see something like this.
PS. The 10.96.0.0 network is from a VPN … you should see the same subnet as Roon server.
All aside, download Roon Ready HiFiBerry-OS from their website, flash to the SD card, and configure via their Web interface.
This way you’ll get a true Roon Ready device.
Of course, you need to make sure it’s on the same subnet as Roon server.
Yes. It seems somewhat likely that the Raspberry Pi was configured to be on a different subnet prior, assuming that the other networking components have been checked (working Ethernet cable and switch port).
Re-installing the OS is very fast, and will default to DHCP on the networking side.
I’ve verified the Ethernet network - Plugged in an Apple TV-3 and it was instantly recognized by Roon as an endpoint. Since I’ve got a working 44/16 stereo endpoint, I’m not going any further with the Ropieee. Thank you very much for the coaching, and if anyone would like to buy a Ropieee, mine’s for sale!
At the risk of jumping into the middle of this, I have to ask what your goal was with the RaspberryPi? Like most of us we use it to stream high quality audio to an outboard DAC or an amplifier with an integrated DAC. The Apple TV is pretty limited in terms of audio. I suspect the quality is fine but according to the specs it can only support AAC or MP3. Maybe that suits you just fine, in which case I’ll mind my own business. However, I suspect getting the RPi with Ropieee up and running is as simple as reflashing the SD card with the latest image. Balena Etcher (freeware) on a laptop with an SD card reader will do the trick. No other investment required.
I am the previous owner, and I will say this is a very nice little product. I assembled it myself and had it running fine. I even tested it before I shipped it, and it worked fine. So, either it’s remembering my network (and I am 99% sure I didn’t have it set to static IP address), the OS somehow got corrupted in shipment, or perhaps as one person said - the HAT got dislodged in shipment and needs re-seated. Any of those are an easy fix.
So - if someone wants to buy it from Glenn - I will vouch for him…great guy! If not, I’ll buy it back from him.
Don’t know how anyone can be fairer than that, kudos to you @Mark_Kline .
Thank you…I really didn’t expect it to go from working to not just via shipping. But, I stand behind whatever I sell. (Which isn’t much, but…) FYI, this was a spare streamer/DAC for a 2nd headphone setup paired with a Cambridge Audio headphone amp. I just didn’t need a 2nd one.
Kudos to Mr. Kline for being a stand up kind of guy! I’m firmly convinced that there’s nothing wrong with this Ropieee that wouldn’t be fixed by updating the network info. I’d not dream of returning it to Mr. Kline, but since I now have a working alternate end point, I don’t really need the Ropieee any more.
Thanks kindly to all who have helped with this question!
