I have two Raspberry pi 3 endpoints with the official 7 inch screen in different rooms. Roon is running on a dedicated server using the Roon rock software. Been running ropieee for ages with no problems - until a power cut last night.
Both endpoints had rebooted but stop at the “We’re ready…” message, both play music fine except that there is no album display. Tried rebooting everything including the Roon server, checked that the extensions were enabled and the audio settings are OK in Roon, downloaded ropieee and reflashed new sd cards, checked the settings again. Every time, ropiee stops at the “we’re ready…” message. On the ropieee web page, the display tab is active and I can make changes.
And now I’m out of ideas! Music flows, the screens show text only and no graphics. Am I missing something obvious?
I’ve found the issue.
I’m preparing an update that will fix this and give you your screen back.
If everyhting goes according to plan this update will be out today.
The touch screens on my two Audiophonics RaspTouch I-Sabre ES9028Q2M units are no longer working properly after RoPieee /Roon upgrades.
On my home setup it no longer shows what’s playing. It’s always ‘unknown’. Just after the last update I found the extension turned off, but turning it on made no difference. RoPiee Remote Control 0.8.3
On my work system it seems to show the first track played, but doesn’t update for other tracks.
UPDATE: I just went to Send Feedback on my home unit and noticed the Restart Roon Remote Extension button. Doing that seems to have fixed the problem. Will try it at work later.
UPDATE 2: First album finished playing. Started a new album.What’s playing details don’t update. Touch controls seem to be working okay, but details of last track of previous album still displayed. Have sent feedback 27cb41efa41f14bb
Doesn’t move on to the next album. Plus, for example, I just started playing an album on my work system. But the screen stayed on the time. When I touched it, it came up displaying the details of what I was playing yesterday, not what I just started playing.
Either something to do with the recent Roon update, or the latest RoPiee update, has introduced this problem.
I am having a similar issue. The extension seems to crash, as the display never updates either the progress or subsequent tracks or albums. If I restart the extension, the display updates but then freezes.
This is a tough one guys as this does not happen on my system. Any hints on how to reproduce it would be nice.
So @Lloyd_Borrett, this ‘does not move to the next album’ means that it doesn’t respond to touches? Or are you saying that it doesn’t even follow Roon properly?
Working on the assumption that it is network related and Roon core related, I rebooted some stuff, and that seems to have fixed the problem for now (rebooting the display had no effect before).
To be clear, in my case the display did not follow Roon.
I’ve had a rash of odd screen issues which were different on different RPi endpoints. Harry’s update solved the main one, reflashing and starting from scratch solved the second and rebooting my ROCK server solved the third! Looks like the update to the underlying OS had some very random effects!
Issue occurred again today. Music playing and the RoPieee display didn’t “wake up” (stayed showing the clock). Steps I took:
Feedback before restarting extension: 99a7c6ed72ccc535
Feedback after restarting extension: 0516c2e92ae99f02
Display showed the album art, but immediately froze (no update of timing)
Restarted NUC running ROCK. (eg not just server software)
Display works as expected. ed55284c00e78432
I wonder whether the latest Roon update is causing some issues with extensions, but I don’t know how to troubleshoot further. Music always plays fine, whether RAAT endpoints or my remaining SONOS endpoints. I have made no recent network hardware changes, and no new extensions or change of end point hardware etc, so I am unsure where to look. I record ping intervals to each endpoint every 10 minutes, and there has been no change that I can determine:
@Nathan_Wilkes, @spockfish This is probably caused by the updated transport API. In version 2 elapsed time is sent to the extension via a separate message. The extension has to be updated to support this.
