#FullPageOS plus Supervised Installer?

1 messages ยท Page 1 of 1 (latest)

shell vessel
#

I have an external touchscreen monitor (not a tablet) with a Raspberry Pi 5. I was thinking I could install "FullPageOS" onto the Pi and then use the HA supervised installer. I could then configure FullPageOS to load the home-assistant page and use the touch screen to interact with Home Assistant.
Will that work? Has anyone done it? I know HA is basically just a web app but a 15" external monitor for $110 is way cheaper than finding an android tablet to repurpose.

bright rapids
#

Supervised is supported with Debian 12 only. And additionally the official support for Supervised installations is about to be deprecated.
The only "sane" installation methods are HAOS (can run in a VM, but no UI support by HAOS itself) or the Container install.

shell vessel
#

If it's deprecated, then I won't be able to get the "fully featured" HAOS unless I install.. HAOS ๐Ÿ˜†
I've seen so many examples online of people using touchscreens that I assumed it was part of home assistant rather than researching ahead of time. That's definitely on me. I'll just need to get creative and see what I can do

shell vessel
#

So... I'm getting a second RPI just for HAOS and I'll just keep it hardwired to the network. I've installed Emteria on the other RPI to drive the larger touchscreen. It has a "kiosk mode" that will open the HA dashboard. The nice thing is that the screen basically acts like an android tablet and I don't have to worry about battery issues since everything is plugged in. I'll just need to build a box to contain the wires and finish setting up the HA dashboard

burnt canyon
shell vessel
burnt canyon
#

Likely. If you tell me the model I can tell you more.

shell vessel
#

Dell XPS with an Intel core i5 (like i said... old)

burnt canyon
#

I need the model to tell for sure.

shell vessel
#

XPS 15Z L511Z

burnt canyon
#

I think that supports UEFI and might work.

shell vessel
#

I'll give it a shot. It's been sitting for a bit. It's got Ubuntu 20.04 running on it but I haven't touched it for a while.

shell vessel
#

It does not support UEFI. I'll have to try something else. There are some old forum posts about how to unlock UEFI on that particular laptop's BIOS but I don't even have windows installed to do that. Oh well

burnt canyon
#

Another choice would be to virtualize if you have enough memory.

shell vessel
#

The laptop has enough ram/hdd space (I upgraded it with an SSD 4 years ago). But it's 11 years old and I'm a bit worried about running it 24/7 like a server. The battery is internal and I'd rather not have a spicy pillow blow up.
So instead of a second RPI, I went with your recommendation and got a mini PC. It should arrive today. https://a.co/d/iV5pcvC

I know that putting HAOS directly onto the PC is an option but, after reading what you've posted (starting with the gist you sent), you have convinced me that that the more stable route is to install into a virtualized environment. I'll install proxmox and go from there! Unfortunately, I'll be out of pocket until next week. I'll update you then! Thanks for the help, @burnt canyon!

burnt canyon
quasi dew
bright rapids
quasi dew
#

thank you

quasi dew
#

the title mentions specific (older) architectures. do you know if this is only relevant to those or the whole supervised project?

bright rapids
#

Core installations and Supervised installations will not be supported anymore (but are still possible - for development for example).

#

Additionally the support for those old architectures will be dropped.

quasi dew
#

i see. thank you very much for clarification!

bright rapids
#

Those will not get new HAOS images for example.

quasi dew
#

coming from hassio, i understand the alternative is managing docker containers by hand and missing out on the awesome "update" button inside home assistant itself?

burnt canyon
#

Or just run HAOS in a VM. Or bare metal if you really want which I find to be a big waste on x86.

quasi dew
burnt canyon
quasi dew
#

thank you, i'll go read through all the links. there's quite a bit of info to catch up on ๐Ÿ™‚

#

at a glance it looks like it would make sense for me to move to "container" option, instead of dealing with it 6+ months down the line

burnt canyon
#

I personally run the container install in a debian VM in production. I also have a HAOS and a supervised VM to help people here.

quasi dew
#

haos on rpi has been running flawlessly for 5 years. i'm pretty happy with it.

i'm planning to add a TPU and read that it's a little easier with direct access to docker containers and underlying OS.
plus want to use the box for couple of small side projects as well

burnt canyon
#

If you want freedom like that then I recommend the container installation method.

quasi dew
#

thank you, that's the exact clarification i was looking for

#

with container method, what does ongoing maintenance for core looks like?

burnt canyon
#

To update you basically just have to run docker compose pull && docker compose up -d.

quasi dew
#

the hasle free "update" button inside ha is just so good

#

makes sense, thanks

burnt canyon
#

You could use dockge if you want a GUI like that that does not restrict you too much.

#

Portainer for example is too involved for my liking.

quasi dew
#

sorry, one last question for now:

any recommendations for underlying OS? (have slight preference to Ubuntu as it's most familiar)

burnt canyon
#

Like I said I use (and thus recommend) Proxmox VE and then a debian VM on there. Alternatively just debian.

quasi dew
#

alright, debian it is

burnt canyon
#

Ubuntu is pretty similar to debian so you can also use that. Use what you're comfortable with. I dislike the snaps and ufw and other things they do.

quasi dew
#

i'll give ubuntu a try then.

@burnt canyon @bright rapids thank you very much for all your help!

quasi dew
#

i remember now why i picked supervised method. built-in support for addons ๐Ÿคฆโ€โ™‚๏ธ

I can kinda see some of the concerns in above posts. Expirience with supervised hasn't been flawless so far. The part that i found most difficult is debugging and tracing where my particular problems come from

quasi dew
#

@burnt canyon dockge is pretty sweet.

went with docker compose setup, so far very smooth sailing. just need to figure out how to ensure it stays up running ๐Ÿ™‚

burnt canyon
#

Why would it go down?

quasi dew
#

good question, things do ocasionaly.

for example, on the initial supervised install the ha ocntainer threw and error and died. it comes up fine when restarted but somehow supervisor did not catch that.

#

also needs to come up on boot

#

was going to go with systemd unless there are better options

burnt canyon
#

Docker handles starting it at boot if you follow the compose docs on the website. It's called a restart policy.

quasi dew
#

oh? does it? didn't know that. i'll test it out

#

so essentially docker compose up -d is all i need?

burnt canyon
quasi dew
#

i'm honestly impressed at how fast you all pull up relevant docs ๐Ÿ™‚

burnt canyon
#

We do this every day so it's basically autopilot.

quasi dew
#

damn, it does indeed come back to life. all containers, including dockge

#

saved me a lot of time and hasle! thank you!

shell vessel
#

Update: @burnt canyon - I was able to put ProxMox onto the mini pc and install HAOS without any hassle. I followed the instructions on your site and it worked flawlessly. I'll post my final build somewhere at some point as soon as I build the frame to house the touchscreen/rpi and get it mounted in the house somewhere. Thanks again for your help!