I have Ropieee running on a Pi3. It worked great for a few months, but in recent weeks, it’ll flip back and forth between the Now Playing data, the “Connection Failure” screen.
I haven’t changed anything recently, so I’m at a loss as to what might be happening.
I’ve done the traditional troubleshooting of power cycling the box, verifying my LAN is working properly, and whatnot.
I’d love some troubleshooting advice. While I like the appliance-like nature of the Ropieee image, it’s difficult to get insight into what might be wrong. Are there logfiles available somewhere?
6d168c793f64672b Similar issue, cycling a “Connection Failure” screen every minute or so, lasting a few seconds. Playback is uninterrupted. Hardware is Pi 3, name brand SD card, Pi official touchscreen, Hifiberry Dac+ pro, all powered from USB hub, hardwired w/ cat6 to a netgear unmanaged Gb soho switch, 10m distant. Operator is SSH capable.
Well, you only have one zone in your Roon system available, called ‘Kitchen’. But you’ve configured the display to control the zone ‘Living Room’. So that won’t work.
@spockfish Firstly - Thank you for RoPieee, and thank you for taking the time to look at feedback. My system is basically working; so these are all annoyance-level concerns at worst. I’m grateful for any thoughts offered, but music is playing and I’m happy.
I’ll double check my zone configuration; I may have introduced a sampling error when I collected the debug package. I normally have 3 zones - a RoPiee as the ‘living room’, two headless DietPis as ‘kitchen’ and ‘garage’. Livingroom and Kitchen often get grouped for background listening. Maybe there’s a lingering issue with the grouping/ungrouping?
Further possibilities: I’m wondering if I have a power-quality issue; the USB hub powering ropieee is nominally rated for 3A, but may be limiting per-port current. I’m running the Pi & Dac from one port, and the touchscreen from another.
The Kitchen endpoint runs on WiFi where the others are hardwired… That’s enough layer-one difference that perhaps RAAT has complaints.
I’m having the same problem. One thing I’ve noticed is that the host name is not resolving. If I enter http://livingroom.local into a browser, it times out, but if I enter the IP address, I can access the GUI. Russian hackers?
BTW, music is playing just fine through the end point.
Again, in your log there was no LivingRoom, also not grouped. So if the configured zone is not detected then it cannot control it and shows the connection failure message.
Thanks Harry. The extension was not showing up under “Discovered Roon Extensions” but was showing up under “Authorizations”. I tried restarting Roon and Ropieee, but I was still unable to enable the extension. I restarted my computer and the router and then was able to enable the extension. Thanks for you all your help.
