BETA Release 2025.01

OK I just blew the 8GB card away and put a 32GB in… so should all be good now just waiting for the beta notification to come in…

its been 24 hours or so now and still no beta update

abf412baf488a7bd

What do you mean? You are running the latest beta…

Oh I think I know maybe what happened - I hadn’t updated the devices page but said beta as that’s the version option, but the date was different. Otherwise I need more coffee or a nap :face_with_hand_over_mouth: :man_facepalming:

1 Like

How do I get the update?

Morning!

I’ve pushed out another beta release, hopefully the last one before we release.
This one only contains a new kernel and some last minute cleanups.
I would love to have some confirms on NAA and Plex.

Thanks!

1 Like

Oh thank you @spockfish about NTP failing handling. Donation following. I’ll switch to beta to see if it work

So I just upgraded to 2025.1. But I have issues. Ropieee seems to works as the Display was not here . Here is a screenshot

Also, issue identifier 97c71bccd7d244b1

NB : At the point of the screenshot/id, the Web interface says it is always in 2024.12. But upgrade process is blocked at the point of the screenshot.

I’m not sure that I understand you. The screenshot shows RoPieee in operational mode, nothing blocking. So what am I missing?

You’re also not running the latest beta, but a stable version.

What is missing is the display ! Normally, I switch to zone display (cover, title etc…) . As I said, the update process stalled at this point, and 2025 has not kicked in. I reverted to stable channel, and I have the Display back.

And as I said: the update process is not stalled. The update process to beta has never started.
Yeah there’s an issue with the display, but no, it is not related to the beta.

Thanks Harry I have 4 devices updated with no issues.
Played music on two of them already (using NAA) and no issues here that I can see.
I also just played a track via PlexAmp and all good there as well.

1 Like

I clicked on “update” and “reboot”. I cannot do more for updating. I reverted to STABLE, and now all is OK and I have the Display. I’ll see for NTP in the next stable version :wink:

That means that you only switched to the beta channel (and back to stable). The actual pulling in of the update, and subsequently the updating process itself never took place. Pulling in an update after changing the channel will take a few hours and requires a confirmation to be given in the web interface.

Anyways, you changed the update channel. That triggers a configure, and during that process for some unknown reason to me (at least for now :wink: ), it disabled the screen.

Three units updated fine here.

Two RPi4s are on RoPieee 2025.01 (2045) [BETA]. Kernel version: 6.6.69-SPCKFSH-v8+
One RPi3B is on RoPieee 2025.01 (2042) [BETA]. Kernel version: 6.6.69-SPCKFSH-v7+

Unit 1

  • Hardware : Raspberry Pi 4 Model B Rev 1.5
  • Network : ethernet
  • Audio : USB Inmotion Air
  • Display : No
  • Remote : No

Unit 2

  • Hardware : Raspberry Pi 4 Model B Rev 1.5
  • Network : ethernet
  • Audio : USB to Schiit Fulla/UE boom 2
  • Display : No
  • Remote : No

Unit 3

  • Hardware : Raspberry Pi 3 Model B Rev 1.2
  • Network : ethernet
  • Audio : digi+ pro hat optical and coax to KEF LS50W and Schiit Yggdrasil
  • Display : Yes
  • Remote : OSMC
1 Like

latest beta (2045) all good here :+1:
pi4 model b rev1.4, 8gb memory, 16gb disk
wifi network, no remote, no display
allo digione spdif hat
roon, airplay2, plexamp

1 Like

:+1:

RoPieee 2025.01 (2045) [BETA]
Hardware: Raspberry Pi 4 Model B Rev 1.4; 4GB RAM, 16GB disk
Network: wired ethernet
Audio: USB DAC (TEAC) — Roon RAAT, Spotify Connect, Squeezelite
Display: no
Remote: Flirc — Roon RAAT only

1 Like

:+1:
5 RPIs updated. All went fine.
Thank you Harry.

1 Like

Goodmorning guys,

I’ve just pushed out another beta. @Johnny_Ooooops ran into an issue with the last version and I wanted to fix that. So no functional changes what so ever, but some robustness work.

Thanks

2 Likes

I had the “update available” message with the beta, clicked on it, seen Roopiee doing some stuff on the display, and clicked on “reboot” in the web interface. After the reboot, no display. No more “update” message in this state, in which I have done the report identifier (but maybe one again if I had waited one hour or two ?). I have not just switched the update channel. And just switching update channel does not explain Display disparition/restoration.

Anyways, thank you for this new beta, and all good improvements. Donation sent.

Then I’m seriously wondering if your SD card is burnt.