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

Expand the VNC embedded client resolution beyond 640x480 #82

Open
marleyjaffe opened this issue Jan 15, 2021 · 3 comments
Open

Expand the VNC embedded client resolution beyond 640x480 #82

marleyjaffe opened this issue Jan 15, 2021 · 3 comments

Comments

@marleyjaffe
Copy link

marleyjaffe commented Jan 15, 2021

As mentioned in this other issue, the embedded VNC version's resolution is locked at 640x480. This really limits the functionality of the embedded VNC version as you can't really see anything in the window at that size. This fix will help users across all platforms!

#i maybe the way to go is to simply fix the VNC embedded client version and improve the resolution beyond 640x480, that way you dont need to use the OS specific client

Originally posted by @fgonza2 in #78 (comment)

@marleyjaffe marleyjaffe changed the title Fix the VNC embedded client resolution beyond 640x480 Expand the VNC embedded client resolution beyond 640x480 Jan 15, 2021
@eddyg
Copy link

eddyg commented Jan 25, 2021

I run ozw-admin in Docker (the "allinone" container) and I came up with a work-around (for the time being) the small size of the GUI.

The changes below affect both the web-based VNC client, as well as when using a "real" VNC client (like Screens, which is what I used for the screenshots).

Here's a "before" screenshot of Preferences for reference:
Screen Shot 2021-01-24 at 7 34 44 PM
I start by logging in to my OZW container:

docker exec -it openzwave /bin/bash

and then copy/pasting:

echo -n 0.5 > /var/run/s6/container_environment/QT_SCALE_FACTOR
echo -n 2 >/var/run/s6/container_environment/QT_SCREEN_SCALE_FACTORS

When you choose File > Exit, ozw-admin will restart and use these new environment variables, resulting in Preferences looking like this:
Screen Shot 2021-01-24 at 7 35 32 PM
I also came up with this one-liner that I also copy/paste to resize the client from the default 1024x768 size:

perl -pi -e's/-platform/-qwindowgeometry 1536x1152 -platform/;s/=1024x768/=1536x1152/' /var/run/s6/services/ozwadmin/run

which, when all combined together, makes Preferences look like this, providing a lot more room to interact with ozw-admin:
Screen Shot 2021-01-24 at 7 37 50 PM

As I mentioned, these are temporary changes, so anytime the container gets re-created it's necessary to re-run the commands. Since I don't need to restart my OZW container very often, this temporary work-around is OK for now.

Not sure this will work in other situations, but thought it was worth mentioning in case it helped anybody else.

@Tieske
Copy link

Tieske commented Oct 2, 2021

when starting the container I pass in these environment variables and it works for me

  • QT_SCALE_FACTOR=0.5
  • QT_SCREEN_SCALE_FACTORS=2

Does not require to shell into the container, and to modify any files. I'm using it on a Synology NAS, hence configure it using a GUI, but from the command line you should be able to add it to the docker run command by adding this:

-e QT_SCALE_FACTOR=0.5 -e QT_SCREEN_SCALE_FACTORS=2

thx to @eddyg for finding the right names to set.

EDIT: I must note that I use the all-in-one image

@fgonza2
Copy link

fgonza2 commented Apr 14, 2022

we should close this. OZW is obsolete I have migrated to zwaveJS which is awesome and works great, never regret the migration

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