This Public Beta marks a major milestone in our mission: bit-perfect audio from source to any remote. Achieving this has required deep technical rework across the entire system. From A2DP fidelity and metadata-only modes to full plugin compliance under Debian Bookworm, the migration has been deliberate, exhaustive, and focused on performance without compromise.
All plugins are manually reviewed. Only plugins that fully meet Bookworm compatibility standards - including updated node requirements and functional parity - are included below. Others remain pending migration by their respective maintainers.
Plugin Compatibility Table
This table reflects the current status as of June 29, 2025. If a plugin is missing or listed incorrectly, maintainers are encouraged to submit updates through the designated channel.
Plugin Name
Bookworm Version
Migration Status
Deletion
80s80s
2.0.4
Migrated
RoonBridge
2.0.0
Migrated
Systeminfo
3.0.8
Migrated
ampswitch
Not Migrated - Owner has not migrated this plugin yet
audiophonics_evosabre
2.0.1
Migrated
audiophonicsonoff
2.0.5
Migrated
autostart
4.0.4
Migrated
backup_restore
1.7.4
Migrated
bandcamp
2.0.0
Migrated
calmradio
2.2.4
Migrated
controradio
2.0.0
Migrated
dmd2_music
2.1.3
Migrated
example_plugin
1.0.0
Migrated
ferrum_streaming_control_technology
1.0.1
Migrated
fusion
2.0.74
Migrated
gpio-buttons
1.8.4
Migrated
gpio_control
2.0.11
Migrated
hifiberry_dsp
Not Migrated - Owner has not migrated this plugin yet
i2samp
Not Migrated - Owner has not migrated this plugin yet
ir_controller
3.4.13
Migrated
jellyfin
2.0.0
Migrated
jellyfin_server
2.0.0
Migrated
lastfm
2.5.6
Migrated
lmsde
Not Migrated – Owner has not migrated this plugin yet
lyrion
1.0.0
Migrated
minidlna
4.1.12
Migrated
mixcloud
2.0.0
Migrated
moosbox
2.0.0
Migrated
motherearthradio
1.3.0
Migrated
mpd_oled
2.1.3
Migrated
mpdoutput
2.0.5
Migrated
music_services_shield
2.3.1
Migrated
myb
2.0.3
Migrated
now_playing
1.0.2
Migrated
onkyo_control
Not Migrated – Owner has not migrated this plugin yet
pandora
3.13.1
Migrated
peppymeterbasic
1.0.3
Migrated
peppyspectrum
1.0.35
Migrated
personal_radio
2.3.0
Migrated
pirateaudio
Not Migrated – Owner has not migrated this plugin yet
podcast
3.2.1
Migrated
radio357
2.0.2
Migrated
radio_paradise
2.0.13
Migrated
randomizer
4.1.2
Migrated
remotepi
3.2.2
Migrated
rotaryencoder2
2.1.23
Migrated
scheduledrestart
0.9.0
Migrated
serialampcontroller
2.7.1
Migrated
shairport-sync
Not Migrated - Owner has not migrated this plugin yet
I’m not sure if this is placed correctly in this thread.
As written in this post, one of my rotary encoders has stopped to work properly.
I’m using “rotary encoder II” module which works perfectly until including 4.005.
Today I have double checked if I’m not facing hardware issues:
Using a differend SD card with 4.005 or even the stable release the encoder hardware works properly.
Now in the beta release rotation on the first encoder needs tons of movement to produce a single event.
Rotation signals (A/B) are connected to GPIO 22 and 27 in my installation.
Functionality-wise the rotation of this encoder is connected to volume up/down - which works if connected to the second decoder. Also switching the GPIOs to the consecutive other encoder switches the error, so from my view signals from the GPIO 22/27 are not read properly.
Any hint/advise would be great.
As said initially I’m not sure if this is a module or a system issue (I would tend to the latter …) but I give it a try here in the module section.
If ever possible I would try to avoid using other GPIOs because HW is build up complicated and this would cause huge effort to re-assemble…
While adjusting settings for Now Playing plugin, it crashed the display system when saving. The Pi was still accessible thru the web, so I pulled this log.
Thanks for sharing the log. Based on your message, it looks like you adjusted settings in the Now Playing plugin, which resulted in the display system freeze (likely the DSI framebuffer or Chromium layer), but the backend remained responsive via web. There is no crash state in the logs present.
From your log:
Yes, I can confirm multiple npm install actions occurred, likely tied to plugin setup or config changes.
However, there is no evidence of a volumio vrestart, volumio vrestart nowplaying, or full reboot, which are necessary to reinitialize Chromium and related display modules after plugin installs or major UI changes.
On Pi5 with a DSI screen (especially 480x1920, non-standard aspect), the Now Playing plugin must be restarted cleanly to ensure Electron/Chromium picks up the correct rotation and resolution parameters. Skipping this restart can leave the screen in a blank or crashed state.
Let me know if restart resolves it or the display freeze persists after clean restart.
Downloaded and re-flashed beta 4.010 after in-place update failed (duh ): Hotspot worked right away. Plugins Youtube, Now Playing and System Info also work fine. Pandora 3.12.1, however, doesn’t work (for me at least) despite being listed as being updated. Gives me this error screen
even after I put in my credentials and saved. The credentials work fine with the 3.xx stable versions.
[Edited to correct my earlier post referencing Buster rather than Bookworm]
This plugin wasn’t migrated to Bookworm. I contacted @truckershitch and he has migrated it (very quickly, I may add ) but it is not yet available in the plugin repository. I downloaded it from his github repository (instructions here) and confirm that it works with the latest beta 4.0.13 released yesterday.
There are no plans for a Buster release on the 4.xxx series - it’s intended for Bookworm, judging by the related plugin discussions. I’ll follow up and validate the plugin migration status accordingly.
My bad I meant Bookworm, not Buster. I’ve been testing with the Bookworm beta over last month and asked @truckershitch to test and migrate the Pandora plugin for that.
Not Migrated - Owner has not migrated this plugin yet
):
) but it is not yet available in the plugin repository. I downloaded it from his github repository (