Since moving up to 6.3, We have seen a lot more trouble with firmware updates than ever before. It’s not uncommon to have the update fail, sometimes to the point we have to go back to ve.flash to get things back. I’ve also seen a refusal to update - usually “you’re on the latest” when it’s clearly not.
I also have a couple of devices where it freezes when the app is opened. If you kill it and restart it seems to come back just fine the 2nd time. This is typically on Android, but has been seen on a windows laptop too.
Matthias, We don’t get any error codes, just a failed update. Or, frequently we’ve seen machines on older firmware reporting “your unit is up to date” even when they are several updates back (I’ll get a screen shot of that next time). It was locking up initially on my phone on first load, but would load fine after I killed it and restarted, but an uninstall/re-install seems to have cured that - same symptom on a tablet in our shop, I’ll double check the re-install on that one tomorrow.
We are a service center too. Anecdotal, but we’ve noted a couple of RMA units in the last week, that were locked up, both took ve.flash to recover, but were 100% following the reflash.
guystewart
(Guy Stewart (Victron Community Manager))
4
Is this just updating the Multi/Quattro?
Or all devices?
Is it random or is it reproducible?
Have you ever made a VictronConnect service report before?
Next time it happens, could you please create one and let me know and I’ll get in touch to collect it (it contains some diagnostics from your phone so best not to post it publicly).
I came here searching for the same, although even with 6.31 or using the VRM portal, I’m unable to update my 250/100 MPPT to 3.18 from 3.16. I’ve tried dozenws of times,. and the VictronConnect Service report doesn’t hold any measurable clues either:
DEBUG 2026-03-31T08:49:32.312 [DTCUPF] Setting firmware paths took 686 ms
INFO 2026-03-31T11:04:45.796 [FM][FR] Requesting firmware version: "0x0631ff" lastModified: 1774884290
WARN 2026-03-31T11:04:45.797 [FM] CHECK FOR NEW FIRMWARE with lastModified: 1774884290
WARN 2026-03-31T13:59:41.886 [FM] Error getting remote firmware list: "Error: Host vrmapi.victronenergy.com not found"
INFO 2026-03-31T14:16:35.913 [FM][FR] Requesting firmware version: "0x0631ff" lastModified: 1774884290
WARN 2026-03-31T14:16:35.913 [FM] CHECK FOR NEW FIRMWARE with lastModified: 1774884290
INFO 2026-03-31T14:16:46.261 [FM][FR] No new firmware available
DEBUG 2026-03-31T14:16:46.261 [FM] NO NEW FIRMWARE AVAILABLE
DEBUG 2026-03-31T14:29:08.615 [VRITEM] Requesting value: "com.victronenergy.venus.ble_2_00015/FirmwareVersion"
My CerboGX units update fine, my other MPPT updates fine, but the 250/100 refuses to update at all.
I’ve tried from VC on iPad, VC on iPhone, VRM portal directly pulling the remote firmware, uploading a local copy of the firmware to the portal, or using the latest in the shared Dropbox, all fail.
I also tried a full, factory reset of the MPPT through VC, no luck.
I even tried reflashing 3.16, in the hopes that I could jump to 3.18 from there. No luck. It gets to 30%, waits about 5 minutes, then ultimately fails.
For what it’s worth, vrmapi does indeed resolve:
$ host vrmapi.victronenergy.com
vrmapi.victronenergy.com has address 18.157.127.184
vrmapi.victronenergy.com has IPv6 address 2a05:d014:509:311:71c5:cb8b:69dc:206d
So that’s not the issue. Anyone else have a method to update the firmware that will work through mobile VC or the VRM portal?
Since the Service report comes form the VictronConnect mobile app itself, how is it able to query the logs of the various devices in the Victron deployment (MPPTs, CerboGX, Inverters, etc.) in order to bring visibility to failures in firmware upgrades of those devices?
If VC says I’m on the latest firmware and VRM shows newer firmware, then it’s never going to see 3.18 as an available upgrade for the 250/100, and thus won’t ever show that in the Service report.
I need a way to see failure logs from the MPPT itself, not from VictronConnect, which doesn’t query the device logs of the MPPT.
How can I see why this firmware update is failing through VRM, when the VC app itself has no idea there are newer firmware updates available?
What exactly is your problem?
VC says you are on the latest FW but via VRM you see a newer version?
VC can only show the FW available in it’s own database.
With VC 6.30 it should also check online for updates if you are online with the device running VC.
Correct. In VRM, I see my device has v3.18 available for it. In VC, it says v3.16 is the latest, and I’m already on it. In the Dropbox firmware files, I also see a released version of v3.18 for my A115 MPPT.
None of the 3.18 versions successfully apply to the MPPT, through any means I’ve tried (VC on iPhone, VC on iPad, manual upload through VRM, remote update through VRM).
It’s the only device that remains on a 2-year old firmware, because it refuses to get past 30% before passing out and failing.
FWIW, I’m on VC 6.32 as of this morning, same results.
The latest 6.32 version of VictronConnect for desktop/Windows contains inside only the 3.16 firmware for MPPT 250/100 (0xA115).
They didn’t update VC with the latest 3.18 version for MPPT 250/100.
It is possible that the VC for MacOS to have the same issue.
Although it should look online and download the latest version of firmware files…
For example, on Windows it makes a local library with all latest firmwares.
But…
You can manually add 3.18 to VictronConnect library on the phone and then update it locally over bluetooth.
You can find the procedure in the VictronConnect manual.
I’ll try adding 3.18 to the VC library and go that route. This process shouldn’t be this fractured.
Update: Clicking “Manual Update” inside VC on the iPhone/iPad (using 6.30, 6.31 and now 6.32) does nothing except lead me to a page that says I’m already on the latest firmware.
Using VC on the Mac, clicking the same option from the same menu items as I see on the iPhone/iPad, does lead me to a file picker, which I used to get 3.18 from the Victron Dropbox, and led me to the above screenshot.
Sadly, VC on mobile devices does not allow me to add any firmware to the library. The VC running ‘natively’ on the Mac, however does, but seems to hang at 5%.
On Android there is a procedure where you keep the VC open and then switch to file explorer and tap on the firmware file.
In that moment the background VC sees that - because it is associated with those kind of firmware files - and it pops a dialog where asks you if you want to add that firmware file to its library.
From where you can manually update.
Isn’t the same on iPhone?
Since updating to 6.32, I haven’t seen any repeat issues.
guystewart
(Guy Stewart (Victron Community Manager))
19
Just to clear up the “fractured” firmware release comment from @setuid
It is intentional that firmware updates are rolled out in stages, and the final stage being the full release to all users via VictronConnect.
Prior to that firmware is often available in other channels, that usually require some manual intervention to discover and install.
This is done deliberately to help us identify any issues that might arise in the real world, outside of all the testing we do in in advance of any public release, but still can’t take into account all the different possible permutations of devices. Ideally we catch these from those ‘early adopters’ who go out of their way to update, and then report back, and can fix them before many people are affected.
It slows the process down (deliberately) and can make things confusing, but overall is a better way to reduce the number of people that might be affected by a bug in a new firmware release..
