HA-Nova 智能家居AI控制流

Optional remote access with Home Assistant Cloud (Beta)

The wizard keeps Local only as the recommended default. If you have a paid Home Assistant Cloud subscription from Nabu Casa with Remote UI enabled, choose Local + Home Assistant Cloud for automatic remote fallback or Home Assistant Cloud only for remote-first setup. The wizard validates your Cloud URL, opens Home Assistant OAuth, and stores the authorization in the native macOS, Windows, or Linux desktop credential store. HA NOVA runs no additional public tunnel or hosted broker.

Cloud Remote requires Home Assistant OS/Supervised and a supported desktop session for authorization; an interrupted, already-verified setup can finish over SSH with ha-nova cloud add --remote-resume. Headless, WSL, service, gateway, Container, and Core setups stay local-only. Remote-first pairing uses a separate private Owner session to create the one-time NOVA device code; the OAuth user can remain a standard Home Assistant user.

Already installed locally? Run ha-nova cloud add, or rerun ha-nova setup for the same guided choice.

<p align="center"> <img src="assets/cloud-fallback.png" alt="Local first, Cloud fallback: at home your machine reaches Home Assistant over the direct local connection; away, the same session falls back through your Home Assistant Cloud remote access."> </p>

Local stays first: the CLI prefers the direct connection and uses your Home Assistant Cloud remote access only as an automatic fallback — no manual URL switching.

Once it finishes, try: "Show me all my automations."

More than one Home Assistant? Add each further instance with ha-nova pair --server <name> --relay-url http://<ha-host>:8791 — every server gets its own profile and its own isolated credential. Select one with the --server <name> flag on relay calls or the HA_NOVA_SERVER environment variable, and manage profiles with ha-nova server list|default|rename|remove.

Upgrading from an earlier HA NOVA? Everything keeps working through the update. To move to per-device pairing, re-pair each computer once (one code each), then revoke the old shared access from the NOVA page whenever you're ready.

<details> <summary><strong>Platform notes</strong></summary>

<br>

macOS — proven end-to-end on real hardware.

Linux — proven end-to-end, including headless setups (servers, containers, LXC, SSH): with no desktop keyring around, the device credential falls back to a private file automatically.

Windows — proven end-to-end on a live Windows 11 system. Ships x64 builds (Windows ARM64 can use the x64 build through emulation; no native ARM64 bundle is shipped). - Claude Code is the most tested client on Windows today - Google Antigravity has basic validation - Codex and OpenCode are still early - Native prerequisites: Claude Code needs Git for Windows / Git Bash; Google Antigravity Desktop or CLI must be installed - See .claude/INSTALL.md and .antigravity/INSTALL.md

Do not download the ha-nova-installer-bundle-*.tar.gz / .zip assets manually. Those archives are used by the installer behind the scenes. Always use the one-liner or ha-nova update.

</details>

<details> <summary><strong>CLI commands & legacy uninstall</strong></summary>

<br>

Coming from a pre-Go install? - macOS / Linux: curl -fsSL https://raw.githubusercontent.com/markusleben/ha-nova/main/scripts/legacy-uninstall.sh | bash - Windows: irm https://raw.githubusercontent.com/markusleben/ha-nova/main/scripts/legacy-uninstall.ps1 | iex

</details>

Not a terminal person? Setup is one copy-pasted command; after that, Claude Desktop and Google Antigravity Desktop give you the same skills in an app window — and pairing another computer is just one more six-digit code.

---