Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SetupHelper on 3.50 GUI_V2 #101

Open
ttraxx opened this issue Oct 31, 2024 · 6 comments
Open

SetupHelper on 3.50 GUI_V2 #101

ttraxx opened this issue Oct 31, 2024 · 6 comments

Comments

@ttraxx
Copy link

ttraxx commented Oct 31, 2024

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

@kwindrem
Copy link
Owner

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
Copy link

endurance1968 commented Nov 2, 2024

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
Copy link
Author

ttraxx commented Nov 2, 2024

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
Copy link
Owner

kwindrem commented Nov 2, 2024

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
Copy link

rholze commented Nov 19, 2024

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
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants