New to Raspberry PI and Ropieee, but just bought my first RPI with screen and managed to install the beta without any problems. So far so good and great stuff - many thanks
Just one question. Is there a way to set a fixed IP-address instead of using dhcp?
Once again, many thanks for the hard work put into this.
RoPieee does not support fixed IP, only DHCP.
But my RoPieee endpoints kept their IP since day 1 without any intervention.
You can assign a fixed IP based on MAC address, keeping the RPi on DHCP though.
Just reserve the IP address in your router. In some routers you can just select it on a list and others you will manually have to type in the MAC address.
Iām not sure what you mean with the hyphens and spacesā¦
Are you talking about the zone names? Because that accepts hypens and spaces.
The hostname not because the standard doesnāt allow it, but the hostname is also not something the user sees or uses.
I must have been trying to set the hostname to something like āKitchen-Piā when trying to set the zone to something like āKitchen Monitorā and gotten confused on what was actually causing the error. I am sorry about that.
Regarding hostnames, what standard are you referring to? RFC952 allows ā-ā, but I am not an expert in these things. As you say, it doesnāt matter, as long as I setup the DHCP reservation correctly.
Regarding showing up as an endpoint in Roon, @wizardofoz, I (incorrectly) expected it to show up without a powered DAC attached, similar to how my Roon Core does.
Finally, I wonder if there is a typo on the commit screen: should āRone Zoneā be āRoon Zoneā?
I must have been trying to set the hostname to something like āKitchen-Piā when trying to set the zone to something like āKitchen Monitorā and gotten confused on what was actually causing the error. I am sorry about that.
No worries!
Regarding hostnames, what standard are you referring to? RFC952 allows ā-ā, but I am not an expert in these things
Youāre absolutely right. Iāll fix that.
Finally, I wonder if there is a typo on the commit screen: should āRone Zoneā be āRoon Zoneā?
Yes! Iām refactoring the web page from RoPieee and just spotted it myself the other day
After 30 minutes or so of music playing, Iām losing covert art.
Changing albums doesnāt fix it, restarting the extension doesnāt fix it, rebooting the Roon Core doesnāt fix it - only rebooting Ropieee fixes it.
Is this something structural? As in: I can repeat this?
Iāll try to see if I can put some debug information for this in the app and provide an update later so we can investigate.
I just had flashing, like the square around cover art and the buttons were flashing. Now itās all gone blank. Eep. Music uninterrupted. Just touchscreen issue.
Again restarting the roon extension doesnāt fix it - only rebooting Ropieee does for me.
@spockfish , weāve encountered the blank image problem a few times. Interestingly, it didnāt happen for perhaps 7-9 hours of classical āradioā this morning / afternoon, with some long works, but then it occurred after only a few hours of early jazz during dinner (2-5 minute pieces, with a new cover every time). It is almost as though an array ran out of memory.
Iāve lost all use of the touch screen too, but Iāve not had it for a week or so.
Iāve three pis running the beta, all reporting different Linux release numbers. Oddly the one which ROON recognises the extension hasnāt even got a touch screen, but the one that does, cannot force a refresh of the extension, the latest reports 4.9.36.1 while the one with touch screen read 4.9.34.1. The ROON extention is listed as being 3.50.
Could someone remind me what Which Roon Zone should the touchscreen control. Make sure you type it exactly as known in Roon. means.