Help with victron connect app

One of the recent updates to the victron connect app includes the following:

GX products:

Make possible to connect to attached products via LAN

Maybe I misunderstand what this is supposed to do. I open the victron connect app on my android phone (android 14) and see all my victron devices in the list. If I click on one of them I am connected via Bluetooth. If I disable Bluetooth on the phone, all the devices disappear except the cerbo. The only option I get by clicking on the cerbo is remote console or vrm portal. I am currently on venus 3.40. Is there a minimum Venus os version required for lan connection of GX connected devices in the app?

The new LAN access via Victron Connect is a great leap forward.
My system is on Victron Connect 6.12 and Cerbo -s GX firmware 3.52

Updated to v3.52 and it does in fact work now. Nice feature. Now if it was made possible to access the ve.bus inverter the same way that would really be valuable.

They mean: you can now access Remote Console locally on your LAN trough your GX device.

A VE.bus device is never ever able to make a direct LAN Ethernet connection because it is a complete different protocol with different voltage levels as well.

Protocol has little to do with it. Software/firmware is responsible for communicating across platforms and protocols. The gx device already handles communicating with multiple protocols. The question is wether or not Victron developers feel the time and effort required for such development is worth it, or wether they want to even make certain features available to the end user or installer. It is certainly possible though.

And there are no protocols implemented in Software/firmware ?
A bus protocol susch as VE.bus can carry a Heartbeat signal to let a inverter function properly. Ethernet can do that as well but it is not reliable enough. Adding Ethernet for simple config purpose only is possible but will add at least $50 on top of the price

I fail to see your argument here. The gx device is already capable of communicating with ve.bus for configuration purposes, as is victron connect. Victron has already opened up a few of the settings to dbus which can easily be changed via mqtt. I’m not suggesting that victron make available full configuration via lan connection, that would be near impossible to pull off and not a good idea to be that easily accessable. I’m merely suggesting the convenience of some of the settings already available via victron connect be available via lan connection.