52 searchable, copyable work prompts

Plan [home/site name] for Home Assistant Matter Hub Stable 2.0.55. First inventory [HA version], [entity count], [controller list], [network segments] and [operations owner]. Identify only gaps and open questions; do not change any settings. Answer in English.

Use [entity inventory file] to define the Matter Hub adoption scope. Group items by area, domain, risk and controller, then list what to include, exclude and test on real hardware. Answer in English.

Create a phased plan from the lab to production for [site name]. For each phase, specify entry criteria, test samples, acceptance evidence, rollback point and stop conditions. Answer in English.

Compare [current architecture] with responsibilities after Matter Hub adoption. Highlight what Home Assistant, Matter Hub, the external Matter controller and the Thread Border Router each own. Answer in English.

Propose how to split bridges based on [floor/area list], [endpoint count], [controller list] and [risk tiers]. Explain each bridge’s purpose, filter boundary and failure blast radius. Answer in English.

Design durable identity and naming rules for [bridge name]. List the field changes that could create duplicate devices on the controller or require recommissioning. Answer in English.

Review [existing bridge configuration] for port conflicts, startup priority, synchronization strategy, session recovery and watchdog risks. Give recommendations only; do not make changes. Answer in English.

Plan a minimal pilot bridge for [controller name]. Select only low-risk entities from [device-type list], and list the tests that must pass before expansion. Answer in English.

Turn [requirements] into a draft Stable 2.0.55 Filter Engine rule set. Separate Include and Exclude, explain ANY/ALL evaluation, and provide expected-match and false-match examples. Answer in English.

Check whether [filter configuration] could expose too much. Analyze area, label, domain, platform, pattern and regex matchers one by one; prefer a minimal Include. Answer in English.

Create a filter test table for [area name] with [entity_id], attributes, expected inclusion/exclusion, actual result and reason for any difference. Do not assume Preview equals the controller’s final presentation. Answer in English.

Refactor [existing filter] to reduce duplicate matchers while preserving results. First list the equivalence-verification method and rollback version, then provide the draft. Answer in English.

Review Matter mapping candidates in [entity inventory]. For each, list the source domain, recommended device type, required attributes, linked entities and controller tests. Answer in English.

Plan a composed device for [primary entity] with [battery/power/energy/temperature and humidity entities] as candidate linked entities. Explain each link’s value, behavior when data is missing and debounce test. Answer in English.

Analyze [mapping failure list]. Classify missing attributes, unsupported domains, incorrect overrides, naming conflicts and unsupported controller features, then give a verifiable remediation order. Answer in English.

Compare [mapping profile A] with [mapping profile B] for [device type]. Cite only fields verified in the v2.0.55 exact tag; mark unknowns for hardware verification. Answer in English.

Create a functional acceptance matrix for [light/switch/lock/cover/climate/fan]. Include HA capability, Matter mapping, controller presentation, control, state reporting and limitations. Answer in English.

Create a read-only acceptance checklist for [sensor/binary sensor/weather/air quality/energy/battery]. Check units, device class, precision and unavailable states in particular. Answer in English.

Assess whether [media player/valve/water heater/alarm/event/robot vacuum/lawn mower] belongs in a production bridge. Distinguish v2.0.55 support, experimental status and controller-side items still requiring verification. Answer in English.

Check the feature flags for [device type]. Explain each default, reason to change it, possible controller workaround, regression tests and recovery method. Answer in English.

Write a pre-commissioning check for Apple Home and [bridge name]. Cover only the home hub, network, bridge status, low-risk test devices and de-identified evidence; do not output a pairing code. Answer in English.

Create synchronization and room-organization tests for [device-type list] in Google Home. Record app display names, controls, state reporting, voice results and unsupported items. Answer in English.

Plan first commissioning and a scale test for [bridge name] with Amazon Alexa. Add [batch size] endpoints per batch; treat every count as an environmental observation, never a universal limit. Answer in English.

Compare how Apple Home, Google Home and Amazon Alexa present [the same device set]. Report conclusions separately by controller; do not infer results for either of the others from one success. Answer in English.

Design a Matter Hub pilot for Aqara [hub model/firmware version]. List the region, device types, app presentation and basic controls to verify; do not promise compatibility in advance. Answer in English.

Create a commissioning, driver/device-type, room, control and state-reporting test table for SmartThings [hub model/firmware version]. Answer in English.

Compare verified, unverified and not-applicable items for [device-type list] on Aqara and SmartThings. Include a source or test-evidence field for every conclusion. Answer in English.

Given [controller error message], create a minimal reproduction: a single-subnet baseline, one bridge, one device type, de-identified logs and stop conditions. Answer in English.

Plan how [bridge name] will join [controller A] and [controller B] using multi-fabric. Back up first; record join order, status, owner and removal recovery method. Do not show any pairing secrets. Answer in English.

Review [fabric status summary] for orphan, session or subscription problems. Request only read-only checks and evidence; do not remove anything or reset. Answer in English.

Design a multi-fabric regression test. Operate [device] in [controller A], verify state reporting in [controller B] and HA, and record latency, offline and reconnection results. Answer in English.

Write a change plan for removing [specified fabric], including impact assessment, approval, backup, downtime notice, post-change verification and recovery on failure. Do not execute it. Answer in English.

Use [network topology] to check Matter Hub, controller, VLAN, IPv6, mDNS and firewall prerequisites. Provide the test order without requesting private IP addresses or hostnames. Answer in English.

Build a diagnostic tree for [device not found during commissioning]. Check service status first, then IPv6, mDNS, cross-VLAN behavior, Wi-Fi/Thread and the controller. State the expected evidence at each step. Answer in English.

Analyze [de-identified mDNS test result]. Distinguish absent advertisements, cross-subnet failure, firewall-blocked replies, name-resolution problems and application-layer errors. Answer in English.

Write base-path and authentication checks for [reverse proxy/Ingress path]. Treat Basic Auth only as a single authentication layer; do not infer multi-account access, RBAC or SSO. Answer in English.

Using [de-identified Health summary], rank possible causes across the HA connection, bridge, fabric, session, subscription, mDNS and resource use. Start with nondestructive checks. Answer in English.

Analyze [de-identified System Logs] for [time range]. Group repeated messages, identify the first root-cause candidate and cascading errors, and note where more evidence is needed. Answer in English.

Create a minimal troubleshooting runbook for [No Response symptom]. Isolate the controller, bridge, HA entity and network layer by layer; do not use reset as the first step. Answer in English.

Create an operations baseline for [bridge name]: startup time, synchronization time, endpoint count, memory, error rate, sessions and controller response. Use [threshold] as the threshold placeholder. Answer in English.

Review the attack surface of [deployment design]: management interface, Ingress, reverse proxy, Basic Auth, IP allowlist, plugins, API, WebSocket and secret storage. List remediation by severity. Answer in English.

Check [document/screenshot list] for QR payloads, manual pairing codes, setup PINs, discriminators, fabric/node IDs, tokens, cookies, credentials, private IP addresses or hostnames. Report locations only; do not repeat secrets. Answer in English.

Design a minimal-exposure policy for [safety-critical entity list]. Separate readable, controllable, human-confirmed and prohibited exposure, and include an exception-approval process. Answer in English.

Review whether [change plan] includes backup, impact, recovery and authorization before plugin installation, reset, restore or fabric removal. Block execution when any item is missing. Answer in English.

Inventory plugins, the REST API, WebSocket, health and metrics in Stable 2.0.55. For each, state its source, release channel, maturity, verification method and whether it is experimental. Answer in English.

Write a security review for installing [plugin package placeholder]: source, version, integrity, permissions, schema, secrets, circuit breaker, disablement, removal and recovery. Do not install it. Answer in English.

Design a least-privilege, read-only-first call flow for [API requirement]. Use placeholders for every URL, token, header and identifier; handle errors and rate limits. Answer in English.

Create an observation test for [WebSocket event]. Record connection, subscription, event format, reconnection and sensitive-field redaction. Do not describe callback architecture as a Stable feature. Answer in English.

Define the Stable 2.0.55 backup scope for [deployment method: add-on/Docker/npm], including persistent configuration, bridge identity, assets, plugin data and external dependencies. Check the exact tag before naming unknown paths. Answer in English.

Design a restore drill for [bridge name]: verify that the backup is readable, create an isolated environment, restore, compare identity and endpoints, then test the controller. Do not run Restore directly in production. Answer in English.

Write a downtime plan for migrating from [old host] to [new host]. Include version pinning, data copy, network identity, verification, rollback and fabric risks; do not output secrets. Answer in English.

Create a disaster-recovery table for [upgrade/corruption/accidental deletion scenario] with RPO [target], RTO [target], owner [role], steps, evidence and failure-declaration criteria. Answer in English.