Integrator · principal

The path for the next house.

A thin visual layer over systems already in the house. The estate manager or integrator works from a short checklist — the principal does not need to be on site.

Audience

Estate managers and integrators

Time

About 25 minutes, after the tunnel

Principal

Need not be on site

Privacy

Neutral hostnames only

Sitting checklist

Six quiet ticks.

  1. 01Cloudflare Tunnel
  2. 02HACS custom repository — Patrimony HA
  3. 03Mint the pairing QR
  4. 04Pair in iOS — Scan QR
  5. 05Verify Offline vs stale on the card
  6. 06Optional — invite a second person
Why this order

Reachable first. Then paired.

The iPhone talks to the house, not to a telemetry cloud. Live state stays on that residence’s Home Assistant. The tunnel makes HA reachable over HTTPS without opening router ports. The custom component issues the pairing QR. The app only scans it.

Architecture: family mobile devices, secure tunnel, Home Assistant, smart home systems, optional api.patrimonycollection.com and Apple APNs

01

Reachable

Cloudflare Tunnel

Give this house a stable https:// hostname. Do not open port 8123 on the router.

Follow the illustrated customer guide: Prepare Home Assistant for remote access.

When you are done, a phone that is not on house Wi‑Fi should see the Home Assistant login page at the published URL.

Use a neutral hostname — for example ha.example.com or house-02.example.com. Do not put a town, island, or property name in the public URL. Do not send location-revealing IP addresses.

Each residence needs its own tunnel hostname. Do not reuse another house’s URL or tunnel token.

02

HACS

Install the custom component

Patrimony Collection is a Home Assistant custom integration. It is added as a HACS custom repository (Integration category), not from the HACS default store.

Add https://github.com/lindystudio/patrimony-ha as a HACS custom repository (Integration).

Do not add unofficial forks. If HACS cannot fetch the repository, write to us rather than improvising a download. The public repository README is the source of truth for labels that move with Home Assistant versions.

If HACS is not installed — download it from the official instructions for your HA type, then restart and finish HACS setup. We do not repeat those steps here: hacs.xyz — Downloading HACS.

Add the custom repository (standard HACS path):

  1. Open HACS in Home Assistant
  2. Open the three-dot menu (top right) → Custom repositories
  3. Repository URL: https://github.com/lindystudio/patrimony-ha
  4. Set the type to Integration
  5. Choose Add

Those five clicks match the HACS custom-repositories FAQ. After the repository is listed:

  1. Find Patrimony in HACS and download it
  2. Restart Home Assistant
  3. Add the integration under Settings → Devices & services

Once it is loaded, Patrimony appears in the Home Assistant sidebar. If the repository README shows a shorter or newer path, follow the README. When the integration supports it, principals can enable optional PQ Shield from the iPhone Connections screen.

03

Pairing

Mint the pairing QR

The custom component issues a pairing QR for this house. The iOS app does not ask you to type a long-lived password into a form.

  1. Open Patrimony in Home Assistant
  2. Mint a pairing QR for this residence, following the current labels in the component README
  3. Keep the QR on the house screen — or print it for the sitting — until the principal has scanned it
Treat the QR as short-lived and single-house. Do not reuse a code from another residence. Do not drop a photo of it into a shared album. If it expires or fails, mint a fresh one. We do not invent button names here; they belong to the component.

04

iOS

Claim it in the pocket

Access is by invitation. The principal (or an authorised household user) already has the app.

  1. Open Patrimony Collection and sign in with Apple
  2. Add this residence
  3. Scan QR — the camera reads the pairing code minted at the house
  4. Confirm the new card appears in the wallet

House-connection credentials stay in the iPhone Keychain. The camera is used only for this scan. Live home state remains on that house’s Home Assistant — see Privacy.

If the principal is not on site, the integrator holds the QR until they can scan it on a call, then discards it.

05

Card

Offline vs stale

The sitting is not done when the card appears. Stay on it for a moment.

  1. The wallet shows Offline when the house is unreachable, or last heard is missing
  2. It shows Stale when last heard is older than about five minutes

A quiet OK card means the house is reachable and fresh — not a frozen snapshot.

Once the house is live, the badge reads severity from the mapping — Severity on the pass.

If the card stays Offline, or last heard never leaves Stale, the tunnel or the component is not reaching this house. Recheck the tunnel from a phone that is not on house Wi‑Fi before minting another QR.

06

Optional

A second person

If another phone should hold this house, the principal creates a code. The guest Signs in with Apple and accepts — no email is required. One sitting can stop at the principal’s card.

Treat an invite like the QR — short-lived, this house only.

—

Handoff

What to keep private

If you need to write to us, send only what onboarding requires. Examples on this site are placeholders.

ItemExample
Home Assistant URLhttps://ha.example.com
Second househttps://house-02.example.com
NotesTunnel via Cloudflare; HACS custom repository (Integration) — https://github.com/lindystudio/patrimony-ha
Never sendTunnel tokens, pairing QR photos, city or property hostnames, public IPs