[PLUGIN] MPD OLED - installation & configuration plugin

[Zhapox]

Hi Adrian,
I tinkered around a bit more and found out that this issue somehow doesn’t seem to exist with the actual plugin version 1.1.3 from the plugin store. The problem is that I was only able to get it work once, playing an entire album without scrolling. After another reboot though I get again the alsa error again. I guess there is still no fix around for this?

Thanks!

Kevin

[Adrii]

Hi Kevin

I think it is the same binary in both cases, so stange that one should have the scroll issue and the other not.

I haven’t had time to do any testing yet, but I did remember that when I added in the scroll reset I tested it by using the same command to set a visible vertical offset in order to show that the reset code was working. Anyway, I will retest to confirm this.

Adrian.

[supercrab]

The mpd_oled plugin always downloads and installs the latest mpd_oled binary, so I’m not sure why you’re getting different results, it should be the same executable.

wget -N http://pitastic.com/mpd_oled/packages/mpd_oled_volumio_install_latest.sh
sudo bash mpd_oled_volumio_install_latest.sh

[Zhapox]

I recently switched from an RPi 3B to an RPi 4B. Would that make a difference? I’d guess not?

I’ll run another test with the mpd_oled binary and let you know.

[supercrab]

I don’t think so, but anything is possible!

[Zhapox]

Sooo… I reflashed the system, installed the binary and after 4 hours of playback, also one or two reboots in between: No more scrolling. Don’t know what’s different apart from a new Pi 4B.

Thanks anyway!

[supercrab]

I think it might have been fairies! Glad it’s sorted though!

[Wheaten]

Tinkerbell is back again?

[Adrii]

Great that it is sorted!

[vmartell]

Still running a Sabre 9023, Raspac Audiophonics kit on a Pi 3B - still does what I want!

Have been resigned to have the Winstar OLED not working, but every once in a while I check.

1. Does the MPD OLED screen plugin support the Raspdac/Sabre 9023/Winstar kit? Should it be working? If so, then I have a broken component? If not has anyone made work those screens in the latest versions of Volumio - I found some instructions but they are bit old and they rely on a Python library, “moment” that does not build on the volumio version I am using (latest downloadable as of yesterday, can’t remember the version)

2. What would be a CATASTROPHE would be Volumio not supporting the Audiophonics ON/OFF pluging - I can live with no display, BUT TO HAVE A PERMANENTLY BLINKING light on the front panel would be madenning - if that happens would be sad to ditch the Raspdac and would probably ditch Volumio along with it.
   Who can we write to implore to NEVER stop including that plugin?

Thanks!

[supercrab]

1. I had a look and it looks like it uses the WEH001602A - Character OLED Display. This display only supports 16 characters x 2 lines and mpd_oled will not work with this type of character display.
2. Not sure what you are asking. I think you want to control an LED? Is that correct? If so have a look at my other plugin gpio_control?

Cheers

[vmartell]

Thanks for your reply! My second point was kind of unrelated, just happy that the switch works. Basically talking about this

Aluminium Push Button and Pre-Welded Connector with Blue Light Circle Ø19mm...

It is included in the Raspdac kit and I am glad the the Audiophonics On Off plugin supports it. I was, kind of jokingly, kind of serious, asking who do I have to talk to to make sure is supported continuously so I can keep using my Raspdac kit - because when is not handled, the switch has a LED that flashes… and is annoying - that is all! Like I said, not related to the thread, but decided to put it out there.

[Gelo5]

New software - new problems. Mpdoled does not show “spectrum”. Other information is shown. Tested on RPi4 and RPi5. System 3.799. My question: is it possible to set the display in the plugin:
1.spectrum only
2.standard as current
3.time and data only (no spectrum)?
Regards
Grzegorz

[Gelo5]

Thread dead?

I’ll ask one more thing: does the VCC and GND power supply have to be from the Raspberry? Can it be powered separately from a power supply?

[Wheaten]

@Gelo5

I have worked on the MPD_OLED dev branch to make this working. Meaning you need to program/build it manually and configure everything from the shell. However it’s not working anymore on the updated versions of Volumio. Due to lack of time I haven’t dig into it anymore.

Screenshots:

DEV: [PLUGIN] MPD_OLED for x86 based systems

@balbuze Just tested it on the main branch for the rpi and it works. Depending on the content of status.txt, it draws one of these screens. 0 = Full CAVA 1 = Default screen 2 = Clock 3 = Blank [image]

Modified source files:

[PLUGIN] MPD OLED - installation & configuration plugin

You need to add parameters to the mpd_oled setup screen, config in order to accomplish this. As not everyone want this. An you’re no longer in line with source code, so you need to keep updating this. Stop mpd_oled generates the clock screen, so you need to break in there as well. doable but not an easy fix. main.ccp & display_info_h. src.zip (9.3 KB) The logic is basically in here, but it’s the dev branch, using different display drivers. Only the setting is stored in a separate file, so i…

You don’t need to power it from the rPi, but I would advise against a separate power supply.

[Gelo5]

Thank you very much, I can always count on you.
Regards

[Wheaten]

The basic does work, however the service doesn’t properly initiate, need to manually stop and start it after boot in order for alsa pipe picks it up. It’s all trial and error.
Status is used to set the display by rotary switch of push button.

Status=0:

Status=1:

Status=2:

Status=3:

[Gelo5]

@Wheaten

…the service doesn’t properly initiate, need to manually stop and start it…

The original plugin works the same way

[supercrab]

@Gelo5 Remove the plugin and try using the non plugin approach. The code is available for you to change too.

GitHub - antiprism/mpd_oled: MPD, Volumio, RuneAudio and Moode OLED status and...

[Wheaten]

Not sure that will help.
Having the same issue with the manual (dev) install.
The service will start mpd_oled, but it won’t react to the state of volumio.
If I stop the service and run from the shell it works, so really confused why. as the service has the same command.:
/usr/local/bin/mpd_oled -b 32 -g 1 -P s -L t -o SH1106,128X64,I2C

@Gelo5

Please try the following, which solved my problem:
sudo mpd_oled_service_edit

replace:

[Unit]
Description=MPD OLED Display

[Service]
ExecStartPre=/usr/local/bin/mpd_oled_launch_test
ExecStart=/usr/bin/mpd_oled_launch /usr/bin/mpd_oled -o 0 -b 21 -g 1 -f 15

[Install]
WantedBy=multi-user.target

with: Only add ( su volumio -c '<your string>')

[Unit]
Description=MPD OLED Display

[Service]
ExecStartPre=/usr/local/bin/mpd_oled_launch_test
ExecStart=su volumio -c '/usr/bin/mpd_oled_launch /usr/bin/mpd_oled -o 0 -b 21 -g 1 -f 15'

[Install]
WantedBy=multi-user.target

press ctrl+o, Enter, ctrl+x

Stop MPD_OLED:
sudo systemctl stop mpd_oled
Start MPD_OLED:
sudo systemctl start mpd_oled
Check if it is running:
sudo systemctl status mpd_oled

volumio@rpi4-ws1280:~$ sudo systemctl status mpd_oled
● mpd_oled.service - MPD OLED Display
   Loaded: loaded (/etc/systemd/system/mpd_oled.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2025-04-08 12:09:32 CEST; 1min 20s ago
  Process: 3388 ExecStartPre=/usr/local/bin/mpd_oled_launch_test (code=exited, status=0/SUCCESS)
 Main PID: 3389 (su)
    Tasks: 0 (limit: 4915)
   CGroup: /system.slice/mpd_oled.service
           ‣ 3389 /bin/su volumio -c /usr/local/bin/mpd_oled -b 32 -g 1 -P s -L t -o SH1106,128X64,I2C,rotation=2

Apr 08 12:09:32 rpi4-ws1280 systemd[1]: Starting MPD OLED Display...
Apr 08 12:09:32 rpi4-ws1280 systemd[1]: Started MPD OLED Display.
Apr 08 12:09:32 rpi4-ws1280 su[3389]: (to volumio) root on none
Apr 08 12:09:32 rpi4-ws1280 su[3389]: pam_unix(su:session): session opened for user volumio by (uid=0)