operating-system VS remote_homeassistant

https://github.com/home-assistant/operating-system/pull/3248

BTW found exact same issue with homeassistant browsing the internet; Add support for Intel GMAC Ethernet controller (#2589) (#2593) · home-assistant/operating-system@9ca836f (github.com)

HAOS (https://github.com/home-assistant/operating-system) is not "vanilla" linux, and I have somewhat little experience of linux, although using raspberry-based systems (Domoticz, Pihole, etc) and basic usage of unix mainframes since early 90s. But the question I could not find answer for by googling is, could I use HAOS to farm chia as well, or is it too much optimized towards HA usage to reasonably serve as a chia farming computer too?

The main issue with the 3A+ is the 512MB of RAM. Combined with only having one USB port and no Ethernet, I would not advise using a pi3A+ as a sustainable foundation for HA.

Home assistant was the last thing I had running as a VM, but recently switched over to running it in a LXC container with their ContainerOS (i think that's what they call it). I would say don't do it (at least not yet), and go with their full OS in a VM (dl link to correct KVM/qcow2 version). I say don't start with HomeAssistantContainer b/c you lose Supervisor and the add-on store, and it's a bit less straighforward to get installed.

One thing to notice, I have been able to successfully boot Home Assistant OS Generic x86-64 https://github.com/home-assistant/operating-system which is using kernel 5.15+ and I don't know why I am able to boot HAOS (maybe they are using uncompressed kernel?), but not other general or special Linux distributions.

Raspberry Pi 4 64-bit

hass.io builds the whole gamut of images. There's a list at the bottom of the github page https://github.com/home-assistant/operating-system/releases/tag/8.0.rc2

I think you could make good use of the Remote Home Assistant Add-on to accomplish your goal here.

I know you're using Homeseer, but since you asked a general question: For Home Assistant, Remote Home Assistant makes it easy to create local proxy devices from another Home Assistant instance. For example, if you have a smart bulb in one house, you can create a virtual remote smart bulb in the other house, and then you can control the bulb from the other house as though it were a local device. It works with basically everything, including complex devices like TVs or thermostats. You just need to have an instance of Home Assistant running in each house, and a secure way for them to connect to each other.

You can use Home Assistant to do it. If you made a S2S VPN, you could easily add them all to a single HA instance. Otherwise, you might be able to connect multiple HA instances together to have all of the camera in once place.

Re No. 5: I've been meaning to look more into Remote Home Assistant, via HACS, which might be of interest.

I also use HomeAssistant, and am quite happy with it, but i wish, they would start including the [`remote_homeassistant`](https://github.com/custom-components/remote_homeassistant) addon.

It solves the Usecase, where not all BT(LE) devices in the house are reachable from the main HA, and you need remote "pickups" for their signals, and then want to integrate them back into the "master instance". It also solves a bunch of other problems, like integrating some sensors of the HA of your holiday home into the HA of your main home.

For some reason, NabuCasa doesn't want to integrate it. Maybe they see it as competing with an own upcoming (cloud?) solution of their own?

I use a Pi with its own Home Assistance instance and then use Remote Home-Assistant to link it to my primary instance. I only have one remote, but the documentation says that it can support multiple.

I see that in Home Assistant users can use plugin Remot-Home Assistant https://github.com/custom-components/remote_homeassistant

You would run a separate zigbee host, like the Deconz. And then one way to link, could be using https://github.com/custom-components/remote_homeassistant