At the options menu, select: Install/update: Custom UEFI Firmware (the firmware will now be flashed)
When back at the options menu: Exit, and Power Off
III. Prepare a USB Flash Drive using a PC
Download the latest Ubuntu LTS image file and flash it onto a USB drive (16GB or larger) using Rufus or Balena Etcher. If it’s an option, maximize or allow up to 16GB of persistent storage.
Shut down the PC and boot from the USB Drive using the Try Ubuntu option
Once Ubuntu is running, connect to the internet
Open a terminal and install the necessary software:
a. sudo add-apt-repository universe
b. sudo apt install libfuse2
Close the terminal and use Firefox to download:
a. The latest Home Assistant OS Generic x86-64 image from the Home Assistant website. (The same or similar to: haos_generic-x86-64-9.5.img.xz)
b. Balena Etcher for Linux x64
Right-click on the Balena Etcher file and select properties. In permissions enable: Allow executing file as a program
Power down Ubuntu (the flash drive is ready)
IV. Install the Home Assistant OS
Insert the flash drive into the Chromebox and power on
When the bunny logo displays, press Esc to open the boot manager
In the boot manager, remove all other boot options, and in the boot menu, boot from the USB drive
Run Ubuntu using the Try Ubuntu option
Once Ubuntu is running, run Balena Etcher by double-clicking on its file
Using Balena Etcher, flash the Home Assistant file to the System Drive
The flash process usually completes perfectly, however, an error will usually be indicated or the system will (appear to) freeze up. Do not be alarmed, allow a few more minutes and then power down, removing the flash drive.
Power on, and within a few minutes “Home Assistant” will be displayed in large letters at the top of the screen. Success.
V. Begin using Home Assistant
Set up your box in its desired location, connecting its power adapter and connecting to the internet via an ethernet cable
Press the power button. Within 15 to 20 minutes you will be able to configure Home Assistant via the local webpage: homeassistant.local:8123
Sorry for the tardy reply. The Asus CN60 seems to tick all the boxes. It’s responsive and instantly turns my bedroom lamp (on LocalTuya) on from my phone or PC. Since it has an Intel Core I3 CPU and 4GB RAM, I sometimes wonder if I will one day have multiple servers installed. I don’t presently have the expertise, but I think it’s possible to install a Plex server and a NAS server in containers along with Home Assistant, all on one device.
My purpose in getting Home Assistant has been fulfilled. Room temperature control. One of my first automations successfully turns my fan and heater on or off based on room temperature. Starting my day, and lights-out automations are also working fairly well with only a bug or a few.
My current challenge is home and away detection. As I gain expertise I will improve on this as well as Zigbee devices and NFC, both of which I have installed. and will eventually implement with automations.
These projects are now all on the back burner as my main interest is in Biblical studies. When implemented as God designed, the Bible brings more vitality than the healthiest food and is more enthralling than the best at the box office.
Especially if you are a fellow Bible enthusiast, I am interested in your experience and sharing as well.
Hello, in steps III.5 and 6, after downloading HA and Balena Etcher and changing the executing permission, I notice that these files are not persisted to my flash drive. When I continue onto steps IV these downloaded files do not exist. I have tried this 2 times and I get the same result. These files are not persisted. What is the workaround?
I think I solved my problem. Rufus USB Format utility has an option for selecting a Persistent partition size that I didn’t see before, or new I had to set! Reformating my bootable usb device now.
Thanks for the detailed instructions, I was able to boot up HASSOS on a CN62! I took a different turn after the firmware part (section III and on), so I’m posting in case it can help others.
First, I’m not sure if our hardware differs that much, but Ubuntu was virtually unusable performance-wise as a live boot on my Chromebox (tbh I never had any luck running any Ubuntu smoothly). I used the latest Lubuntu LTS release instead, which runs way better on lower specs hardware.
Second, I followed the instructions from the official docs to restore the HASSOS image, replacing sections III and IV here. This essentially skips the live boot part on your preparation PC. The difference with the official docs is that Lubuntu is not natively bundled with the Gnome Disks utility, but you can install it in a terminal with sudo apt-get install gnome-disk-utility. I haven’t had any success with KDE Partition Manager, sadly.
Also, if you bump into a screen saying Developer Mode is restricted by the device owner of your Chromebox or something (I picked up my box at an auction so most likely it was still associated with the business) , I was able to solve that by powerwashing the device. Google is your friend here.
Hello Alexis, perhaps the issue with slow performance is with your flash drive rather than your ChromeBox. My device has an Intel Core i3 processor and 4 GB of RAM, and I’ve never experienced any performance issues. I’m unfamiliar with KDE, but I have had great results with DiskGenius, which can also run from a flash drive.
Thanks for sharing your victory in installing the disk image. It helps to have more installation options and firsthand accounts of their success.
Fair point, I only had my old faithful OS installation 8Gb USB drive around so I didn’t try other options in that regard. I also have the lower spec Celeron CPU so probably a combination of both.
As you said, my point was to showcase an alternative for readers that would encounter issues.
