Problem:
Sometimes (maybe 20% of the time), I start playing an MP3 file and after maybe 30 seconds the Ropieee box appears to crash. It disappears from the Roon interface, the web interface stops responding and it no longer responds to pings.
Sometimes (inconsistent) a hard reboot will fix it, but sometimes it just happens again.
When was the last time you rebooted everything (including the core server and network)?
Is the RPi wired or wireless?
On the WebUi what does the RPi temperature look like? For reference my RPi4s run around 45-50C when idle.
If you still have issues after the above, I would go to the WebUI and from the advanced tab send feedback and then post it here so that Harry can take a look when he gets a chance.
@bearFNF Thanks for getting back to me.
I’ve definitely rebooted the core and still had the problem…but possibly not the network so will reboot everything later today.
RPi is wireless.
Current temp on that device is 51.1℃ / 123.9℉.
Worth pointing out that this issue is a degradation of a system that was rock solid until (roughly) 2 weeks or so ago.
I’ll do the ‘send feedback’ thing as well.
Thanks again.
Alex
‘Crashing’ is a confusing term. Can you access the web interface when this happens? In that case, I would love to get a feedback on that very same moment.
When it happens everything stops responding: the webui stops responding, Roon no longer knows anything about the endpoint, and it doesn’t respond to pings.
Is there anything I can do after the restart to get some logs to look at?
Ok. I’ve attached an ethernet cable so I’ll wait for it to happen again.
How do I control which interface Ropieee/Roon binds to? I was expecting to see the device listed twice in the Roon audio config so it seems to be cleverer than I am as it’s bound to the wireless interface currently…
But if you have ethernet attached you should be able to access the unit over ethernet (look in your router or connect to ‘mypi-wired.local’) and thus be able to send feedback while this is happening.
Thanks @spockfish All setup now, waiting for it to happen again.
JFYI, not sure that this relates to Ropieee at all but I can’t access (web or. ping) the wired interface by name (-wired.local), only by IP address. My nameserver (router) has a record for it and it seems to match the one for the wireless interface, but no device on my network can resolve that name. .local addresses work fine for all other devices on my network, just not that one.
same problem here. My rpi has been hard crashing. just got about 30s into a song and roon UI went int the select an endpoint mode. It’s on wifi. I’m running rock on an intel nuc wired. Can’t get to the ropieee web ui when it happens.
My Rpi is built with rpi 4, and ian canada:
#20B. TransportPi Digi,Audiophile grade master mode digi transport
#48B. PurePi II 5V+3.3V ultracapacitor/LifePO4 battery power supply combo with ultracapacitors/battery holders pre-installed
Ropiee is set for “Audio HAT” to use “HifiBerry Digi2 Pro”
It never used to be like this. It’s approaching unusable.
