Possible to install on another host?

[dekiesel]

Let me preface this by saying that I have seen that it is strongly recommended to install Bermuda via HACS.

But I've also seen, that there were slowdowns reported in some issues. Since I want to keep the WAF high I was wondering if it is possible to run Bermuda on a different host or if it is not only recommended to install via HACS but the only possible way.

Any hints are welcome! Thanks!

[agittins]

TL/DR: Bermuda must be on the same host as it runs "inside" of HA.

So there are two types of "extra things that don't come in the box with Home Assistant":

• Add-ons: these run in docker containers "alongside" home assistant, in their own execution environment. They might be in any language and may or may not have multiple executables. Most can be set up to run on another host, assuming any network and filesystem requirements are managed.
• Custom Integrations: these are python code that run "inside" home assistant, so they must run on the same host, regardless of whether they're installed via HACS or manually.

HACS does not handle Add-ons, only custom integrations (and cards and themes, if you consider those to be distinct).

Since Bermuda is a custom integration, Bermuda must run on the same host as Home Assistant.

Since HACS takes care of dependencies, permissions, updates etc etc, it makes support WAY easier, so I don't promise to provide any support for anyone who is deliberately choosing to make both our lives harder by not using HACS. 😁

Re slowdowns, there are a few possible situations where they've come up:

• some earlier versions did excess processing or had bugs in how Bermuda used the async setup. These issues are not present in the current release.
• enabling lots of the "disabled-by-default" sensors in Bermuda, like "distance to..." or "unfiltered distance to..." will cause extra load due to internal state (on the host) and browser state (on the client) being larger and more dynamic, and by causing more data to be logged to the database. There's info in the wiki on how to manage which sensors get logged to the database if that's a concern.
• if you are running on a particularly resource-constrained machine (various types of rPi) along with other integrations or add-ons that are a bit "busy" then Bermuda might push things from "barely ok" to "not ok", performance wise. If your current cpu usage is around 10 to 20% you'll probably be ok.
• if some other integration is pumping obscene amounts of Bluetooth data into ha, this will cause issues, with or without Bermuda. This has happened with older versions of a custom integration that lets you use Android devices as a Bluetooth proxy.

As with all performance-related stuff, you just gotta suck it and see. Check your cpu usage before and after install if you're concerned, and don't mess with the settings until you know you're ok with the system load.

Hopefully that covers it, but let me know if you've got any questions!