Review fixture 03 · Source-mapped · Independent human review pending T-052 / Profile 03
artificially.cloud
Directory
T-052
04 sources

Published recordSources checked

Technologies / Device records and system repair

Home Assistant Device Registry + Repairs

Home Assistant already gives connected devices stable records and surfaces some problems that need attention. It does not manage repairs for the rest of your life.

Canonical record
technology-home-assistant-registry-repairs

Sources checked


Next review

01 / Identity
Two internal records

Canonical profile

A device can have a page. A problem can have a next step.

Home Assistant’s Device Registry and Repairs are separate parts of the same open-source home-automation project. The registry organizes devices and their entities. Repairs surfaces issues that Home Assistant or an integration has identified inside the Home Assistant instance. Together, they let Home Assistant show both the device and the problem attached to it.

Object type
Device registry + internal issue registry and repair flows
Responsible project
Home Assistant, a project of the Open Home Foundation
Domain
Open-source home automation and device integration
Human system
Home operation, configuration, maintenance, and support
Geography
Software project with global use; integration and device availability vary
Verified scope
Devices and services registered by integrations; issues raised within a Home Assistant instance
Access
Included within Home Assistant; hardware, installation, integrations, and optional services vary
Last verified

What is established

A useful model for devices and the problems attached to them.

The Device Registry groups related entities into device records and can attach names, manufacturer, model, firmware, area, hub relationships, and other metadata supplied by integrations. Repairs presents issues that need attention and may offer a repair flow or instructions.

What is not established

It is not a service desk for everything you own.

The official documentation does not establish a system for condo work orders, RV service, vehicle repair, watercraft maintenance, contractor dispatch, estimates, invoices, insurance, payment, or a complete ownership history across providers.

02 / State
Four dimensions

Technology state · as of 17 Oct 2026

Available is not universal.

Both systems are documented parts of Home Assistant. Their usefulness depends on what integrations identify, how completely those integrations describe devices, and whether an issue belongs to Home Assistant’s technical world at all.

Development
Maintained project capabilitiesCurrent project and contributor documentation covers both registries and their integration-facing behavior.
Availability
Included within Home AssistantThe Repairs integration is documented as enabled by default; device records depend on installed integrations and their data.
Adoption
Not independently assessed hereProject analytics and download counts are not treated as evidence of active, complete, or representative use.
Lifecycle
Active and version-sensitiveIntegration behavior, issue types, metadata, and repair flows can change with Home Assistant and the connected system.

03 / Ledger
Claims and limits

Capability / limitation

The record stops where Home Assistant stops.

The left side records what official documentation supports. The right side names the wider ownership work it does not establish.

C-01 · Documented capability

The registry groups entities into devices people recognize.

A temperature sensor, humidity sensor, and battery can appear as entities of one physical device. Device records can carry model, manufacturer, firmware, area, identifiers, connections, and hub relationships when the integration provides them.

Sources Device Registry · Create devices quality rule

L-01 · Material limitation

An integration record is not a complete asset record.

The documentation does not supply purchase, title, warranty, inspection, insurance, contractor, invoice, or resale history. A physical device configured through two integrations may appear twice because records are scoped to their configuration entry.

C-02 · Documented capability

Repairs shows problems that need attention.

An integration can raise an issue for something requiring attention, such as old firmware, an API shutdown, or unsupported configuration. An issue may explain the next step or open a repair flow.

Sources Repairs user guide · Repairs contributor documentation

L-02 · Material limitation

A repair issue is not a contractor work order.

The mapped record does not establish diagnosis of physical damage, service-provider assignment, scheduling, estimates, parts, entry permission, payment, or verification that a real-world repair was completed.

C-03 · Documented capability

Issues can say how serious a problem is, where it came from, and whether the app can help fix it.

Contributor documentation defines an issue domain and ID, severity, whether a repair flow is available, an optional affected configuration entry, a breaking version, and whether the issue survives restart.

Source Repairs contributor documentation

L-03 · Material limitation

The system only knows what its integrations report.

A leaking valve, cracked hull, weak RV air conditioner, or empty washer-fluid reservoir does not become a Home Assistant issue merely because its owner cares about it. The observation needs a sensor, integration, or manual record somewhere else.

04 / Boundary
Record chain

From device to obligation

The record works until the fix has to happen outside Home Assistant.

Home Assistant can organize an integrated technical system. The broader service relationship usually begins where that internal record ends.

  1. 01 / DocumentedIntegration registersA configured integration supplies device identity and related entities.
  2. 02 / DocumentedRegistry groupsHome Assistant presents the entities as a named device in an area or topology.
  3. 03 / DocumentedSystem detectsHome Assistant or an integration creates an issue requiring attention.
  4. 04 / ConditionalRepair flow guidesSome issues can be fixed in the interface; others only explain what to do.
  5. 05 / Not establishedPhysical service completesNo universal contractor, dealer, property-manager, estimate, payment, or completion record follows from these capabilities.

The distinction matters for the linked Manager for Your Things interface. A Home Assistant issue can inform an ownership record. It should not be presented as proof that the wider repair was diagnosed, scheduled, or completed.

05 / Operations lens
04 record verbs

What Manager for Your Things can borrow

Identify. Group. Flag. Guide.

These verbs show what the Ownership Ledger can borrow from Home Assistant. They are an editorial reading tool, not official Home Assistant terminology or a claim of universal service capability.

  1. 01

    Identify

    An integration supplies identifiers, connections, names, models, versions, and related metadata.

  2. 02

    Group

    The registry gathers related entities into a device and can place it in an area or behind a hub.

  3. 03

    Flag

    An issue says something needs attention, how serious it is, and which integration reported it.

  4. 04

    Guide

    The issue may explain a remedy or open a repair flow, within the limits of the integration.

06 / Evidence Margin
04 official records

Provenance and absence

The sources are direct. The larger frame is ours.

All four sources come from the Home Assistant project. They directly establish documented behavior and developer contracts; they are not independent evaluation of reliability, adoption, security, or household benefit.

Support
Official user and contributor documentation supports the described registry fields, grouping behavior, issues, and repair flows
Agreement
Consistent across project user and contributor documentation; independent agreement not assessed
Directness
Direct for documented software behavior; indirect for everyday usefulness and service outcomes
Independence
Low; every attached source is published by the project being profiled
  1. source-ha-device-registryDevice RegistryHome Assistant Contributors · integration architecture and registry behavior
  2. source-ha-create-devicesCreate devicesHome Assistant Contributors · Gold quality rule and device metadata guidance
  3. source-ha-repairs-userRepairsHome Assistant · user-facing issue and repair-dashboard behavior
  4. source-ha-repairs-contributorsRepairs — integration documentationHome Assistant Contributors · issue fields, severity, persistence, and repair flows

07 / Present → Proposed

From integrated device records to a wider ownership ledger.

Manager for Your Things borrows one simple idea: keep a reliable page for the thing and another for the problem. It does not claim Home Assistant connects to it or plans to manage the rest of your possessions.

  1. / Present

    Connected devices get a page of their own.

    Home Assistant can group entities, metadata, areas, topology, and some technical issues inside one instance.

    Inspect the documented boundary →
  2. Adjacent precedent / Present

    Repairs for Linden Court, the Dutch Star, Roadster, and Sea-Doo still live in different places.

    Maintenance requests, appointments, manuals, dealer records, and physical work live in separate systems with different authority.

    Read the fragmented record →
  3. Interface study / Not a product claim

    One owner gets one honest to-do list.

    The proposed ledger keeps manual observations first-class and labels connected updates by source and freshness.

    Open Manager for Your Things →

What would change this record?

Questions for the next review.

Scheduled for , or earlier after a material registry, repairs, integration, security, or correction record.

  1. 01

    Do new device or integration contracts change how one physical asset is identified across systems?

  2. 02

    Which integrations expose lifecycle, diagnostic, or service information rather than momentary device state?

  3. 03

    Can an issue carry evidence of a physical repair without confusing a report, diagnosis, action, and outcome?

  4. 04

    How are issue permissions and visibility handled in multi-person households?

  5. 05

    What happens to device and issue records when an integration, account, vendor, or household changes?

  6. 06

    What independent evidence measures comprehension, accessibility, missed issues, false alerts, and recovery?

Related concept and story

Atlas — Try Manager for Your Things →

Story — Read why the records remain fragmented →

Related placement describes an editorial relationship. It does not assert endorsement, interoperability, or technical lineage.