WiiM Ultra Firmware v5.2.813259 - Apr 8, 2026

Please review the WiiM Ultra update release notes below. If you encounter any issues, feel free to reach out to us. This firmware update is being rolled out in stages, with devices updating sequentially over the next few days.

5.2.813259 (In Progress)​

Release date:

Apr 8, 2026

Highlights:

1. Sub & Main Speaker Sync: Automatically aligns subwoofer and main speakers for improved timing at the listening position.
2. Per-Input Screen Control: Enable or disable the screen display for each input mode.
3. Headphone EQ: Added independent EQ for headphone output optimization.
4. Standby Source Mode: Automatically switch to a selected input when entering standby, enabling instant playback.
5. Spotify Smart Play: Resume your latest listening session with a single tap.
6. Surround Setup: Simplified setup with full backward compatibility. (requires upcoming app update).

Screen:

1. Playback Screen: Added a vinyl-style playback screen for a more immersive experience.
2. Localization: Added French language support.

Playback & Audio:

1. Playback Latency: Reduced delay when starting playback.
2. EQ: Improved responsiveness when adjusting and switching EQ settings.
3. Line In: Fixed distortion during extended playback sessions.
4. Bass Output: Fixed low bass levels for Apple TV (Dolby 5.1).
5. Audio Sync: Improved sync accuracy at microsecond level for better group playback (requires upcoming app update).

Radio & Streaming Services:

1. TIDAL Connect: Upgraded SDK to resolve unexpected playback interruptions.
2. Soundtrack: Updated SDK for improved playback stability and performance.
3. TuneIn: Fixed playback issues for certain stations and improved resume behavior after long pauses.
4. Deezer: Fixed unexpected playback interruptions.

General Improvements:

1. Wi-Fi: Improved network stability and enhanced compatibility with Wi-Fi 7 routers.
2. HDMI ARC: Disabling automatic audio output now correctly keeps WiiM in standby and defaults to the TV speakers.
3. HTTP Server: Improved concurrency and stability under high load.
4. Audio Input: Fixed playback crash issues.
5. Remote: Fixed occasional disconnection and unexpected max volume issues.
6. Alarm: Fixed incorrect alarm and preset volume behavior.
7. Roon: Fixed occasional crash issues.
8. EQ: Enables EQ for Dolby 5.1 playback.
9. Alarm: Fixes BBC and vTuner alarms defaulting to the chime.
10. Spectrum Display: Improves dynamic visualization.
11. Qobuz Connect: Fixed occasional playback stopping issues.

 

[Saponetto]

I gave up trying to understand it too.
Anyway, this delay switch thing is something I'll appreciate for sure.

 

[hipoagumol]

Same but I don't care as I t does what I want it to

I hope so...still waiting it for the HDMI handling... Now all of a sudden is like it was released 2 days ago ?! when I've been waiting for it more than 10 days...don't really know what is going on.

 

[QuarryHunslet]

I hope so...still waiting it for the HDMI handling... Now all of a sudden is like it was released 2 days ago ?! when I've been waiting for it more than 10 days...don't really know what is going on.

The firmware version, and release date have been revised.

 

[Skull]

I hope so...still waiting it for the HDMI handling... Now all of a sudden is like it was released 2 days ago ?! when I've been waiting for it more than 10 days...don't really know what is going on.

Don't use hdmi and tbh most of the updates for the past months are not useful to me anyway
Just hoping that anything that is important to me isn't broken by them

 

[Wiimer]

View attachment 36547
It's a bit confusing as it states both

At least in the beta version, you can't set a time period.
Maybe this feature will be added in a future app update.

 

[Burnside]

Ugh, wait. Wasn't this firmware released on April 2nd or maybe even earlier? I didnt receive that one... first post is March 28th announcing a firmware with release Apr 8th..kind of confused now..still on 5.2.809035

It's not unusual for this to happen and it's down to the phased rollout approach as outlined here. It looks like some issues may have been encountered at the start of the initial rollout, so WiiM paused that, addressed the issues (hopefully ) and superseded that version with this new one. Unless you're urgently waiting on a fix and support told you it's in the next release, I don't see it as anything to fret about.

 

[hipoagumol]

I understand the phased rollout.
But it is confusing they announce a firmware, they don't finish the rollout and in the middle they come up with a new firmware build and re-write the release date and all is kept in the same forum thread.
If firmware released on March has been "killed" in the middle of rollout and a new one is born with another build number (and another build date) then just open a new thread...

 

[Burnside]

Yeah, they could do that, but I guess like me they also subscribe to the line in the excellent Jackson Browne track "These Days" where he sings "Please don't confront me with my failures / I had not forgotten them".

 

[harkpabst]

If firmware released on March has been "killed" in the middle of rollout and a new one is born with another build number (and another build date) then just open a new thread...

I see where you're coming from, but this could be just as confusing. Why keep information on firmware versions that haven't really been rolled out (except to a handful of users)?

Once this has happened (and it can and will happen occasionally) there's no "clean" way out of it. The release is in the wild, but only to be withdrawn and replaced with a new version. And this new version will usually not bring any new features, just fixes (unless someone forgot to include a promised feature).

 

[QuarryHunslet]

I see where you're coming from, but this could be just as confusing. Why keep information on firmware versions that haven't really been rolled out (except to a handful of users)?

Once this has happened (and it can and will happen occasionally) there's no "clean" way out of it. The release is in the wild, but only to be withdrawn and replaced with a new version. And this new version will usually not bring any new features, just fixes (unless someone forgot to include a promised feature).

This third version contains a few new general improvements.

 

[harkpabst]

This third version contains a few new general improvements.

Yes, but unless someone had received the original version it's not clear if these improvements are really new or if it's just a documentation update.

 

[hgo58]

At least in the beta version, you can't set a time period.
Maybe this feature will be added in a future app update.
View attachment 36550

If you turn Automatic Updates off, you can set the delay.

So you cannot turn it off completely, just for some months.

 

[Wiimer]

If you turn Automatic Updates off, you can set the delay.

So you cannot turn it off completely, just for some months.

Thanks. I didn't realize because I'd never turned it off before.

 

[sNc]

Finally, HDMI issue is fixed and I can normally keep TV speakers ON whenever I want

 

[erictheperic]

Ugh, wait. Wasn't this firmware released on April 2nd or maybe even earlier? I didnt receive that one... first post is March 28th announcing a firmware with release Apr 8th..kind of confused now..still on 5.2.809035

Same here, so it's probably a bug (or a few) within the initial version, and a corrected firmware update is rolling out now.

 

[hipoagumol]

I see where you're coming from, but this could be just as confusing. Why keep information on firmware versions that haven't really been rolled out (except to a handful of users)?

Once this has happened (and it can and will happen occasionally) there's no "clean" way out of it. The release is in the wild, but only to be withdrawn and replaced with a new version. And this new version will usually not bring any new features, just fixes (unless someone forgot to include a promised feature).

If this staged rollout means a release may die before fully rolled out I would rather call it 'main firmware beta' and put it in the beta track which I and many users would happily use. Then only release it officially, announce it and open a thread once it is ready for roll out with enough confidence after the period of user testing.
I honestly see quite confusing/frustrating/illogical that an official firmware release was announced on March 28th, then I fell back from beta track to main firmware hoping to solve a problem i currently have with HDMI and on April 10th, 17 days later, me and barely no one has actually been able to downloas/use that firmware... plus in between it has been 2 times re-released with different built numbers, edited release dates and notes on the same wiim forum thread.
So do i now have to maybe wait another 1-3 weeks till this one is declared suitable for all users? I would have rather have announced it as beta, i would have happily applied or not depending on my interests/needs and then just see official release announcement on a
April 8th instead after corrections.

This is constructive criticism, don't get me wrong. I love wiim products, support and agile development. I just don't fully agree/understand some ways of working but if those are not changing I will just get used to it even if i don't like .

Regards

 

[Wiimer]

If this staged rollout means a release may die before fully rolled out I would rather call it 'main firmware beta' and put it in the beta track which I and many users would happily use. Then only release it officially, announce it and open a thread once it is ready for roll out with enough confidence after the period of user testing.

I think there’s a possibility that distribution might be suspended to urgently address an issue that arises suddenly and is unrelated to the new firmware. For example, this might be the case with Qobuz and Deezer this time. No one knows for sure, but I’m sure there’s a reason for it.

Since the team must prioritize issues that require immediate resolution, there’s absolutely no problem with the current approach. That’s my opinion.

If you just turn off Auto update, your worries might disappear.

 

[harkpabst]

@hipoagumol, I have no professional relationship with WiiM/Linkplay. I'm first and foremost a WiiM user with a little background in Hi-Fi and software engineering. So even if some think otherwise, I'm not here (let alone paid) to defend WiiM, but to help other users.

And in this case – as much as I see your point – my opinion is that there is a huge difference between releasing a beta firmware and staged rollouts. A beta firmware is expected to have shortcomings, a "general availability" release is not. Due to the countless use cases for WiiM devices out in the wild and the plethora of connected input devices, output devices, devices running the WiiM Home App and so on, sometimes errors are not detected in regular testing. This shouldn't happen, but it does.

Promoting a beta release to a public release after whatever period of time or market share is totally uncommon. It usually takes a new build for the final software, if just to make sure that the internal version numbers match the externally documented one. Degrading a public release to beta status is something unheard of and would be even more confusing.

If WiiM wouldn't even announce their firmware updates until e.g. 20 % of all devices sold have received the update, nobody would even notice this side effect of staged rollouts. I agree, the situation is not perfect. Some might prefer a certain version number to be clearly marked as withdrawn. That's certainly doable, but ... well ... it doesn't aligne with Jackson Browne ...

 

[hipoagumol]

If you just turn off Auto update, your worries might disappear

If I could ever get the new firmware!
No, my worries won't dissappear because I would still see here in the forum announced official releases that take weeks to get or even got re re-released, re-built , re-written in between. As said, in my opinion rather seen them first as betas and opt in or not, but once it is announced as official, make it truly stable and downloadable from the moment it is announced .

 

[Wiimer]

Please just imagine. If thay released the public firmware as a beta version, we’d be stuck using the beta version indefinitely.

By the time the beta version is poblic released, the next firmware update will be available as a beta version.