Feature Request: integrate NoVNC Web Client

[taucher4000]

Since the VNC server is already installed, what to you think to integrate the noVNC Web Client into the App so that users can directly access to the Kiosk with the button in the Web UI.

There is already a similar Project which is starting NoVNC as a dedicated App. Maybe you could integrate this directly into your app?

[puterboy]

Not sure I understand need or benefit for this.
I really only added VNC to help with remote troubleshooting when one doesn't have access to the screen.
For regular use, it sort of defeats the purpose of HAOSKiosk -- if you are on a remote computer, why wouldn't you just use the regular web access (either through a VPN, Nobus Casa, or ssh.

In general, I want to err on the side of not adding unnecessary additional code that just makes the addon heavier in size or processing.

[taucher4000]

The reason for my inquiry is that my screen isn't even on the same network. I access the Home Assistant instance via the Nabucasa Cloud. Using VNC from my remote computer isn't possible. With the web-based VNC client, I can access the screen from anywhere in the world to troubleshoot issues.

[puterboy]

You should be able to use any standard VNC client.
Not sure what you are asking on the HAOSKiosk server side.
If there is a better, existing VNC server available in Alpine that you prefer that adds better web support without bloat or losing functionality of existing solution, feel free to submit a PR.

[taucher4000]

My ask is not about the VNC server but about adding a web based VNC client into the HAOSKiosk so that I can access to the Display through the Home assistant UI from everywhere in the world. .

[puterboy]

I'm sorry but I still don't really understand the use case.

[taucher4000]

I have created a change request for this feature. I've also added a short screen share video to demonstrate how it works. Hope this makes the use case more clear.

#95

(BTW - I haver also added a icon.png generated by AI. Feel free to remove it if you don't like it. There is no copyright on this icon since it is AI generated. Hence, there is no problem in using it. The icon is going to be showed in the Home Assistant UI un the App section.)

[puterboy]

Thanks. I will take a look and review.

• I like the idea of an icon though I want to think a little more about what it should communicate. Your example is a great thought starter!!!

• Regarding NoVNC Web Client - it looks pretty cool - but I am still not sure why this belongs in HAOSKiosk vs. in a separate addon-app.

Maybe I am misunderstanding the use case of VNC + HAOSKiosk, but my original inclusion of VNC was really just for remote testing & troubleshooting. In particular, I don't see the use case where you would use this full-time and enough to justify including more code and adding this as a built-in UI. Conversely, for remote testing and troubleshooting, I prefer using a standalone VNC since I have more control over the screen.

I am not saying I am against this, I just still don't understand its general applicability.
And if its generally not applicable, would it be better just to add this as an independent add-on?

[taucher4000]

Maybe I am misunderstanding the use case of VNC + HAOSKiosk, but my original inclusion of VNC was really just for remote testing & troubleshooting

That's exactly the same use case I have. The only difference in my solution is:

1. You don’t need to install a VNC client. If I want to troubleshoot something, I can simply open the Home Assistant UI and access VNC directly in my browser.
2. This becomes especially useful if your Home Assistant instance is not in the same network. With my solution, you can troubleshoot or test things from anywhere in the world. Just open your Home Assistant UI (e.g. via Nabu Casa Cloud) and connect to your kiosk using a web-based VNC client.

Let me explain my use case for HAOSKiosk:

I have a Home Assistant running in my camper van (using a Raspberry Pi). An LCD display is connected to it, providing a dashboard where I can control the entire camper (via HAOS-Kiosk). The system is connected to the internet via a 5G router.
When I want to test something (e.g. adding buttons or changing the dashboard layout), I connect via VNC to the kiosk to check how the changes look on the screen. Since I’m not always in my camper van, I access my Home Assistant remotely via Nabu Casa Cloud. With noVNC, I can connect to my kiosk directly from home using my browser.

If you want to learn more about my Camper Van project and use case, you can find the full documentation here: https://github.com/taucher4000/Smart_Camper

[puterboy]

Cool project but it really is a special use case -- i.e., troubleshooting when you don't have direct access to your HA server/display.
I provided the option to launch vnc using a built-in vnc server which works for the vast majority of use cases -- including yours though perhaps not in the exact way you would like. If you are on another network and worry about security you could use a vpn or tunnel over ssh.

I just can't see justifying adding another apk plus launching 2 additional server processes (x11vnc, novnc) just to support this edge case -- especially since there is a solid working alternative.

I also am concerned that a regular user could be confused by the option of having an HAOSKiosk dashboard within an HAOS web window.

But more generally, I really need to keep this add-on focused on its core mission - displaying HA dashboards on your HAOS server. Otherwise, there is no limit to the number of programs one could justify adding...

If you really want to use novnc, I imagine you could use 'docker exec' to manually install the apk and launch novnc.

[taucher4000]

Thank you for your feedback and the constructive discussion. It’s your project, so it’s your decision. Feel free to reject the merge request and close this issue if you wish.

Just a few final comments:

1. The "Benutzeroberfläche öffnen" button was already enabled in your version, but it wasn’t working. With my implementation, I gave this button a purpose, as it now actually opens a user interface.
2. I could also adapt my implementation to use your built-in VNC server. There is no strict need to run two VNC servers—it was simply more convenient and less intrusive for your existing VNC setup. A single VNC server serving both the web VNC client and external VNC connections would also work.
3. VPN and SSH tunneling are not always feasible. Modern network connections, such as fiber or 5G, often do not provide public IP addresses but instead use NATed networks. Therefore, a remote connection via VPN is not always possible. This is why reverse proxy solutions like Nabu Casa Cloud, homeway.io, or Cloudflare Tunnel are commonly used.