This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hi All,
VictronConnect v6.05 no longer connects remotely to any of the 3 installations that I manage.
Gets stuck at 40% when connecting.
This happens on both my Windows 11 laptop and my Android phone. I tried it from both my home and my office Internet connections.
Seems to be a recent regression, I vaguely remember that it worked earlier last week, I accessed a SmartSolar and a BMV-712 remotely.
Does it work for you?
There are not known issues related to remote site connections. I ran some tests and everything seems to work as expected.
Meanwhile we investigate this further, can you please try to connect again and report back if it does work now?
This morning (May 1st), two installations were still broken (stopping at 40%) but one was working. I looked at the Venus OS version and the one that was working was at 3.31 (auto updates enabled). The ones that were broken were at 3.30 (manual updates only).
So I remotely upgraded all GX devices from Venus OS v3.30 to v3.31 and now everything works again.
I can access remotely all CAN and VE.Direct devices attached to the GX Device.
One installation uses a Cerbo GX, one EasySolar II GX and one Ekrano GX.
Hi there :)
It doesn't work for me too. None of 11 CerboGX couldn't be reached via Victron Connect 6.05. Also, update check isn't possible too (see screenshot for error message). Two-way communication is enabled and all CerboGXs are running Venus OS 3.30.
Best regards,
Srđan
I works again after upgrading Venus OS from v3.30 to v3.31
VictronConnect v6.05
I can access remotely all CAN and VE.Direct devices attached to the GX Device.
I can confirm.
VC 6.05 and Cerbo with 3.30, doesn't work.
Something has changed.
And the common consensus is that if it works dont change it.
But now we must/are forced to change it because VC is updated automatically on Android and then it wont work on Venus 3.30....
And 3.31 will introduce some other quirks and so on... Vicious circle...
A possible solution is to disable auto updates on both VC and OS.
