Qu Firmware v1.1.3 has now been released for Qu5/6/7 and their Dante-enabled variants, including bug fixes and improvements.
It is available to download here: https://www.allen-heath.com/resources/ - then select your Qu model from the drop down menu.
Im just gonna throw this out there, but I’m seriously disappointed in the lack of bug fixes from 1.1.2/1.1.3 considering how long it took that to come out.
It’s risky when firmware updates are not optional if using the Android app.
We should be able to pick when to install a firmware update on critical hardware - not when we arrive at a show and then find out that it won’t allow a connection.
You are getting that error because your mobile device has updated to the most recent app version which was updated for the new firmware, but the firmware on the console is not running the latest version that the app is designed to work with. This problem arises when you allow your mobile devices to automatically update the A&H apps. That’s not really a A&H problem. The “auto-update” functionality is managed by the various app “stores”, not the individual app developers.
A&H obviously has to update their apps in the app stores to correspond with all firmware updates, so if you want to manually update the console’s firmware at your discretion, you also need to make sure that your A&H apps aren’t going to auto-update. This is the only way to ensure you can manually update the app at the same time you update the firmware. (By default the apps stores are going to auto-update all installed apps). I use Android and in the Google Play App Store there is an option for each app to prevent it from auto-updating. I would be shocked if Apple doesn’t have a similar setting.
As an immediate solution you need to uninstall the “updated” app version and reinstall the app version that corresponds to the firmware version the console is using. As an Android user I could easily find the older version of the app online (using one of the trusted APK archive sites) and uninstall the “updated”/non-matching app version and then download/install the older/matching version of the app. Hopefully users of iOS/Apple products have a way to recover/install older versions of their apps too.
“You are getting that error because your mobile device has updated to the most recent app version”
Ok, I see what happened. I didn’t know the app had done that by itself.
My suggestion was the A&H app could allow doing a firmware update later rather than forcing an update to an expensive piece of audio hardware while we may be at a remote location with no internet service, or at a live show and it happens to popup and deny connecting.
I had it fully up to date and was not behind on either item except for the newest update that just came out.
“This problem arises when you allow your mobile devices to automatically update the A&H apps.
That’s not really a A&H problem”.
The menu that forces an update is from the A&H program, not from the operating system.
It’s not practical to turn off updates or cell phone data just in case 1 app might update someday and lock us out of their program.
I rebooted, tried again.
Nope, I MUST update the firmware right now or exit the program.
There was no other option in the A&H app.
I understand I could start over and try to uninstall the app assuming:
1, We have extra time at a gig to start researching APK file versions to diagnose app issues.
2. Hope that we have cell phone signal to start looking for older APK files and that we find the right one from a legitimate source.
3. We hope that the uninstall and reinstall works and retains the settings and login we had before and that an older version works with the cosole.
Each step is risky and takes time.
I suggested simply let us do the firmware update later.
For exactly the reasons you’ve outlined, we’ve always advised turning off auto-update on our apps. The app stores don’t allow us to maintain older app versions so when we issue an update, we have no choice but to update. Sometimes, the update will include improvements in the mobile app that necessitate us pushing the update in a way that breaks compatability with older firmware versions.
If you get stuck, you can always contact us in Support - on Android at least, we can provide older APK files so you can install the older version again. (This isn’t possible on iOS)
I think you misunderstand the situation. The way A&H has set up their apps prevents them from functioning when the console’s firmware version and the app’s version don’t match. There is no “just let the app connect without letting me update” option because A&H cannot guarantee that there hasn’t been any breaking changes in the firmware or app update. Therefore the app prompts you to upgrade the console firmware so that the app can connect again.
If you need to use the A&H apps (obviously the console will work just fine on the older firmware as long as you don’t need to connect the A&H apps), the ONLY options are to upgrade the firmware version or downgrade the app version so that two versions match again. Because the app stores generally don’t provide a way to “roll back” to an earlier version of an app, the easiest solution for A&H to suggest is changing the firmware version on the console. They even have set it up so that the app will handle the firmware upgrade in an effort to make this process as easy and seamless as possible.
Obviously you can always continue to use the console on the older firmware and simply not use the A&H apps. This is a situation where using the third party app Mixing Station might be an option. Generally speaking, any updates to that app are backwards compatible with older firmware versions.
“we’ve always advised turning off auto-update on our apps”
Ok, I haven’t seen that in the documentation but will make a note of it.
Rather than change app update settings or try to uninstall and locate an old version I’ll probably make sure the app works before heading to a gig now that I know it will lock out the app if the versions don’t match.
“There is no “just let the app connect without letting me update” option because A&H cannot guarantee that there hasn’t been any breaking changes in the firmware or app update.”
Ok. There probably is no guarantee either way..
I purchased Mixing Station since A&H hasn’t published a version for Windows.
That software seems to be able to do some things the official software can’t do, such as showing the full XY routing of IN’s and OUTs like the SQ consoles have.
Oddly, Mixing Station updates to new versions regularly and simply works without firmware or version warnings. It connects, updates if we want or stays on the old version.
I wondered how they are able to program in such detail and it works.
“They even have set it up so that the app will handle the firmware upgrade in an effort to make this process as easy and seamless as possible.”
That’s impressive but seems risky since portable devices doing an update onto expensive gear could have 100+ other programs from unknown sources running at the time or weak cell signal.
I presume the app does some form of MD5 or other data integrity calculation before sending a file to an active mixing console.
Thanks for the detailed response.
The question would have been shorter if the app message had said it can’t run ANY version except what matches the console.
FWIW here’s a screenshot of my Samsung Galaxy S24 Ultra, the A&H Qu Mixpad app with the 3 dots (mini menu) at the app clicked on. Highlight red circles around said 3 dots and then the check box for Auto updates, which is unchecked on mine.
I use my S24 with my Church Qu-5, as well as my iPad Air 5th Gen. Not both at the same time for me, because my sound assistant at Church uses another iPad.
The auto update bit me once too. Once only for that. And I’ve had my Qu-5 since about July 2025.
Might just be my opinion, but isn’t Mixing Station third party? Therefore they do whatever they want in updates and all that. And this whatever they do with their app shouldn’t reflect back to the mixer company such as Allen and Heath.
Yes. Not only that, but because Mixing Station supports so many different console models, the developer has to take the extra time and effort to ensure the app is backwards compatible because not every app update corresponds with a console firmware update for every supported console.
Generally speaking A&H could make their app backwards compatible, but given that they control both the app releases and the firmware releases, it seems like a waste of time and resources to do so.