remote_homeassistant VS frigate

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

Am in to selfhosting and homeserver, finally got to try Frigate with some aliexpress camera that was not mine. Love it.

However, I have had success using IP Camera app with Frigate. https://play.google.com/store/apps/details?id=com.pas.webcam https://frigate.video/

Frigate https://frigate.video/ and ZoneMinder https://zoneminder.com/ come to mind. Blue Iris https://blueirissoftware.com/ is not open source but is what I prefer to use for my PoE systems ($80/yr)

Logger: custom_components.frigate Source: custom_components/frigate/__init__.py:201 Integration: Frigate (documentation, issues) First occurred: 1:59:34 AM (2 occurrences) Last logged: 1:59:48 AM

Engineering implies working within constraints. Most people in this realm only have to deal with the spouse acceptance factor as a limiter.

Went from openhab -> homeassistant -> Node-RED. Then sprinkle in MySensors, Frigate, and Double-Take, but not on just the entrance, go for the perimeter then defense in depth.

https://www.mysensors.org/

https://frigate.video/

https://github.com/jakowenko/double-take

- https://github.com/blakeblackshear/frigate/discussions/7932#...

I have found my frigate+ model to be much more accurate and crazy good even at night. Will be curious how things change when it snows here more often, since I've not submitted any examples of winter at this house yet.

According to the author of that PR, they're using 10% of 1 NPU core on 3 cameras: https://github.com/blakeblackshear/frigate/pull/8382#issueco...

The bottleneck instead will probably be the video stream decoding speed, especially as the SoC's hardware decoder isn't being used yet.