It took a little bit longer then expected, but here’s 2024.12!
This release is pretty big, but nothing stands out: a nice combo of some new features (mainly display related), and a few fixes all over the place.
Especially the bug on the Pi Zero and Compute Module was challenging (difficult to reproduce amongst others), so I’m happy with having that one squashed.
As usual you can find everything you need on https://ropieee.org, but here’s the changelog for completeness:
NEW: support reverse proxying RoPieee’s webpage
NEW: [display] continue on ‘Connection Failure’ screen
NEW: [display] zone selection on ‘Zone Not Found’ screen
IMPROVEMENT: change Usbridge kernel to 64 bit
IMPROVEMENT: update Linux kernel
IMPROVEMENT: update Librespot component (Spotify)
IMPROVEMENT: update HQPlayer NAA component
FIX: sometimes RoPieee on a Compute Module and Zero 2 W fails to boot
FIX: handle S24_LE format properly on some SPDIF HATs
FIX: some Hifiberry DAC HATs are not compatible with the Pi 5
The update will appear on your Pi over the coming hours.
@spockfish Oddly with this new release, it’s not playing well with my pfSense DHCP reservation for it. With an identical MAC address as I have statically mapped, it picked up an IP address in my open range rather than the static mapping. I’ve switched to a static IP address within the RoPieee device (matching what the reservation should be) for now but I wanted to share this. Odd behavior that I’ve never seen before.
Updating from 2024.11 (1931) [BETA] to RoPieee 2024.12 (1991) [STABLE] on my Pi Zero 2 W was successful.
Raspberry Pi Zero 2 W Rev 1.0
RoPieee 2024.12 (1991) [STABLE]
Internal Wi-Fi
Apple, Inc. USB-C to 3.5mm Headphone Jack A
Roon 2.0.43/2.0.44, Plexamp 4.11.2, AirPlay 1 (Forced)
Approximate time to update: 7 minutes
Anyone having issues with HQ Player and the most recent update of RoPieee? Not sure this is the issue, but the problem did start after updating RoPieee.
I have not looked at my issue closely but I have rebooted and and other RoPieee points are working fine. It starts up no error messages indicates wit will start playing and then does not. I am using iancanada’s stack configuration with an IS2 connection to my DAC.
Same situation here.
Updated PI4 with wired network, does not work with OPNSense kea dhcp, does not get reserved address.
Update PI3 with wireless, does get reserved address.
Something is strange here. (pFsense and OPNSense are basically the same, what dhcp are you using on your pFsense? Kea?)
I traced the dhcp-traffic while setting ropieee back to dhcp, unfortunately could not replicate the issue. Which is basically good, no issue in ropieee!
Sidenote to others, kea dhcp is meant to be a replacement for isc dhcp due isc being eol’d in near future as I understand it. Still somewhat buggy sometimes
