The situation:
I have a Venus GX connected via Wifi to the local network and internet.
An EM24 Ethernet is connected to the LAN port via direct cable between both devices.
The GX receives the default gateway via DHCP over Wifi.
On the LAN subnet there is no gateway (set to 0.0.0.0).
In Venus OS v3.55 this worked perfectly.
After upgrading to Venus OS v3.60~78, routing breaks.
Connecting to the GX from within the Wifi subnet works, but from outside that subnet it doesn’t - a clear tale that the default gateway doesn’t work.
This also causes VRM connectivity to break.
I’ve set the Wifi IP to static but that only fixes the issue for a few minutes.
(re-)setting the LAN gateway to 0.0.0.0 fixes the routing, but only for a few minutes
It seems that in Venus OS 3.60 the system is prioritizing the LAN port and drops the default gateway via Wifi.
This doesn’t seem to be correct routing behavior.
For the record: this notification didn’t result from an active attempt to create the most bizarre and twisted setup
Basically it was just me grabbing spare parts off the shelf and connecting them in a strange but network-wise logical way to get a logging system at my parents’ place while they’re waiting for their digital meter.
Grid meter is a VM-3P75CT, the EM24 Ethernet is used as a PV inverter meter.
I could replace it with an ET340 over RS-485, but where’s the fun in that?
(That would also mean I’d have to a) open up the electric board again, b) wipe the GX device to flush out the old meter and c) have a less-than-pretty USB to RS-485 device dangling next to the GX )
Mine will still drop the VRM connection and fails firmware check after a reboot. #153 connection error & no route to host.
Changing the IP address of the Ethernet port restores connectivity to VRM. The GUI is usable on my local LAN even though VRM is not functioning. v3.60~83.
Very strange. It’s been happening for quite a while now, on several devices. Changing the last octet in the Ethernet IP will remedy the problem, until another reboot or firmware update. I thought changing the IP to a link-local range solved it, but it was just the change of IP that make it happen.
)
