Beelink N100 Mini PC and Home Assistant

Thanks for the hint.

Proxmox is already installed.

HAOS as well.

But cant update Supervisor from 2024.12.3 to 2025.01.0.0601dev

Any idea?

Already set Beta Channel via CLI

Why would you want to use the Beta Channel.
The official release is currently 2025.1.2

Because my Backup with all configuration wont else work.

Make sure your network/DNS settings are correct to get the update presented.

Hi,

It has the same Gateway and both DNS Servers Like my HAOS Installation on a Raspberry Pi 5.

Still doesnt find a Supervisor Update.

So I compared again

HAOS PI5 DNS Info

And Proxmox HAOS VM DNS Info

They share the same Host IP with 172.30.32.3

Do you have 2 hosts with the same IP on your network and .57 & .173 are both DNS servers on your network?

DNS Servers are .57 —> my primary Pi-Hole

And .173 —> Secondary Pi-Hole

I think I didnt setup both HAOS Enviroments under the same Host IP.

I could shutdown my HAOS on Raspberry Pi 5 and then use the one which is a Proxmox VM on my Beelink.

The original idea was to shutdown the one on Pi 5 and restore from a Backup from that one to the Proxmox VM.

But since it doesnt show the Supervisor Update on the VM I couldn‘t do that so far.

Are your Pi-Holes not blocking anything related and what’s your upstream DNS?

Hi,

No , they arent blocking anything.

On my PI5 HAOS Updates work like a charm with both DNS Servers. Pi-Hole also doesnt show anything blocked in the Web UI for Home Assistant

Upstream DNS Server:

Quad9

What happens if you try to access

from your browser and ping from your HA?

Try 1.1.1.1 for DNS

Will try that later.

Thank you

Update

First Link from Web Browser works

The second doesnt


How can I ping from Home Assistant?

The HAOS on Pi5 Shows following today

Found the following in Supervisor Log

2025-01-15 22:55:54.924 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection

2025-01-15 22:55:54.928 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed

Maybe I need to shutoff the HAOS Installation on Raspberry Pi 5 before continuing with HAOS on Proxmox VM?

If you don’t mind me asking? How many VMs and how have you split the memory/cpu allocation? I am trying to understand how many I can run on my own setup. I currently have HAOS and Ubuntu headless. Ubutnut is running Plex, but I am wondering if I can split this off into it’s own install with GPU pass through.

Excuse the delay in responding. I saw the question, moved it to another tab, and promptly forgot about it :roll_eyes:.

I’m not sure how much I can help you here, I use the late tteck’s helper scripts (now maintained by the community he created around them) for my Proxmox installs with (mostly) default settings. I then adjust available resources in Proxmox depending on how much of what the LXC’s/VM’s are using to balance that out. The only VM I install is Home Assistant, but I’ve had up to 3 instances running with everything else without issue… YMMV.

Hi Jason, welcome to the forum!

The answer to your question is not straightforward because it all depends

  • what you are doing with these virtual machines
  • are you using VM’s or LXC’s
  • how much RAM your system has

You can get an idea by looking at the individual RAM/CPU usage and the overall values to know how far you can go.

With 32Gb of RAM and a 4-core (i5-6500) I’m running 14 LXC’s and 1 VM.
The CPU idles at about 11% average and now and then a 50 - 60% peak

1 Like