Volumio 4 for Volumio products (Motivo, Integro, Primo 2, Primo Plus, Rivo, Rivo Plus)

Wheaten · July 9, 2026, 1:52pm

These where/(still are) great devices.
Produced in the Netherlands by Siltech and serviced by NAD, in the old days.
A crime to service though due to the acrylic front plate.
Back to memory lane.

NikosR · July 10, 2026, 8:57am

One more week and the Rivo will complete one full month supposedly in V4 beta testing after the rapid fire releases for the previous devices. All this time the beta version available through the test channel has been at 4.165. Make what you want of it, since we have absolutely no update information from Volumio. In the meantime Primo V3 was made available and Ferrum announced their Volumio based streamer.

volumio · July 10, 2026, 2:50pm

Hi everyone. Just want to clarify why we are lagging a little bit behind. As you all know, our goal for this update is to give you the best possible experience. But for some heavily technical reasons, going from Volumio 3 to Volumio 4 is the most complex over-the-air update we have ever done.

So besides being very cautious in testing, we have been monitoring closely how the update behaves in the real world. What we observed is that in total, eight devices out of thousands failed to update from Volumio 3 to Volumio 4. The important thing here is why they failed. In every case it was because the power was removed mid-update. The update can take a while, in some cases more than 30 minutes, and we think some users assumed it was stuck or frozen and pulled the plug before it finished.

While eight out of thousands might seem like a small number, we don’t want to take any chances. We really believe you deserve a smooth experience, and we are fully committed to it. So we decided to pause the update for the latest two devices while we improve the process. We built a new over-the-air update that reduces the chances of breaking your device to zero, even if the power is removed mid-update. That is why it is taking a bit longer.

We are testing it right now and the results are very promising. The new update is both faster and safer. So yeah, while we know it is disappointing to wait a little longer, we hope you understand we are doing this to get it right. That is the reason for the delay, and we felt you deserved our transparency on it.

Thanks for your patience, and stay tuned.

sschot · July 10, 2026, 3:00pm

What is within Volumio 4 the number of tracks it can handle without any issue? As maximum library size is the question I mean with this.

Wheaten · July 10, 2026, 3:00pm

Hi @volumio

Thanks for the reply.

I don’t think anyone would disagree that Volumio is taking the safest approach here. It’s completely understandable that you’d rather delay a release than risk users ending up with unstable or, worse, unusable devices.

That said, I think the main concern from the community is the lack of communication around the reasons for the delay. If the decision is driven by stability, testing, or preventing issues for users, I believe most people would appreciate and understand that.

So far, the messaging has mainly been along the lines of “delayed” or “as soon as possible,” which leaves a lot open to interpretation. A bit more context and transparency would likely go a long way in managing expectations and reducing frustration.

Just my two cents.

NikosR · July 10, 2026, 3:48pm

@volumio
Thanks for the up-to-date information. This should have been done without our persistent prompting though. In any case it is good you’re trying to improve the OTA update process. I live in a place where short power outages and voltage drops are not infrequent so I was planning to connect my Rivo to my UPS when attempting the update, having read your previous warning. I will still do that despite the improved process.

volumio · July 10, 2026, 4:12pm

You’re 100% right on this. We’ll do better on communication from now on.

backenst · July 10, 2026, 5:38pm

Volumio RiVO updated to 4.156

The install process went very smoothly.
The set up process was intuitive, easy and an improvement.
Set up with Volumio Precisio was fine.
Audio up and running no issues. I use Qobuz.
My Flirc remote interface is working well.
The HDMI interface is not working - it is turned on in the Video Output options menu. All I am seeing is the prompt on the screen, although I saw all the startup Volumio logos and status when booting up so the HDMI is connected properly.
There is also no "Now Playing Plugin** available in the Plug-in store. Is that coming? It is there when I did Volumio 4 on Raspberry Pi.** Maybe its not there because the HDMI interface is not yet ready?
I lost my settings for Fusion DSP but i think that was expected.

balbuze · July 10, 2026, 7:44pm

available now!

all settings are lost with the update from Volumio3 to volumio4
But for FusionDsp, you can backup the shared folder

/INTERNAL/FusionDsp

BEFORE the update and restore it after

backenst · July 11, 2026, 1:41pm

Ok now I can no longer connect to WiFi. I can connect via Ethernet. Rivo sees my router but when I enter WiFi password it does not connect. I do have band steering enabled on my Linksys router and this worked initially and worked worh all other Volumio 4 instances using pi5. I also did a factory reset. Should I put in a ticket?

And @balbuze thank you for adding in Now Playing plugin.

Wheaten · July 11, 2026, 5:23pm

@backenst

Yes please raise a support ticket.

I own a Rivo and was involved even before the beta release.
No matter what I try, I simply can’t reproduce the issue you’re experiencing.

For context, my Rivo is part of a “mobile” setup dedicated to IEM listening. Because of that, it regularly moves around the house and connects to different Wi‑Fi networks and SSIDs without any connection issues.

I mention this because it suggests that the Rivo is generally capable of handling network changes reliably. It may be worth taking a closer look at the specific network environment, router settings, or other factors that could be contributing to the behavior you’re seeing.

backenst · July 11, 2026, 5:41pm

Thanks @Wheaten, so it must be my network which I have never had issues with before. I have been doing all kinds of troubleshooting with my Linksys mesh system to no avail. However, I may have the perfect solution. I just ordered a Linksys extender which once connected to Wi-Fi, I can ethernet directly to the Rivo and hoping that will work. If so, that will solve this problem and perhaps give me more stability. The extender is just one floor above the router so I should have a strong connection. I can report back dtomorrow. Thanks again for your commnets.

NikosR · July 12, 2026, 5:42am

@Wheaten
I may be asking the obvious but have you tried resetting your router?

backenst · July 12, 2026, 3:23pm

@NikosR I believe you meant this for me. But yes, I restarted the router, several times. I played with the band steering and other settings all to no avail. Although it did connect initially and once on the guest network,so it can do it. But alas i think I have a solution with the wifi extender and then ethernet from the extender.

backenst · July 12, 2026, 5:08pm

Update on Volumio RiVO updated to 4.156

Wifi non connect issue I added a Linksys extender and plugged ethernet from the extender to Rivo and all is good. My connection is now 1 Gb/s. If somehow the Wi-Fi resolves itself, I will continue to use this configuration as its more stable and stronger.

Volume Options I noticed in the Volume options, if you set the Volume to “None” (which I prefer because I use the Preciso to control volume) the streamer volume decreases to 41 which is strange. I know this because when I set the volume back to “Hardware,” 41 pops up on the on-screen volume wheel. Setting the startup volume to 100 does not fix it either.

The HDMI interface is not working - it is enabled in the “Video Output Options” menu. I see the Volumio splash screen and bott up on the screen, but when it normally projects the interface to the screen, I simply get the system prompt and black screen.

Otherwise, all is smoother, faster and cleaner than prior versions of Volumio.

Wheaten · July 12, 2026, 5:33pm

Wifi:
As mentioned in an earlier post, this I can’t reproduce with my system.

Volume options:
In my case the Rivo + Primo Plus as DAC. (DAC part is pretty similar to the one of the Preciso).
There is some weird behavior going on.
Rivo is normally always on “none”. After a reboot, the Volume control shows a slider. When trying to move it, it goes away.
If I try to switch to Software control, Volumio crashes (log).

After the crash we have a HW mixer available???

Setting it to “None”, Volume is 100%.

HDMI interface is not working:
This I can also reproduce. During boot the logo is visible, kiosk won’t start.
(Used HDMI 1920x440 screen. Which works fine on the Primo Plus.SBC related?)

Darmur · July 12, 2026, 5:50pm

please set the volume to HW and keep it at 100%, you won’t have any difference compared to setting it as None

backenst · July 12, 2026, 6:39pm

@Darmur Yes, that is what i did.

@Wheaten now I see your solution, so I did just that and all is fine.

Thanks to both.

Zabriskije · July 13, 2026, 6:51am

HDMI interface is not working:
This I can also reproduce. During boot the logo is visible, kiosk won’t.
(Used HDMI 1920x400 screen. Which works fine on the Primo Plus.SBC related?)

We’re already tracking it. I’ll bring it to the developers’ attention again today.

Rene · July 14, 2026, 9:50am

Starting Live Log…

 volumio : PWD=/ ; USER=root ; COMMAND=/usr/sbin/i2cdetect -y 11
pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
pam_unix(sudo:session): session closed for user root
 volumio : PWD=/ ; USER=root ; COMMAND=/bin/journalctl -p 7
pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
pam_unix(sudo:session): session closed for user root
info: Log sent successfully, reply: {"status":"OK","link":"http://logs.volumio.org/primo2rev2/uUekESU.html"}
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: VolumeController::SetAlsaVolume40
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume21
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume9
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume45
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume67
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume86
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume59
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path
info: VolumeController::SetAlsaVolume29
info: CoreStateMachine::pushState
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
info: Updating  RAAT Signal Path

log.