remote_homeassistant VS nixpkgs

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

I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.

As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...

For example,

```

Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...

I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...

NixOS uses a monorepo and I think everyone's love it.

I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.

Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.

https://github.com/NixOS/nixpkgs

In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].

[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...

[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...