Open Home Assistant Dashboard/ Browser by default #60
Replies: 1 comment 1 reply
-
|
currently more inclined to keep the overlay-based approach, because it is more reliable in terms of compatibility and stability. The main reason is that some older Android devices simply do not have a usable browser engine, or their built-in / Google WebView implementation is incomplete or unstable. I have already tested this on real devices, and in those cases enabling an embedded browser can lead to crashes, freezes, or even make the system difficult to use normally. For this class of hardware, tightly coupling the app to a browser-driven foreground home screen would introduce more risk than using a dedicated solution like Fully Kiosk Browser. On the other hand, Ava’s current overlay logic is already quite solid and much more flexible. Users can continue running Ava in the background while using Fully Kiosk Browser as the main front-end, and then use Ava’s overlay browser only when needed for notifications, temporary pages, or more polished screensaver-style content. This preserves Ava’s strengths without forcing every device to depend on a working WebView environment. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there any option to force or automatically open a browser?
Currently, I’m using Fully Kiosk Browser in order to boot straight into a Home Assistant dashboard.
The only option in Ava is to open a webpage through Home Assistant, right? It would be great if there were an option to simply replace Ava’s start page with a dashboard URL. The little settings icon in the bottom right could then be used to open Ava’s home screen.
Beta Was this translation helpful? Give feedback.
All reactions