I posted yesterday about my HA system plan. After hearing from a few members that the plan was OK, I pulled the trigger on the install.
Flashed the HAOS for Generic x86-64 on my new SSD using Balena Etcher. Got the “flash successful” message. Removed the old laptop HDD and installed the new SSD. Made BIOS changes to enable UEFI boot and set the new SSD as first boot device. Connected an ethernet cable into my LAN.
When I turned the system on, I never got the Home Assistant welcome screen … only a blinking (command line?) curser in the upper left corner of the display. Tried logging into the HA system from a browser on my desktop machine at both homeassistant.local:8123 and homeassistant:8123 as suggested in Installation Help documentation. Nothing…
Any ideas how to proceed would be greatly appreciated.
Karl
HA System: dedicated Asus U52F laptop, 2.5GHz dual core i3 processor, 4GB RAM, 240GB Crucial SSD.
My mistake
I didn’t realize generic x86 was supported
You should verify OS is booting properly
I’d expect to get some message if OS not boot or nothing running so the flashing prompt tells me OS booting but something is hanging or it’s actually doing something in background but not displaying to you.
This is expected. You’re welcome to install HAOS on a laptop obviously but the operating system has no GUI. A blinking cursor is all you will ever see when you lift the lid of that laptop as long as HAOS is installed.
That isn’t expected. It’s possible that is caused by reasons outside of HAOS’s control though. Those urls work via mdns and llmnr and not all devices understand those technologies.
Find out the ip address of your laptop on your network. You should be able to see this in your router (or by using the terminal when you lift the lid if you’re more comfortable in the command line). Once you figure it out go to your desktop and enter http://<ip address>:8123.
If that doesn’t work then something is wrong with HAOS and you’ll need to track down logs. If that does work then your desktop is unable to use the mdns or llmnr names. So you’ll either need to debug that on your network/machine, use the ip address instead or figure out an alternate way to give it a local domain name (like in your router perhaps or a local DNS server).
Still running down my install issues. Responding to some of the replies …
stevemann … I did use the generic x86-64 install image for the HA OS
CentralCommand … The HA welcome screen never came up on the laptop, only the blinking curser. I could not enter any text from the laptop keyboard. I couldn’t log into the HA laptop from my desktop.
nickrout … I’ve waited hours for the home screen. I’ve power cycled a few times. No change to the curser. No welcome screen. Can’t get an IP address of the laptop. Logged into my router looking for a new wired client, since I was connected via ethernet cable. No new wired device showing up.
Thanks for the suggestion. I reflashed the HASS OS image as you suggested and tried again with same results. I’m suspecting my ancient laptop just is the wrong hardware solution. It is well over ten years old and the BIOS is pretty rudimentary to set up like recommended. It will be turned back into my Linux playground.
I’ve decided to substitute a much newer Dell OptiPlex 3050 micro ($100 eBAY special). It still has a dual core i3, but runs at bit faster and has 8GB RAM. The box just arrived and I will verify it all boots into the installed Windows 10 before doing the BIOS mods. If all works well, I’ll pull the SSD and replace it with the same HASS OS imaged SSD that I used on the laptop. If it boots successfully into HA, I know the problem was related to the laptop in some way. If it still doesn’t bring up HASS OS, I will scratch my head a bit and figure out a new install plan.