The HA Companion app needs an external_url for clickable notification
deep-links to resolve when the phone is off the home Wi-Fi. Reach is via
Tailscale (Headscale tailnet solar.internal), so external_url points at
the FQDN jupiter.solar.internal:8123; internal_url stays on the bare
hostname for LAN-attached devices.
Phase A only: device registration + notify group + smoke-test land in a
follow-up commit once Companion has registered real mobile_app_<slug>
service names. See docs/superpowers/specs/2026-05-18-ha-push-notifications.md.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The bare "xiaomi" component only ships the legacy IP-camera platform.
Mi Home Wi-Fi devices (vacuums, air purifiers, Yeelight, fans, etc.)
are provided by the xiaomi_miio integration.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
UI-saved automations land in /var/lib/hass/automations.yaml, but HA
won't load them unless configuration.yaml has \`automation: !include
automations.yaml\`. The Nix-managed config didn't have it, so HA's
post-save reload found no automations and timed out.
The NixOS HA module's renderYAMLFile post-processes the generated YAML
to convert quoted bang-strings into real YAML tags (see the sed step
in nixos/modules/services/home-automation/home-assistant.nix), so a
plain Nix string is enough — no escape-hatch needed.
Pre-create the three include targets via systemd.tmpfiles so HA
doesn't fail at startup if the user hasn't saved anything yet.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
HA expects \`name\` and \`unit_system\` as keys of the top-level
\`homeassistant:\` block, not as top-level integration names. Recent HA
versions tightened config validation, so this surfaced as
"Integration 'unit_system' not found" / "Integration 'name' not found"
warnings, blocking the automation reload that runs after saving an
automation in the UI.
Pre-existing bug, unrelated to OTBR — surfaced now because automation
edits trigger strict validation. Bonus: NixOS auto-populates
\`time_zone\` from the system locale once \`homeassistant\` is a real block.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Nabu Casa's prebuilt OpenThread RCP image for the ZBT-2
(zbt2_openthread_rcp_2.7.2.0_GitHub-fb0446f53_gsdk_2025.6.2.gbl)
runs at 460800 baud, not the module's 115200 default. Aligns the
radio URL with the firmware so otbr-agent can actually open the
Spinel link after rebuild.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Brings up otbr-agent against the ZBT-2 over Spinel/UART, opens the
REST API on :8081, and wires HA's otbr + thread integrations so
Matter-over-Thread devices can commission through the existing
matter-server.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Pulls the services.openthread-border-router NixOS module directly from
nixpkgs-unstable since it isn't in 25.11 yet. Service stays disabled
in this commit; configuration follows.
Also promotes `self` from `_module.args` to `specialArgs` in
machines/configuration.nix, since `imports` are evaluated before
`config` and so can't reach `_module.args.self`.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds the `zha` extra component so Home Assistant can drive the
Nabu Casa Connect ZBT-2 radio, and puts the `hass` service user in
`dialout` so it can open `/dev/serial/by-id/usb-Nabu_Casa_..._ZBT-2_*`.
Pairing is then handled through the standard ZHA wizard in the HA UI.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
extraComponents only installs packages; mobile_app needs to be declared
in configuration.yaml to actually load.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
finn.markwitz
marthsincemelee