I’ve got an odd one where I am seeing consistent communication errors between my Cerbo GX and EV Charger. In the last week it has started dropping comms for around 1 hour every 2 hours. When it is showing as not linked to the Cerbo, I can still access the EV Charger through its wifi portal, so it is still connected to my network.
My Cerbo is hard wired to my network, the EV Charger is only via wifi. I’ve played with my mesh wifi settings to force the charger to hook up to a single unit (in the garage with it), connect only via the 2.4ghz network.
I’ve double checked all my IP addresses as well on both Cerbo and the EV Charger.
I’m honestly not even sure where to start to try and troubleshoot it?
The problem with mesh wifi systems is one AP can have issues communicating with the others, so no matter how strong a client can connect to its local AP, overall comms are poor. They can have pretty shoddy performance when AP’s aren’t wired.
Get a utility like mtr and run it while connected to that AP to the cerbo IP it will show any packetloss. You can also do an extended ping but it doesn’t have the same detail.
That makes sense to me, more steps to run through = more chance for problems.
The one I’ve got it connected to is the ‘main’ one that has the hard wiring from it to the Cerbo (through a switch at least), does that change anything
Sometimes fixed IP’s can resolve some connectivity issues.
You can ssh to the Cerbo, from there run extended pings to the EVCS. If you see it timing out you know there are broader comms issues rather than modbus.
Static IP’s, but set at through my network settings, not the device itself. I would presume the network settings would override anyway given I’ve fixed the IP there.
How do I ping it from the Cerbo? At this exact time, it has not pinged the cerbo for ~16 minutes, but I can still login to it through the web portal from its IP address.
Noticed this thread. Not a field expert but do have experience with WiFi being disrupted by ‘new nearby WiFi devices’ or channel changes to less favourable settings. Some systems will ‘auto optimise the network settings’ at a certain interval.
Mine changed so that (one of) the APs switched to a channel overlapping with the neighbors and other non wifi 2.4 GHz protocols.
maybe run a scan and see if the channel selection is good.
(Edit) PS my EVCS is on that specific AP as well. No major issues with (vrm) data connection here.
I did a bunch of the testing, all seemed to work (though I’m no network guru). Tracing to the EV charger showed a slower first response (>200ms, one of them was even ~2000ms) than the cerbo (cerbo was <1ms)
Through all of it I stumbled across how my network was setup with Starlink. It would seem my network was setup less than optimally as Starlink wasn’t in bypass mode, and my TPLink gear was also acting as a router.
I changed Starlink to be in bypass mode, and so far today, no disconnections. Pinging to the EV Charger is a much faster response (<100ms now)
