HA is running fine - just going through the settings and learning how to add integrations and automations etc.
Did notice that although I can access the HA sever by IP address on the LAN, I cannot do so by going to homeassistant.local:8123. Does that need some extra configuration somewhere?
Ports have changed from 8123 to 80 on a new, default installation. homeassistant.local without specifying the port at the end should work.
Thanks - that worked. so xxx.xxx.xxx.xxx:8123 works but you can’t use port 8123 when using homeassistant.local?
No, the port changed from 8123 to 80 on new installs in 2026.8.0. 8123 is no longer in use if you start out with 2026.8.0.
I’m on 2026.8.3 - and xxx.xxx.xxx.xxx:8123 worked but homeassistant.local:8123 didn’t work while homeassistant.local:80 worked.
Im not sure why you at all makes such a commend ?, are you “recommending” Running HA in a Windows HyperV , on a 2 Core 2 Thread , Single Channel Memory Bus CPU ?
PS: im sure i don’t wanna see your answer, as well as your constant promotion of ProxMox in every Topic
Why are you being so rude? I make “such a comment” because you’re claiming things which I disagree with and to correct/educate. Hence why I was linking to official documentation.
And no, I don’t recommend Hyper-V. Why would I recommend Hyper-V when I apparently constantly promote Proxmox VE?
I made a single suggestion here to use PVE instead of Hyper-V. Why wouldn’t I recommend something that I consider superior? Especially since this topic is specifically about virtualization as per title?
And in this OP’s case you suggesting assigning 2 vCORE to HA ? on a amd A9 CPU
I wouldn’t call that “Superior” in any ways , it will in any case Not be a Stable Solution …
As i said , Your Commend and this Answer is not the way to “Guide” someone
Yes i know, and this is not the first Topic you jump in, with that very same “opening-line” , maybe without reading the Posts first, or just because you don’t know the " impact /consequences"
Face it ,OP would have ended up with most likely the worse experience, and most fragile installation of a Proxmox an HA Installation
I did not suggest that but you absolutely can. It works no different than an app on your PC having access to all your PC’s CPU.
PVE itself doesn’t need a lot of CPU and virtualization overhead is usually in the lower single digits so I expect it to perform somewhat similar.
This CPU is far from being fast but there’s enough RAM to be a waste to only use it for HAOS. Virtualization has been used since CPUs were even slower. I don’t think the age/slowness of a CPU is a good argument against using it to virtualize unless you have specific requirements.
What makes you think that?
Please enlighten me.
I will have to disagree..
IF a system never changes this is true.
Thats patently untrue in the case of HA. The system and underlying plumbing has SIGNIFICANTLY changed inthe last three years and in next version you’ll even need to change the proc type in Prox to even allow it to boot.
Yes two cores (is an A9 hyperthreaded I can’t remember… But 2 HT cores != 4 cores) can absolutely run HA especially w 16gb ram. It will absolutely also cause contention with OS base processing because proc queueing.
Now in an exploration sure knock yourself out. But understand it will creep along and clunk and sometimes exhaust threads and wierd stuff happens for no good reason…
BUT. With a newbie struggling with a new box and hoping they get a good experience? Asking if a machine is even VIABLE?
No!
Let’s not complicate the situation. In this -specific- case prox will probably make it worse.
And op - before I wasn’t saying don’t use this box I was saying dont attempt to Hyperv that box in windows. - primarily bec the USB pass through issue mostly but that box honestly doesn’t have enough chooch for hypervisor AND a passenger OS. Either or. Probably ok.
So please read everything above as options you CAN do a lot of stuff. Read up, it’s interesting as hell. But in HA you will find - like in windows land you CAN do it a bunch of different ways. (and many of them aren’t optimal) The ones that work for you may not work for someone else.
Now for the rest of us. Who are going to stop arguing on this nice ops thread… (right?)
When you give advice please stop and think if the advice is appropriate for the situation before just tossing It yes virtualization works, bare metal works this works that works but for this situation. With someone starting out on a less than optimal machine. Start SIMPLE. then if they have a good experience move on to more advanced config.
This machine is perfectly good for haos or container but I prob wouldn’t run container or haos INSIDE another virt platform because limited proc in this machine (personally I require four real not hyperthreaded cores before I even consider virt.)
Also op. I hope you get hooked on your new install and It makes you immediately want to go buy a new rig to run it on. 
good luck.
You learn the most when you have to fix it.
How to put it? You’ve put yourself on a path of robust learning! Self torture.
In retirement, time doesn’t equal money, so maybe a potter around and finding just how close you are to stepping off the edge of the flat earth you are really going to get to without a parachute.
Read lots. Make lots of snapshot backups so you can revisit your mistakes with fresh options, and discover why gardening may increase your lifespan than persisting with a Penny Farthing in midtown Paris peak-hour traffic.
Save your money while you are tinkering to get something more appropriate. Even your local recycling place may be a source of a box with more grunt. A laptop with a broken screen can be plugged into an external screen like the one you already have while you are getting it going and then it can become a headless server (as designed) and you can use this HP box to run your web browser to remotely access it, even using Windoze.
Yes that’s partly the intent. Plus no point outlaying major capital funds (ie >$100) if I don’t even know whether it’s going to work for me and how I can extend it. Once I get to that point, I will look at upgrading the machine. At that time what should I look for as a min:
Just for a bit of encouragement, 8 years ago I retired and my project for the first winter was home automation, after a few false starts I ended up putting HA on an old pi3 I had in a drawer. Now 8 years later and many mistakes and a massive learning curve I now have loads of devices many of which are home made Esphome stuff. I went from very little if any coding experience since messing with a BBC micro, to trying to help out here and a few other places. Still can’t code by the way, but I have got the hang of yaml, and an understanding of the structure of stuff.
It has kept me busy and still learning stuff on those rainy days.
So keep at and ask away there will always be someone to help and if you don’t understand the answer ask again as many tech terms here might not be obvious.
To be Correct:
" Every processor in the AMD A9 family features a rigid 2-core, 2-thread configuration. This means each physical core can only handle a single instruction stream at any given time." ( It’s not “Hyperthreaded” ) as far as i know
And it only support “single channel memory”
It’s own specs
32KB L1 data cache per core.
96KB L1 instruction cache shared per two cores (per module).
1MB L2 cache shared per two cores (per module).
So yes either way, virtualization , i would say is a " No Go " for HA , with those specs.
So it’s great OP got it up and running in a baremetal environment
So many options…
No matter which install method you use,