AiHummer
English▾
Sign inAccount
v1.6.x▾
{ }Swagger

Home Assistant configuration and diagnosis

v1.6.x · updated 2026-11-15

Connect your own Home Assistant instance through Connections, using its exact URL and your account’s long-lived access token. Keep certificate verification enabled. An operator must explicitly permit the intended private-network destination where required; do not allow every host.

Discover before changing

Ask the agent to inspect current capabilities, entities, devices, areas and available services. REST access and authenticated event or registry access are checked separately. Partial access is not full support. Event observations may contain reconnect gaps and are not a complete historical log.

Read the current entity state and actual service before commanding a device. Editing a remembered state does not operate the physical device. A service acknowledgement also needs an appropriate follow-up observation.

Edit one selected configuration

Select one automation, script, supported helper or dashboard view. Read its current configuration and inspect the proposed changes. The initial helper editor supports boolean helpers; unsupported helper types must be reported explicitly.

Before a supported write, a complete private backup must be saved. If configuration was redacted, its shortened display is not a complete restoration source. A changed configuration requires a fresh review. Home Assistant does not provide a transaction covering all outside editors, so a concurrent edit or partially completed rename must remain visible.

After saving, read back the selected configuration. Readback does not prove completed reload, disk persistence, a triggered automation or a device outcome. For a dashboard, open the affected view through an available authorized browser and inspect its actual appearance. No browser session or visual success is invented when preview is unavailable.

Investigate before renaming or repairing

For an entity rename, scan references first and review the proposed target, selected sources and unverified regions. Only understood structural references are updated. Templates, custom cards, omitted files and unavailable sources are not globally rewritten by text search. Keep the backup and inspect partial results before continuing.

For “why did this automation not run?”, supply the exact automation and time interval. Current configuration, retained traces, history and supporting logs are different evidence. Missing traces do not prove that it never ran. For calendar comparisons, check the statistic, unit, time zone, interval and available data before interpreting a difference. Reading statistics does not repair recorder data.

After an uncertain write, inspect the original operation and current state before repeating it. A configuration backup or copied reference never supplies another person’s Home Assistant permissions.