home-assistant/core

Prefer upstream unless you specifically need this fork's older behavior or local customizations. This fork looks like a legacy maintenance branch, not a good starting point for new adopters.

Choose this fork only if you need its specific customized baseline or internal workflow changes. If you want current Home Assistant features and the easiest upgrade path, upstream is the safer choice.

Prefer upstream unless you explicitly need a 2015 legacy baseline. This fork is materially stale and highly diverged, so it is a poor fit for users who want current integrations, stability, or low-maintenance adoption.

Choose this fork only if EcoFlow Public API support is the primary goal and you are prepared to maintain a deeply diverged Home Assistant Core branch. If you want current Home Assistant features, active support, or easy upgrades, upstream is the safer choice.

Choose this fork only if you need its custom behavior or patch set. For most adopters, upstream Home Assistant Core is the safer choice because this fork is heavily diverged and likely to lag fixes and features.

Choose this fork only if you need its custom integration and workflow changes and can absorb the maintenance burden. If you want a stable, current Home Assistant base with minimal divergence, upstream is the safer choice.

Prefer upstream unless you explicitly need this old snapshot. This fork is only attractive as a legacy baseline or archival/customization starting point; it is a poor choice for anyone who wants current Home Assistant features, fixes, or active maintenance.

Prefer this fork only if you need an older Home Assistant behavior set and are prepared to maintain it yourself. For most adopters, current upstream is the safer and more capable choice.

Choose this fork only if you specifically need its older, highly customized baseline. If you want current Home Assistant Core behavior, active maintenance, and broad upstream compatibility, upstream is the better default.