New recent issue with a Cerbo GX V2. I’ve had this running for several month on my bench testing a new configuration. Connected to Wi-Fi no problem and have been able to do OTA updates to the firmware and some packages. Recently I noticed I was unable to update firmware OTA. Upon further review I have found that the wifi is unable to obtain a network gateway address. It appears as 3 dashes.
I googled and the response was the usual… reboot, update firmware, give it a static IP, go manual IP, forget network plus a few others. I’ve tried all of that, and have updated and down graded the firmware via USB stick (v3.66 –> v3.67 –> v3.65).
I have reverted to Manual IP Configuration, and I can access the unit locally, but still unable to update OTA or update packages. Additionally, there is not connection to the VRM. Obviously, the unit is unable to get out beyond the local network.
Last recommended step is to factory reset and start from scratch. Before wiping and starting over, anybody seeing this and have a fix?
The other option mentioned was this is possibly a hardware issue on the Cerbo itself?
Additionally, I have attempted to connected it to a cellular Wi-Fi hotspot on my phone to eliminate the local network as an issue, but unable to get it to connect. Very flakey behavior. keyboard doesn’t pop up when attempting to add a password, wont remember the password once entered and doesn’t solve getting it on a network.
DNS server is being pointed at a dual PiHole installation. Nothing new there, has been working like this since new. However, I did suspend the Piholes (revert it back to what you would suspect 192.168.1.1), and no change observed.
Additionally, attempted to connect to a cellular hotspot to eliminate local network issues. That was even worse. Could not get anything to “automatically” connect or populate, and the interface was not correct (I did not get the keyboard to display).
The Ethernet port is connected to a Raymarine MFD to support the Marine GX Integration - Its working as expected.
The VE CAN 2 is setup to connect to the Marine NEMA2000 network and is also up and running as expected.
I have a second Cerbo GX V1 installation running remotely with no issues and was able to update that unit to the latest firmware no issues…so at this point I’m suspecting some type of hardware issue specific to the Wi-Fi on this unit only.
This fixed the issue with the Wi-Fi. I am doing an OTA update back to v3.67. That is working.
I’ll reattempt connection over ethernet to the MFD after that, but I hope I dont have to choose 1 or the other…that MFD connection is main access point to the system/boat.
In an earlier version of Venus.os, you could use both interfaces without 0.0.0.0. With the new firmware this is no longer possible.
Please check whether the time is consistently correct in this configuration. After prolonged operation, it becomes inaccurate or displays random values. Presumably, the NTP server cannot be reached consistently.
The new set up is going to replace the old set up and its on a boat, so a number of the network connections get turned off/reset on a fairly regular basis. That may alleviate some of the issues.
