Display Scaling

[RyanEwen]

Is it possible to somehow scale the web page shown on a device? For example, with the ESP32-8048S043, everything is very small (mostly due to it being stuck in landscape mode at the moment). I was thinking I could use it in landscape but it would save a lot of messing with my HA dashboard if I could tell the remote webview to scale the page so that it is larger.

[strange-v]

I've already tried implementing scaling, but with no luck — nothing worked as needed.
I may try again at some point (perhaps by switching to Chrome, if that works), but there's nothing I can do now.

[Heronimonimo]

I've already tried implementing scaling, but with no luck — nothing worked as needed. I may try again at some point (perhaps by switching to Chrome, if that works), but there's nothing I can do now.

Does anything scaling wise happen when you use the '--force-device-scale-factor=1.5' parameter for the server?

Also it seems that for Puppet (the add-on that makes screenshots of a webpage and serves it as image) they have found a way doing this using built in Chromium: https://github.com/search?q=repo%3Aballoob%2Fhome-assistant-addons%20zoom&type=code

[Heronimonimo]

Another option would be to add playwright-zoom to get it working with the current setup using playwright: https://github.com/dszendrei/playwright-zoom

[strange-v]

AFAIR, there was no effect at all from adding --force-device-scale-factor=1.5.
playwright-zoom looks interesting, thanks.

The switching to Chrome idea is also to solve another issue: strange-v/RemoteWebViewServer#4

[Heronimonimo]

AFAIR, there was no effect at all from adding --force-device-scale-factor=1.5. playwright-zoom looks interesting, thanks.

The switching to Chrome idea is also to solve another issue: strange-v/RemoteWebViewServer#4

And for HA users Chromium seems to be built in, so it might also fix the backup size issue if you use a similar config like the Puppet Add-on uses.

But the playwright-zoom route might be the faster one to implement for now.

[strange-v]

Just to clarify this part:

And for HA users Chromium seems to be built in…

Home Assistant itself does not provide Chromium to add-ons. Each add-on runs in its own Docker image.
The reason the Puppet add-on can avoid downloading an extra browser is simply because its own base image already includes Chromium, and Puppeteer is configured to use that instead of fetching another copy. This doesn’t mean Chromium is shared with the HA core or with other add-ons.

In RWV’s case, fixing backup size would only involve reducing what gets stored in /data (or other folder it backs up).

I don’t plan to work on RWV in the next few months, but I’m happy to review a PR if someone implements a fix/improvement without breaking the existing functionality.