Newbie: Difficulty Setting Up Home Assistant

Installation Home Assistant OS
1

New to HA. I setup a VM on Fedora Core 43 running HA OS. Been trying to use ChatGPT and Gemini to setup HA. I am very skilled in Linux.

What I know:

  1. I don't have add-on apps
  2. I don't have logbook
  3. I don't have recorder
  4. I don't have history
  5. hassio is up, but not reachable.
  6. Don't have HACKs

The hassio and docker0 virtual network bridges on your host are marked as disabled. Because those internal bridges are down, the Home Assistant Core container cannot talk to the Supervisor container across the internal network layer, blocking the UI components (like the Add-ons panel) while the underlying processes run blind.

What next?

Thanks,

Mark

2

Why are you using an AI? How's that actually going for you?
I suggest try the documented way. You sound like you want to install HAOS either in a native version or in a VM, both are listed here.

3

Hi - I followed the HA install guide for initial install of HAOS on a VM. But, not all things were working. I was following another guide and it mentioned HACs (or HACKs) and I
could not find it. I turned to ChatGPT to try to diagnose the problem. During the
process found logbook, recorder, history, and some other things are missing. They appear to be there, but not responding.

System Information

version core-2026.6.2
installation_type Home Assistant OS
dev false
hassio true
docker true
container_arch amd64
user root
virtualenv false
python_version 3.14.5
os_name Linux
os_version 6.12.85-haos
arch x86_64
timezone America/New_York
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 17.3
update_channel stable
supervisor_version supervisor-2026.06.1
agent_version 1.8.1
docker_version 29.3.1
disk_total 30.8 GB
disk_used 5.3 GB
nameservers 192.168.42.1
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons Z-Wave JS (1.4.0)
Dashboards
dashboards 3
resources 0
views 1
mode storage
Network Configuration
adapters lo (disabled), enp1s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth58a0de6 (disabled), veth1737326 (disabled), veth62cb6eb (disabled), vethdde7f45 (disabled), veth35666ab (disabled), veth05ca1d2 (disabled), veth3a94dd8 (disabled)
ipv4_addresses lo (127.0.0.1/8), enp1s0 (192.168.42.50/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth58a0de6 (), veth1737326 (), veth62cb6eb (), vethdde7f45 (), veth35666ab (), veth05ca1d2 (), veth3a94dd8 ()
ipv6_addresses lo (::1/128), enp1s0 (fe80::84ce:9264:1de:cf72/64), docker0 (fe80::7c16:1ff:fe75:9965/64), hassio (fd0c:ac1e:2100::1/48, fe80::f4ef:1ff:fe06:94e8/64), veth58a0de6 (fe80::cc2a:9cff:fe0f:b028/64), veth1737326 (fe80::d847:e3ff:fe51:27d4/64), veth62cb6eb (fe80::9ca4:f7ff:fee4:11b5/64), vethdde7f45 (fe80::f4b7:9dff:fe86:c4df/64), veth35666ab (fe80::48d7:9aff:fea6:37f4/64), veth05ca1d2 (fe80::108a:5aff:fe83:87c8/64), veth3a94dd8 (fe80::b0b5:d0ff:fe43:ca11/64)
announce_addresses 192.168.42.50, fe80::84ce:9264:1de:cf72
Recorder
oldest_recorder_run June 1, 2026 at 10:55 PM
current_recorder_run June 11, 2026 at 5:09 PM
estimated_db_size 14.06 MiB
database_engine sqlite
database_version 3.49.2

The hassio and docker0 virtual network bridges on the host are marked as disabled. Because these internal bridges are down, the Home Assistant Core container cannot talk to the Supervisor container across the internal network layer, blocking the UI components (like the Add-ons panel) while the underlying processes run blind.

But, I don't know why or how to fix it?

4

Installing Home Assistant in a VM under Ubuntu can work. It works OK if the goal is just trying out HA to see how it works, but it is a very poor way to set up a production server. The reason is that you now have a dependency stack. The VM depends on some library, and maybe your web browsers depend on the same thing, so now updating Chrome or Firefox means restarting the VM.

You never want to be in a situation where updating a desktop web browser means the light switch in the bathroom stops working, or your wife has the video stream to the TV interrupted because your email client has a security update. That is just plain wrong. Dependency stacks are OK only in development or test servers, never on a production server.

Many people do run HAOS on a virtual machine. But they use a bare metal hypervisor to host the VM, and the hypervisor’s only job is to host a VM. It has no other features. Proxmox is a common choice.

OK, so you are just kicking the tires and want to try HAOS. It should work fine if the VM is using a bridged network adapter. If you are having problems, you should tell us how you have set up the VM and how you have passed the network and USB to the VM.

5

Fedora Core 43 with a KVM running HAOS.

I am using the Zooz 800 Series Z-Wave Long Range S2 USB Stick ZST39 LR.

Fedora saw the stick as Bus 002 Device 002: ID 1a86:55d4 QinHeng Electronics 800 Z-Wave Stick

with device path /dev/serial/by-id/usb-Zooz_800_Z-Wave_Stick_533D004242-if00

which pointed to ../../ttyACM0

The VM was configured in KVM/virt-manager (or Cockpit) with Add Hardware → USB Host Device and the Zooz/QinHeng USB device was selected.

Once attached to the VM, Home Assistant OS saw it directly and Z-Wave JS reported:
Controller ready, Firmware 1.70, and Add device available

Home Assistant VM was is not using the default libvirt NAT network** (192.168.122.x). I setup a bridged connection on br0 so Home Assistant would appear directly on my home network.

The Home Assistant VM was attached to Bridge device: br0,
Model: virtio and gets a reserved IP addresses on my private network.

Thanks,

Mark

6

It is AI-Bullock .

Im not sure there is a guide for HA-VM in Fedora in HA-Docs, But you maybe another KVM guide will help

Focusing on Your claimed Network Issue

Everything seems to look fine ( Notice IPv4 , on enp1s0 )
The other “network addresses” you see is HA-Internal, and these are nothing you should worry about, just make a note that they are there

Apparently this is KVM’s way of implementing VM’s, And yes it needed to be bridged

If you by any chance have a Virtual LAN , Network setup , i believe you need to look into this part ( Also )

Elaborate on this, as i think the other points above are ok

7

Hi, welcome to the forum!

Are you using that system for other stuff and/or already for other VM's?
Do you know about the existence of Proxmox VE?
If not, or not much details about it, I would strongly advice you to have a look at it if you don't want to install HA bare metal.