Oh, also, not too surprising, but a ping6 fd6e:7763:6711::862 works fine.
➜ ~ ping6 fd6e:7763:6711::862
PING6(56=40+8+8 bytes) fd6e:7763:6711:0:cb:82fe:f55d:3a5b --> fd6e:7763:6711::862
16 bytes from fd6e:7763:6711::862, icmp_seq=0 hlim=64 time=8.856 ms
16 bytes from fd6e:7763:6711::862, icmp_seq=1 hlim=64 time=6.575 ms
16 bytes from fd6e:7763:6711::862, icmp_seq=2 hlim=64 time=3.506 ms
16 bytes from fd6e:7763:6711::862, icmp_seq=3 hlim=64 time=7.217 ms
16 bytes from fd6e:7763:6711::862, icmp_seq=4 hlim=64 time=3.652 ms
16 bytes from fd6e:7763:6711::862, icmp_seq=5 hlim=64 time=3.578 ms
16 bytes from fd6e:7763:6711::862, icmp_seq=6 hlim=64 time=4.321 ms
But I know less than nothing about IPv6 addressing, so I have no idea if this is relevant or not.
I would assume both IPv4 and IPv6 are enabled, as my laptop has an IPv4 address (192.168.1.25) and HA appears to have an IPv6 address (fd6e:7763:6711::862), but it’s a crappy Starlink router, so there are pretty much no controls or options.
I flashed my NUC’s SSD with Home Assistant OS using the haos_generic-x86-64-10.5.img.xz image as directed by the Generic x86-64 Installation Instructions. I don’t know what it enables by default, but I’ve tried net update eno1 --ipv4-method auto, net update eno1 --ipv6-method auto, net update eno1 --ipv6-method disabled (this one obviously killed all network connectivity, including HA Observer).
If I don’t change it, I’m guessing it’s using DHCP. The Starlink router doesn’t let me reserve IPs, so I don’t know that static would be a good method with my current setup.
I don’t exactly know what this question means, but I flashed the SSD on my Intel NUC with Home Assistant OS, so I’m not sure if this question applies to my situation.
Thank you for trying to help me. Please let me know if there’s any additional information that I can provide to help us understand what’s going on.
From here you can see the IPV4 address and the computer’s MAC address.
The OFFICIAL nomenclature is “Permanent Lease”, but different routers use different terminology. (I can imagine the tech support calls- “What do you mean lease? I own my router”). It refers to the lease time of the DHCP IP address assignment. As long as that lease time has not expired, when the DHCP server sees the same MAC address, it will reassign the same IP address. A permanent lease never expires, so for all practical purposes it acts like a static IP address (without the headaches). So, look through the router manual for “fixed IP, lease, or reserved”. You may find a reference to static IP, but that usually means the IP address of your router. Don’t go there.
I am not a fan of static IP addresses of my network devices. My IP scan shows that I have 142 devices on my network. Can you imagine the nightmare of documentation to keep track of this many IP assignments. That’s the beauty of DHCP. You don’t have to do anything. There’s a reason that using DHCP is the default.
Don’t worry about containers, Docker, VM or Proxmox. Since you are installing HAOS directly to the boot device, there is no need at all to add yet another layer to your installation. You only need one of those if you are doing other things on the NUC besides Home Asistant.
I thought this, too, but you can imagine my surprise to find that http://[fd6e:7763:6711::862]:4357]/ DOES appear to reach my Home Assistant NUC and show me a good Observer status. Replacing :4357 with :8123 gives me a connection refused (as if the port is not open) rather than a host unreachable (no device found at this IP address) error. That’s what seems incredibly strange to me.
It has come to our attention that there is a false and harmful version of our software, balenaEtcher, being promoted online. This post is an examination of the discovery, and a reminder to only download balenaEtcher from our official sources: the balena.io website, or GitHub repository.
Basically, the version at balena-etcher-io.comis spyware.
That answer might be to simple. The official etcher github is full of users complaining about ads, tracking and privacy issues in the official version
So it might be the issue linked by @francisp (that thread also posts a solution btw.)
As both projects are open source you have everything you need evaluate it. The simple fact that etcher shows ads that can’t be disabled and has a option to restrict tracking (which conveniently can only disabled after data leakage) might be some clue already. Missing ads and missing settings for tracking in usbimager on the other hand is something to investigate further.