question

The GuiMods project started by adding details to the tiles in the flow page. At the time these were seen by many as critical information only available by digging into the device menus. Next was an effort to make the flow page a single page showing all status including tanks and temperatures. The result was a crowded screen with abbreviated details and compressed tiles (tanks and temps). Also response to changing pages, etc. slowed significantly.

At the same time, installers were looking to see more devices on the flow page. Enter AC and DC coupled variants of the flow page which had no detail (just total power).

While many technically oriented people can look at a number and figure out if that is a good or bad value, a better approach is to represent power graphically relative to its maximum value. I feel showing only the gauge or graph of power vs time and show the number only on a details page would be the best approach, but keeping the total power on screen isn't a bad compromise.

Even with the screen full of numbers, there was still information that was not visible without digging through menus. The details pages accessible by tapping on each tile of the flow page provided most of that missing detail. In retrospect, adding the details pages was a better solution, keeping the flow page as an overview and allowing the user to access details quickly. Moving tanks and temps to a separate page allowed more detail and also space for more devices.

gui-v2 does all these things and also provides the user with a watts/amps selection to see production and consumption in a number familiar to them. Not all "drill-down" pages have been created but eventually each tile on the flow page will have one. The drill-downs will provide breakdowns for what is shown on the overview and brief pages including AC vs DC solar production, critical and non-critical AC loads as well as other parameters (e.g, voltage and frequency). Drill-down pages provide a better view of the device/subsystem than can be provided in a small portion of the screen occupied by each tile. So ... while gui-v2 seems to be missing many things GuiMods displays on a crowded flow page, I think most will find the Overview provides useful system status with rapid access to details when they are needed.

The other three packages don't have a GUI component.

ShutdownMonitor will probably become Raspberry PI only if I keep it at all. On the PI, it can use a GPIO input to trigger the shutdown. There's also a shutdown command in the General menu but has little value on platforms like Cerbo since it eventually reboots after receiving a shutdown command.

Thank for your great and hard job all this time.

Surely gui v2 solves the shortcomings for which we installed guimods, but a new path has been opened for motorhome users. It would be great to control our heating and lights systems from the same screen, like the new development of Markus Buck (You can check it on https://youtu.be/JvIKf1ds3gI). I’m sure that many of us would be willing to pay for those new screens and control all our devices from a single screen/system. Victron should employee or collaborate with you or Marcus to make a development that would be unbeatable. Just an idea :)) 

I'm running GuiMods v10.50 with v3.40~33 firmware with no issues.

One change I made does require SetupHelper v8.x so if you are on SetupHelper v7.x or earlier that is the problem.

Otherwise I would need the logs to diagnose further. (SetupHelper ReadMe includes instructions to retrieve the logs if you don't have ssh access.)