Installing Home Assistant OS using Proxmox 8

Can the upgrade of Proxmox from 6.4.13 to 7.x be done from a shell within the UI by using this → sudo apt update && sudo apt dist-upgrade -y && sudo apt autoremove -y? I was thinking it had to be done outside of the UI.

Follow the instructions here
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

Does anyone here have Unifi Dream Machine Pro? Or some sort of Unifi device hosting dhcp/Unifi controller? If so, I’m looking for help. So HA is in the LXC an running ok. I have the Unifi integration installed and devices are showing fine. When phones disconnect from Wi-fi the device tracker changes to away. However when they reconnect the device tracker does not change status to home. I have seen on the integration page


Presence detection depends on accurate time configuration between Home Assistant and the UniFi controller.

If Home Assistant and the UniFi controller are running on separate machines or VMs ensure that all clocks are synchronized. Failing to have synchronized clocks will lead to Home Assistant failing to mark a device as home.

however there is no mention anywhere how to setup the time sync. I can’t find anything with a Google search either

I know this isn’t a Proxmox support forum :wink:

That said, reading the upgrade instructions I am hesitant about this section:
(my emphasis)


Update the configured APT repositories

You must also disable all Proxmox VE 6.x repositories, including the pve-enterprise repository, the pve-no-subscription repository and the pvetest repository. Use the # symbol to comment out these repositories in the /etc/apt/sources.list.d/pve-enterprise.list and /etc/apt/sources.list files. See Package_Repositories

Add the Proxmox VE 7 Package Repository

echo "deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise" > /etc/apt/sources.list.d/pve-enterprise.list

For the no-subscription repository, see Package Repositories. Rather than commenting out/removing the PVE 6.x repositories, as was previously mentioned, you could also run the following command to update to the Proxmox VE 7 repositories:

sed -i -e 's/buster/bullseye/g' /etc/apt/sources.list.d/pve-install-repo.list


Would I be right in thinking that I have the no-subscription repisitory and I can run the above sed command.

(I just wonder why they document two methods; the sed command or commenting lines in config files?)

Great guide. Thanks @kanga_who!

Can I suggest that step 2.3 needs to be changed a bit? The parts about buster can be switched will bullseye.

1 Like

I plan on updating the guide over the next week or so to reflect any changes that need to be made with Bullseye :+1:

1 Like

great into and manual to this topic. Exactly what I was looking for the next weeks to come :slight_smile: May I ask you also kindly to please check & update on if proxmox 6.4 or 7.0 should be used instead of 6.3

Use the latest available. As noted in the post directly above, the guide will be updated shortly.

1 Like

I am looking at running another instance for testing purpose. If I run the script will it automatically increment the VM ID or will it create another one with VM ID 100.

Yes it will

:+1: Thanks for confirming.

1 Like

Thanks. A perfectly straightforward guide, no hidden snafu’s. Nicely done!

1 Like

Have anyone used this guide and succesfully gettting the Conbee II to work?
I am really struggeling, could it be that proxmox 7 have an issue?

The conbee show up in homeassistant but can’t find anything no matter what?

I assume you’ve passed the device though to the VM correctly?

Correct. Can see there at other post in the community, but none of them have any answers and solutions.
As of the picture below the Conbee looks like it is connected correct.

Have tried using Deconz integration, ZHA and Zigbee-2-mqtt

@MartHan

I have ConbeeII working with Deconz without any issues using Proxmox 7.

How have you configured ConbeeII in Proxmox - have you passed through the device or the USB port?

I have passed through the device:
Proxmox_conbeeII

1 Like

I wouldn’t select “Use USB3” because it’s a known issue that causes interference with the network

1 Like

Good pick up.

I think I this is a hangover from when I first moved from a Pi3b+ to a x86 box, and selected this as the ConbeeII is connected to a USB3 port and I wasn’t sure what setting I needed.

Interestingly, I am not sure if this has caused me any issues - ConbeeII on a 3m extension lead out of a Optiplex 9020m.

Just deselected it and restarted the VM - will be interesting to see if I see any changes in behaviour.

1 Like

When you say configured, what does you exactly mean?
Isn’t all you need to do is to add the USB port, like you did i your picture?
Or is there more to it? :slight_smile:

But, as per the picture and my prior message, I am pointing out that I haven’t added the USB Port - I am passing through the Conbee II Device - not the USB port.

I was asking, as you were stating you could not get yours to work and this may have been a difference in our set-ups that may help you.

1 Like