I know a ton of embedded shops that are running x86 (including some actual i386 still) in production, and will likely for years to come. That stuff was bullet proof, cheap and still runs today.
It’s not the same. With a mobile carrier, you could just continue to make monthly payments as normal, and at the end of your contract, the payments stop.
With this program, you can either pay a lump sum to cancel the lease early, or you can continue making monthly payments, but at the 24-month mark, since you can’t return the phone, you’ll still owe them $430.
It's not that it's that complex to need all of this. It's about ease of use. Home Assistant OS makes life simpler for users (such as myself), it makes it easy to use adding that run as additional docker containers, it makes plugging in USB z-wave/zigbee devices a breeze.
While it is technically no longer supported, you can still install the whole kit and caboodle using pip in a Python virtual environment, but why would you?
> You can still install the whole kit and caboodle using pip in a Python virtual environment, but why would you?
This is how I did it, instead of the container or HA OS in a VM.
If you want the simplicity of everything preconfigured, managed, and hands-off, go with HA OS, whether in a VM on a beefier machine, standalone, or the HA Green/Yellow dedicated hardware.
But if you already have a home server and want to add HA, I found just pip installing to be easier than dealing with the container.
Maybe I'm just the silly type that enjoys fiddling with Linux, but I'd argue that it actually makes more sense to install HA bare metal over a container. HA doesn't actually have any major dependencies outside of what pip installs, so setup wasn't any more annoying than via container. And then you never have to deal with container annoyances like passing hardware through to it or weird failures and misconfigurations.
Contrast this with https://frigate.video/, which has so many fragile native dependencies and a super complex stack that trying to install manually is an exercise in futility. I gave up and used the container.
This is what I've been running on my generic x86-64 system for a couple of years now, 0 issues. Even migrated to a newer system recently because I wanted something that was slightly faster for ESPHome compilations.
"self-installing" being the key point. Those instructions require you to use some other piece of software to write the image onto your boot disk. In my case I used an Ubuntu livecd to download and write the image to the machine. It's obviously not a showstopper but it is slightly annoying.
That's why Matter and Thread are IPv6. You don't need IPv4 at all... and if you run out of IPv6 address space, I'd love to see just how many devices/sensors you have in your home.
What might be a problem is the number of devices that can be connected. For example someone who is using an Xfinity Gateway for their WiFi has a limit of 100 devices on each band (2.4 GHz, 5 GHz, 6 GHz) if they are on an XER10, XB10, or XB8. An XB7 can have 75 on each of 2.4 GHz and 5 GHz. An XB6 can have 30 on 2.4 GHz and 75 on 5 GHz.
I went through the whole blind research rabbit hole and ended up with Smartwings via Amazon. I had looked into a lot of other providers and nothing had a similar combination of reliability, cost, and customer service.
yeah, I think it's one of those annoyingly over stylized articles that animates/loads as you scroll and Archive doesn't preserve the javascript (or whatever) to make it look & work right
reply