question

seb71 avatar image

Cerbo GX Remote Console connection issues after FW update to 2.62 (also in 2.63 and 2.65)

Yesterday I updated my Cerbo GX from firmware 2.60 to the newly released 2.62.


Cerbo GX is connected to my Internet router using WiFi.


Several times already (first time it happened yesterday, while looking into the Cerbo GX settings after the FW update) Cerbo GX was not accessible using Remote Console via LAN for several minutes.

After a few minutes I can access it again (without doing anything to fix the issue).


When this happens, on VRM there are no updates for a few minutes (VRM portal log interval is set at 1 minute).


Not sure if this is a WiFi issue (haven't got a chance to try it with a LAN cable since updating the FW) or if Cerbo GX freezes for a few minutes and that is why I can't access it with Remote Console over LAN.


The WiFi and Bluetooth LEDs are blinking normally even when this happens (or I did not catch them in time).


Yesterday, after the first time it did this, I did a Cerbo GX reboot (from Remote Console menus), but again it had the issue today: once when I tried Remote Console from a phone and second time when I tried from a PC (both devices were in the same LAN with Cerbo GX).


I never observed this problem with 2.60 firmware.


Anyone else has this issue after updating the firmware to 2.62?


cerbo gxfirmware updatewificonnection issue
1 comment
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

It happened again several times after I wrote the above post.


I went back to 2.60 firmware.

13 Answers
JohnC avatar image
JohnC answered ·

Hi @Seb71

I may be experiencing the same thing.

Might be wifi. I switched to ethernet and got this from the wifi screen.. 1612949935703.png

The 'Failure' thing I've never noticed before, usually says 'Connected'. Pulled the ethernet and lost it, the wifi didn't take over as it should.

I managed to revive it to 'Connected' status, then pulled the ethernet. Worked ok for a few minutes, then while scratching my head looking at it, a couple of flickers and gone again. Back to ethernet.

2.62, auto updated (whenever). Works ok on ethernet.


1612949935703.png (127.7 KiB)
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

johanc avatar image
johanc answered ·

Morning Guys

I have just installed my cerbo and had problems similar to what is described, almost as though the processor is lagging and very slow. I noticed it on the LAN network connected and slow loading times. I even lost all bluetooth connectivity, to the point where the blue LED would not even work on the cerbo and light up, even though it was enabled on the unit and the wifi side working.


I finally resolved the speed issues by resetting the unit and for some weird reason all started to work, including the bluetooth and the blue tooth LED on the cerbo. This is on version 2.62. After the reset, I had to use a PC screen and keyboard to enable bluetooth and the wifi again, but it is working well for the last 12 hours and the slow loading seems to have gone away as well. I can only currently, and within reason presume that the new 2.62 firmware is not either flashing correctly or has bugs. When I did flash to the new firmware, I had no issues and it did flash. Hope this helps a little.


Regards

Johan

2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

wkirby avatar image
wkirby answered ·

I have found that if I change to a different WiFi channel on the Access point than it solves it.
For me, CH6 has issues, if I change to CH13 (Europe), it works well.

1 comment
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

With the same WiFi channel I have no issues when using FW 2.60.

I have my WiFi router set to channel 11 (2.4GHz)

seb71 avatar image
seb71 answered ·

After reverting back to 2.60 (with which I never had this problem), yesterday I upgraded to the newly released 2.63.


Today I had the same issue again (as described in my original post).


Remote Console was not accessible on my LAN via WiFi for a few minutes.


I checked in VRM right away and I saw:

"Last updated: 7 minutes ago".


Then it started working again, without me doing anything to fix it (same as with 2.62).

2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

seb71 avatar image
seb71 answered ·

I managed to catch it again a few minutes ago.

I sent a ping request to Cerbo GX from a PC in the same LAN (while Remote Console was not accessible via WiFi).

192.168.0.171 is my Cerbo GX (via WiFi)

192.168.0.101 is the PC from where I was sending the ping request to Cerbo GX.

=======================================

Pinging 192.168.0.171 with 32 bytes of data:
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Reply from 192.168.0.101: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 192.168.0.171: bytes=32 time=7ms TTL=64
Reply from 192.168.0.171: bytes=32 time=18ms TTL=64
Reply from 192.168.0.171: bytes=32 time=19ms TTL=64
Reply from 192.168.0.171: bytes=32 time=9ms TTL=64
Reply from 192.168.0.171: bytes=32 time=5ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=4ms TTL=64
Reply from 192.168.0.171: bytes=32 time=7ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=17ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=4ms TTL=64
Reply from 192.168.0.171: bytes=32 time=12ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=4ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=22ms TTL=64
Reply from 192.168.0.171: bytes=32 time=9ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64
Reply from 192.168.0.171: bytes=32 time=34ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=5ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=3ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64
Reply from 192.168.0.171: bytes=32 time=8ms TTL=64
Reply from 192.168.0.171: bytes=32 time=13ms TTL=64
Reply from 192.168.0.171: bytes=32 time=5ms TTL=64
Reply from 192.168.0.171: bytes=32 time=1ms TTL=64
Reply from 192.168.0.171: bytes=32 time=1ms TTL=64
Reply from 192.168.0.171: bytes=32 time=110ms TTL=64
Reply from 192.168.0.171: bytes=32 time=1ms TTL=64
Reply from 192.168.0.171: bytes=32 time=7ms TTL=64
Reply from 192.168.0.171: bytes=32 time=9ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=2ms TTL=64
Reply from 192.168.0.171: bytes=32 time=9ms TTL=64
Reply from 192.168.0.171: bytes=32 time=5ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64
Reply from 192.168.0.171: bytes=32 time=6ms TTL=64

Ping statistics for 192.168.0.171:
Packets: Sent = 109, Received = 98, Lost = 11 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 110ms, Average = 7ms

=======================================


At the same time I quickly connected a LAN cable between Cerbo GX and my Internet router.

I could access the Remote Console through the LAN (UTP) cable, but just at that time I saw that the Cerbo GX WiFi recovered and I started to get replies to that ping (see above).


Nevertheless, I managed to capture this screenshot:

cerbo-gx-wifi-failure.png


As you can see, same status ("Failure") for WiFi as @JohnC had.


2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

seb71 avatar image
seb71 answered ·

And now it did it again.


It is definitively a WiFi issue.

It's not a Cerbo GX freezing issue as I wondered in my original post.


I now know this for sure because this time I already had the LAN cable plugged between Cerbo GX and my Internet router and I could access Cerbo GX via LAN cable, while could not via WiFi.


WiFi had the same "Failure" status.

Then I saw "Connection lost" status and right after that "Connected" status and Remote Console started to work again via WiFi, too.

2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

michelg avatar image
michelg answered ·

Hi Seb71 ! Stupid question, are you using a 2.4Ghz phone or a Device for Baby monitoring ? They can create interferences on the 2.4Ghz bandwith... You could check that using a laptop and see how many WiFi networks are in your area, and which canal is the less occupied, then change the router to use it, and wait a few days to see if the issue happens again or not.

Michel

1 comment
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Only a few 2,4Ghz phones.


Already selected a less busy channel (ch 11).


But I never experienced this issue with 2.60 firmware on Cerbo GX. Only with 2.62 and now with 2.63.

So it seems unlikely to be caused by radio interference.

seb71 avatar image
seb71 answered ·

And now it did it the 4th time today.

WiFi not working ("Failure" state) for about 7 minutes.


I went back to 2.60 again.

2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

JohnC avatar image
JohnC answered ·

@Seb71

I haven't seen it again, so consider the experience a one-off.

But I did note in the VenusOS changelog an entry for 2.62, "Fix connecting to another WiFi network after a failure". I take that to mean it won't now connect to another unintended one.

I'm quite remote, so never see a stray unprotected network, and my own phone is banned from such. But maybe applies to you?

2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

seb71 avatar image
seb71 answered ·

@JohnC

But do you have the LAN (UTP) cable always connected between your Cerbo GX and your Internet router (or switch)?

If your UTP cable is always connected to your Cerbo GX, it would be difficult to notice random WiFi failures.

-------

I do have other WiFi networks visible here (from neighbors). All are password protected.


-------

I bought my Cerbo GX last summer (2020), but I completed my system only at the end of November 2020.

My Cerbo GX came with 2.56 firmware (if I remember correctly) and I updated it right away to the latest available firmware at that time (which was 2.60).


Since the end of November 2020 it ran fine with 2.60, until I updated it to 2.62 (and later to 2.63).

Switching back to 2.60 always fixes this issue.


-------

Unfortunately I did not download the 2.60 firmware when it was on Victron Professional.


As you know, Victron, for some reason, does not keep old versions available for download.


I only have 2.60 in my Cerbo GX (so I can still boot it).

4 comments
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

@Seb71

My ethernet loses it's lan address daily (my fault), so I just leave it on wifi. But now that you mention it, I do use VictronConnect most days, and it sometimes needs a restart, possibly because of spotty wifi. But that's not overly common, and certainly hasn't happened more often on the newer fw.

My apologies too for not mentioning that mine's not a Cerbo, it's a CCGX. Far less powerful and with just a little Victron-sourced nano/usb hanging level with the bottom of an Easy 5000 on a shielded cable.

I tested my pings to compare with yours, and most were 1-2ms, but did crack one at 38ms. Maybe busy at that time.

I still think your issue is wifi in some way, but I can't relate my own brief experiences to fw updates..

Ah, that's why you have a different manufacturer for the wireless interface. You have a CCGX, not a Cerbo GX.

I wondered why they would use different components on a newly released product.


Regarding the ping requests, the problematic moments were those when the host was not reachable or the ping request timed out.

When there was a reply (even with higher latency), Cerbo GX was again reachable via WiFi (and Remote Console worked again).

That 'manufacturer', if you mean the Optus thingy, is just my WAN gateway, like a mini wifi hotspot, a modem/switch. Nothing to do with Victron. And why my ethernet has to come from a pc, clumsy hey.

BTW, your issue has been raised by Daniel at a higher level. No response yet, but if you can think of anything else relevant, now's the time..

Not that.

First half of a MAC address is the manufacturer (of that NIC device) identifier.

seb71 avatar image
seb71 answered ·

For comparison, this is the result after about 14 hours of ping requests (made today), when using 2.60 firmware on my Cerbo GX:

=======================================

Ping statistics for 192.168.0.171:
Packets: Sent = 49286, Received = 49231, Lost = 55 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3761ms, Average = 19ms

=======================================


ping-cerbo-gx-260-wifi.png



Those 55 lost packets were not grouped together, but like this:


request-timed-out-260-wifi.png


I also accessed Remote Console at random intervals. It always loaded right away.


2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

seb71 avatar image
seb71 answered ·

Unfortunately it still happens in 2.65. This time WiFi did not even recovered after waiting about 15-20 minutes. I had to reboot the Cerbo GX (I connected an UTP cable to have access to Remote Console).

1 comment
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

After that it happened a few more times but always recovered by itself after 7 minutes or so.


I reverted to 2.60.


I had to reconfigure the temperature sensor connected to Cerbo GX (re-enable it, change the offset and re-name it).

Mark Maritz avatar image
Mark Maritz answered ·
2 comments
2 |3000 characters needed characters left characters exceeded

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Yeah, I know about that, but:

  • I don't have a Cerbo GX display.
  • I use channel 11.
  • This issue does not happen with 2.60 firmware.


So I don't think it's the antenna.

Hey Seb, I'll contact you soon to get an engineer to see what's causing this. All the best, Matthijs