v3.75 is almost equal to v3.74. It differs in an test for production.
And restores the Wifi connection status (to be the same again as in v3.73).
This backports some fixes from the v3.80 branch:
Fix VE.Bus ESS systems sometimes remaining in bypass when combined with an external transfer switch (S99 firmware).
Fix a VE.Can issue where the address claim procedure would not complete under certain conditions (BUS-OFF), resulting in the GX no longer transmitting data on the network.
Don’t report to VRM that devices can be opened in VictronConnect if that is not supported.
One of my two Cerbo GX updated automatically to v3.74 and didn’t show actual and available WLAN-connection(s) correctly any more - unless being connected to WIFI somehow. Problem doesn’t exist with v3.73 and I was lucky to restart with the old version which was kept in memory as backup.
I can confirm that, in the list of wireless networks, the network to which the GX device is connected is shown with a disconnected status. However, the Wi-Fi connection is in fact active and operating normally.
Back to 3.55 – stable, practical, and free from unnecessary fuss.
OMG, can you release just one version without breaking something that worked in the previous one?
That’s exactly why I don’t rush to update myself, and why I don’t update my clients systems either.
So, it appears the WiFi issue is related to the v2 gui. The v1 gui shows connected to WiFi as normal, the v2 gui shows no connection. However, in the v1 gui the WiFi networks appear duplicated.
Hi @jeroen , I don’t mean to be picky, but Firmware - Victron Professional has no mention of firmware 3.74, nor 3.75, and there’s no mention of either in the change log, however, Index of /feeds/venus/release/images/einstein has 3.74, but also two versions of 3.75 and also now an incorrectly named swu of the same date and time as the second 3.75 version? Perhaps there’s still a bit of housekeeping to do?
“Hi @jeroen , I don’t mean to be picky, but Firmware - Victron Professional has no mention of firmware 3.74, nor 3.75, and there’s no mention of either in the change log, however, Index of /feeds/venus/release/images/einstein has 3.74, but also two versions of 3.75 and also now an incorrectly named swu of the same date and time as the second 3.75 version? Perhaps there’s still a bit of housekeeping to do?”
That is already done. And the professional changelog is for tomorrow.
My colleagues have already started calling me, asking what’s going on with their customers. Wherever automatic updates were enabled, the wireless connectivity has started dropping out. I suspect this is only the beginning.
Updating from 3.75 32535 to 3.75 633305 failed. Rebooted to 3.73, and did the Update again. I am happy to report the new 20260624163305 is showing the Wi-Fi network correctly as Connected.
did someone also have problems with shelly devices with authentication?
they will not work for me…
and if i disable password i can find them but not controll them. i have the shellys in different vlans as the cerbo but communication is allowd
