SetupHelper on 3.50 GUI_V2

[ttraxx]

Hello.
Is there a way to run setuphelper and then remote GPIO on v3.50 on GUI_V2?

[kwindrem]

Remote GPIO is not my package but as I recall, it relies on GuiMods which enhances the gui-v1 but not gui-v2 so you would not see the additional relays and digital inputs in the GUI.

Also, PackageManager adds menus to gui-v1 but not gui-v2 so you would not be able to access those menus to manage the other packages.

I have not seen the v3.50 release so do not know if it allows switching between gui-v1 and gui-v2 like the beta versions did. If so, you can switch to gui-v1 for PackageManager and any other configuration items needed for other packages then switch back to gui-v2.

[endurance1968]

the release 3.5 is out - it would be good to fully support this as work on v1 is stopped and future is only v2.
I just switch and the only missing I found was the packagemanager menu. Using the full webbrower, far faster navigation I like V2.

since you can easily switch between the gui mods via changing the url X between 1 and 2 it is not super urgent but would be nice to adapt.
https://<your venus device IP>/gui-vX/

[ttraxx]

i d

Hello.
3,50 umí přejít na V1, ale guimody na tomto stabilním FW nefungují. Hlásí nekopletní soubory v packake manageru.
I have already modified the automation so that it does not rely on remote GPIO and sends data to tcpmodbus directly, but of course it is not visible in the GUI.

[kwindrem]

The only way to access PackageManager is to switch the GUI back to v1 which is currently possible. For things like the generator enhancements, you can switch to gui-v1 for configuration then switch back to gui-v2. But obviously the menus will be the stock gui-v2 menus without any of the GuiMods changes.

The fate of all of my packages is uncertain until there is a path to modify gui-v2.

[rholze]

Thank you very much for your help. The resolution and calibration of the touchscreen worked. Now I only have the problem that switching off the display after xx seconds does not work, and dimming does not work either. The slider does not appear in the config dialog. Do you have any ideas for this? Is there a class for this? I think these displays, or similar ones, are used more often and it would be great if they were supported directly. That would be a relief for many people. Apparently the manufacturer also uses a different driver? (http://www.lcdwiki.com/7inch_HDMI_Display-H)

I would be happy if you/someone could help me with the last few problems. Maybe I can also make a video for others?

Thanks again
Ronald

P.S. Do you know this script here: https://communityarchive.victronenergy.com/articles/43646/how-to-quickly-update-rpi-touch-screen-configurati.html

[kwindrem]

Most HDMI displays do not provide a mechanism to dim or turn off. This can often be done via the display's menu system but not remotely over HDMI. It's a limitation of the HDMI protocol unfortunately.

I forget the specifics but you can cause the screen blanking to make the screen to all black but the backlight remains on so the screen will glow.

[jdeus]

Still incompatible with v2. Is this lazyness or is this project not supported anymore ?

[kwindrem]

I will not be developing a gui-v2 interface for SetupHelper or any of my other packages. You can still access PackageManager and other packages requiring the local or remote GUI for configuration by switching to gui-v1 (aka Classic UI), then switch back to the New UI (aka gui-v2).

I will not be migrating any of the GuiMods user interface changes to the New UI. However, generator enhancements including support for an external transfer switch will still work once configured using the Classic UI even after switching back to the New UI.

[endurance1968]

I think we should be happy that this project exists and is maintained. Even though I would also like to have a v2 version.
BUT this is unpaid time invest by creators. Stating that is lazyness for me sounds like clear lack of respect. A simple question if there will be an update to v2 would have been enough.

[kwindrem]

I do not take lack of New UI support lightly. There are a number of reasons:

1. The way that the New UI is designed makes it difficult to add or modify functionality. The remote GUI is via WASM which is a single file compiled with all the functionality. This makes it impossible to merge one package with another without combining source files and recompiling. Victron and others are working on mechanisms to support some level of modification but it isn't fully in place yet.

2. Much of GuiMods already exists in the New UI. GuiMods adds dozens of numeric parameters to the display making it much more difficult to extract basic information and is generally not useful unless a problem exists. For example, knowing the exact voltage and frequency of the AC input is really only useful when it is rejected. Displaying all that numeric data also comes at a computational cost: The system responds slowly when displaying the "enhanced" overview pages.

3. The New UI uses significantly more CPU power than Classic UI and any modifications added to the system must be done carefully to avoid negatively impacting system performance.

4. GuiMods and PackageManager have taken 10 years to bring them to where they are today and much of that work would need to be undertaken again from scratch to implement in the New UI.

One good thing is that Victron has indicated they no longer have plans to eliminate the Classic UI. This was the plan for a while which would have left things like PackageManager hanging without any user interface. By keeping the Classic UI, there is still a path to use these tools even if it is a bit more clumsy.

[endurance1968]

@kwindrem thanks for this detailed clarification.

I my case I use SetupHelper "just" as installframework for e.g. BatteryAggregator (BA). I would be fine even with a version wo any GUI support. Just a cli where I can control the updates (active packages).
pulquero (BA) has adapted the install help already to use the shell only installing BA (without GUI)
I had several issues with GUIv1 as it was not working anymore - at the end I had to do a fresh install of my Ekrano and Cerbo. After starting from scratch now v1 and v2 are working in parallel.

[kwindrem]

SetupHelper started as a set of utilities to make writing install scripts for packages easier. Theses still exist and any package can be installed and uninstalled via its setup script using a command line interface.

PackageManager was added because many people without command line knowledge wanted to install GuiMods. The only interface to PackageManage is via the menus in gui-v1. However there is limited control over PackageManager by adding "flag files" to either a removable media or the package's directory or its setupOptions directory. These are detailed in the documentation included with SetupHelper.

Once PackageManager is configured, it will run faceless. For example, you can set it to automatically scan for package updates on GitHub at a desired frequiency like once a day, and then to automatically install those updates. No further action is needed.

Some package authors have built their own "blind install" mechanism that installs SetupHelper and their package from a .tgz image they provide. They then set PackageManager to download and install their package updates.

Hope that helps.