question

Hello, please note 2 bugs on Cerbo UI

Hi Matthijs,

following issue was already present in previous versions, today I had time to proof the relation with GX and to confirm it also on current beta.

When overall grid solution is launched, Venus GX starts quicker than network router where GX is actually attached. Since GX obviously has also an DHCP-server included (mostlikely as a consequence of the running avahi* processes), other network devices partially retrieve from GX a network address in the 169.254.0.0 range. As a consequence local devices can't communicate between each other anymore.

Interestingly GX assigns itself one address from offical network DHCP (as configured on GX setup), but in parallel another assigned by GX itself.

Offically assigned IP:

eth0      Link encap:Ethernet  HWaddr F8:36:9B:FF:09:1B
          inet addr:172.27.27.220  Bcast:172.27.27.255  Mask:255.255.255.0
          inet6 addr: fe80::fa36:9bff:feff:91b%lo/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1450  Metric:1
          RX packets:40488 errors:0 dropped:1030 overruns:0 frame:0
          TX packets:96372 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3186316 (3.0 MiB)  TX bytes:115059375 (109.7 MiB)
          Interrupt:178

Internally assigned IP:

ll-eth0   Link encap:Ethernet  HWaddr A2:4A:4A:3F:22:D1
          inet addr:169.254.7.57  Bcast:0.0.0.0  Mask:255.255.0.0
          inet6 addr: fe80::a04a:4aff:fe3f:22d1%lo/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1450  Metric:1
          RX packets:4287 errors:0 dropped:677 overruns:0 frame:0
          TX packets:158 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:598261 (584.2 KiB)  TX bytes:56654 (55.3 KiB)

I can imagine, that the DHCP is required, when GX runs with activated Wifi-access-point option. However would it be not possible to resctrict the DHCP-function on that interface only and to ignore the LAN interface?

Cheers,
Thomas

Hi Mathijs,

I would not necessarily declare my second post about the UI beahviour on this beta as a bug. However at least the implementation is not consistent.

When entering certain menus, the most recently used submenu item is selected by default. As you can see from following illustrustration, that previously selected subitem "Details" gets selected, after having entered the BYD menu. This beahviour is actually present on all main menus except the "Settings" one.

However when selecting the "Settings" menu, this nice feature does not get applicated. After having selected the "Settings" menu, ever the first item gets selected.

Since I have to perform a lot of tests with ESS currently, it would be very helpful, if the feature that is present in other menus, would be also functional in "Settings" one.
Of course I could assume that other users would like just the opposite. Therefore I could image to offer such feature maybe as a parameter in "Display & language" section.

Cheers,
Thomas