You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Home Assistant (HA) runs on a "Blue" (Odroid N2 with HassOS). This has been functional-ish. My gripes are partly with the move from declarative configuration via yaml to a config flow (I dislike click-ops); and with some quirks of the supervisor and hassOS ecosystem. I don't like the limitations on DNS config, or lack of customization with container parameters. This typically interferes most with add-ons like node-red, and with network connectivity. I use many vlans, and while the configuration I've defined is explicit about how to network, the supervisor tries to connect across all vlans anyway and the subsequent failures make connectivity appear "spotty"
Describe the solution you'd like:
Move the home-assistant core to bloopysphere. This will require making a helm-release, allocating storage, migrating config and state backups. Take some inspo from budimajojo's approach here. Healthchecks should be relatively straightforward using the appropriate kustomize config.
The text was updated successfully, but these errors were encountered:
Details
Currently Home Assistant (HA) runs on a "Blue" (Odroid N2 with HassOS). This has been functional-ish. My gripes are partly with the move from declarative configuration via yaml to a config flow (I dislike click-ops); and with some quirks of the supervisor and hassOS ecosystem. I don't like the limitations on DNS config, or lack of customization with container parameters. This typically interferes most with add-ons like node-red, and with network connectivity. I use many vlans, and while the configuration I've defined is explicit about how to network, the supervisor tries to connect across all vlans anyway and the subsequent failures make connectivity appear "spotty"
Describe the solution you'd like:
Move the home-assistant core to bloopysphere. This will require making a helm-release, allocating storage, migrating config and state backups. Take some inspo from budimajojo's approach here. Healthchecks should be relatively straightforward using the appropriate kustomize config.
The text was updated successfully, but these errors were encountered: