Remote Console Error loading the WebAssembly

[Service-1 (Hanspeter Fluder)]

New installation CerboGX and GX Touch 70 try to login to the remote console receive the message
Error loading the WebAssembly

[Olexabdr]

I have the same problem

[nickdb (Nick)]

What version? Can you share any more details?
Really difficult to help with so little info.

[Olexabdr]

V 3.53
I try update to beta.
And download again 3.53.
But still have problem.

[Olexabdr]

Old interface work normal, but when i switch to new in vrm. I must go 20 km in objekt for switch in old interface.

[derk]

Same problem

[peregrines (Felix)]

Same problem here… really annoying. Venus OS Large Functions and VRM are not reachable!

Also getting this message sometimes:

[peregrines (Felix)]

[Slawa19 (Slawa)]

I fixed the issue by enabling Remote Support (Settings - General)

[stefan123456]

I have the same Problem. I suspect the tool “dbus-serial-battery”.
if i reinstall the tool after changing the config, it tells that it is installing QML files for GUI V2.
Is anyone of you using dbus-serial-battery?

[StefanJ]

Hi.
Also I run bus-serial -battery. I have not been able to get VRM Remote Console to work on version 3.55, although fresh install and although I run on Victron hardware. But both beta versions 3.59 and 3.60 work fine.

[PVHase (Frohmut Hoffmann)]

I had the same problem after reinstalling VenusOS on the RPi. I also use SerialBattery. The Venus firmware is v3.64 large. For me, the solution was simpler than expected: I simply logged out of vrm.victronenergy.com and logged back in. After that, the RemoteConsole and olso NodeRed were accessible again .

[clintos (Clint)]

This is caused by the serialbattery modification. Serialbattery installs UI mods by default. Once installed, it appears you can’t access the remote console because (what looks like) a sum in the URL no longer matches.

If you used enable.sh, immediately run custom-gui-uninstall.sh to remove overlays while leaving the service running.

Don’t run enable.sh. Instead, just supervise the service:

• Create the service link: /service/dbus-blebattery.0 → /data/apps/dbus-serialbattery/service

• Start it: svc -u /service/dbus-blebattery.0

[tgsail1]

This was spot on. The simplest solution was to simply comment out the custom-gui-install.sh line in enable.sh. Everything seems great now, including no BLE errors. Also the GUI mod appears to have been related to displaying individual cell voltages.

[mr-manuel (Manuel)]

Since the hash of the WASM file is different you need to enable full VRM access and remote support, so that VRM can download the modified WASM. This will be changed once plugins are fully supported in GUIv2.