Release 2025.01

New Year, new RoPieee release!

This release has changes all over the place. Most prominent one is the work on the display, where support for Roon’s volume limits has been implemented.

The other change that stands out is the ‘survive hostname change’. The ‘hostname’ was still a rather technical computer term, so that has been changed to ‘device name’. And furthermore the webpage will ‘survive’ a hostname/device name change, because it navigates to a URL that is indepedant of the hostname.

For most this is trivial, but I often got questions from first-time users that run into the issue that they don’t realize they need to navigate to the ‘new_hostname.local’ address.

So, I’m pretty happy with this release; I hope you are/will be too :wink:

Here’s the changelog:

  • NEW: survive hostname change from webpage
  • NEW: install update from display
  • NEW: [display] implement Roon volume limits
  • IMPROVEMENT: update Linux kernel
  • IMPROVEMENT: update Plexamp component
  • IMPROVEMENT: update Shairport-Sync component (Airplay)
  • ENHANCEMENT: update Squeezelite (LMS) component
  • IMPROVEMENT: automagically switch to HTPDATE if NTPDATE keeps failing
  • IMPROVEMENT: webpage has it’s own ‘donate’ page
  • FIX: [display] volume slider initial position is not correct
  • FIX: increase network online time-out

Enjoy and have a great weekend!

17 Likes

Just updated a Rasp4 with HifiBerry DAC2 HD

Will do the Allo tomorrow

A great thank you, all good

1 Like

Got the update, choose to install, but after reboot it shows 2024.12 version.
How to get again the update?

All good here Harry, thank you for the hard work and vibes.

1 Like

Just updated two RPi4’s and I see my allo USBridge Signature updated automatically at 3:00 am this morning. Glad to see my old allo bridge is able to accept this release.

1 Like

Allo USBridge all Ok :+1:

Dear @spockfish :

Updating from 2024.12 (1991) [STABLE] to 2025.01 (2074) [STABLE] on my Pi Zero 2 W was successful.

Raspberry Pi Zero 2 W Rev 1.0
RoPieee 2025.01 (2074) [STABLE]
Internal Wi-Fi
Apple, Inc. USB-C to 3.5mm Headphone Jack A
Roon 2.0.45, Plexamp 4.11.5, AirPlay 1 (Forced)
Approximate time to update: 7 minutes

Best regards to you in the New Year,

RU

Hi @spockfish,

Thanks for adding the volume limits! It was all too easy to drag it to 0dB in the past.

I have two Ropieee Touch units. One of them upgraded successfully to 2025.01, but the other one failed in the middle. It boots up on the old version 2024.12 (1994), but doesn’t start the GUI. It works as an endpoint though. Rebooting doesn’t fix the problem. I’m hoping the web GUI will prompt me for the upgrade again. If it doesn’t I may have to re-flash the card with 2025.01. Any other way to rescue it?

Same issue here…

Well, I’m interested in why the upgrade failed (because it means the unit did a role back).
Can you send me feedback? I’m pretty sure that a reflash is the way, but I’m interested in knowing why.

Thanks

Sorry I re-flashed with 2025.01.

My Unit:

Hardware: Raspberry Pi 4 Model B Rev. 1.5
RAM: 4 GB
ROM: 32GB microSD Samsung
Network: WiFi
Audio: USB DAC → Yamaha R-N1000
Display: No
Remote: OSMC

Works well!

1 Like

Since this update neither Spotify Connect or Plexamp have worked. RoPieee shows as a destination on both phone apps but playback doesn’t start when I click play.

I have grabbed a new claim code for Plexamp just in case, but no improvement. When I access the Plexamp page from ropieee.local I can browse the collection but nothing plays.

I have power cycled the Pi and my network router with no improvement.

Feedback 2bad46fd95729b5b

Thanks.

EDIT : Same issue with uPNP Bridge mode - must be connectivity related ?

Well,

Your logs show that the audio device is locked. I presume you’re trying to use the services at the same time, but that won’t work.

My suggestion: focus on one service when debugging. And in this case I would start with Spotify.
Disable the rest, try to use Spotify. If that still does not work, send me feedback (with only Spotify enabled).

Thanks

OK thanks, Harry.

I set the Audio Output on the Plexamp and DLNA service to off (I assume this is what you mean by disable).

Configuration applied and then rebooted the Pi. Spotify Connect worked correctly from my Android phone app.

I then set Plexamp back to HAT output, reconfigured and rebooted.
Plexamp worked correctly from my Android phone app.

I made sure to redirect Plexamp back to the phone before I tried again with Spotify, which worked fine.

I’m not sure how I got into the locked state before and why a full reboot didn’t cure it. I’ll be sure to make sure I bring the stream back my phone before swapping services unless there is a better way to prevent this lock in the future?

Thanks again.

1 Like

HTPDATE fallback working just fine !

1 Like

Recalls me something :wink: