60 searchable, copy-ready Node-RED prompts

Prompt 01: Build a four-layer version matrix that distinguishes the Home Assistant Community Add-on, the Node-RED runtime, node-red-contrib-home-assistant-websocket, and FlowFuse Dashboard. Verify each installed version against its exact tag or commit, explain how the layers relate, and flag any version that cannot be proven. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 02: Compare the release notes for each relevant pinned component with its source at the exact tag or commit. Report added, changed, deprecated, and removed behavior; separate documented facts from source-based inferences; and call out any discrepancy between the release notes and pinned source. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 03: Determine which product layer owns [FEATURE_OR_SETTING]: the Home Assistant Community Add-on, Node-RED core, node-red-contrib-home-assistant-websocket, or FlowFuse Dashboard. Trace the setting from its user-facing label to the implementing documentation or source file, and explain which project should receive an issue. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 04: Verify that FlowFuse Dashboard is optional, is not bundled with Home Assistant Community Add-on v22.0.1, and must be installed separately. Inspect the pinned add-on package/configuration sources and the Dashboard installation documentation, then list the exact checks that can confirm its presence without installing or upgrading anything. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 05: Prepare a pre-upgrade drift inventory. Compare [INSTALLED_VERSIONS] with the four pinned versions, include custom palette packages and configuration-schema changes, classify each difference as expected or unexplained, and identify compatibility checks and rollback prerequisites before any upgrade. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 06: Create a pre-installation checklist for Home Assistant Community Add-on v22.0.1. Cover supported Home Assistant installation type and architecture, repository access, storage and backup needs, required network dependencies, and the evidence that each prerequisite is satisfied; do not instruct the reader to install the add-on. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 07: Audit the add-on's configuration schema and container capabilities at tag v22.0.1. For every requested option, compare config.yaml, build/runtime scripts, and official add-on documentation; state the accepted type/default, whether restart is required, and why any capability or host access is needed. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 08: Compare Home Assistant Ingress with direct Node-RED access for this add-on. Explain URL routing, authentication boundary, TLS termination, exposure to untrusted networks, and operational trade-offs, then recommend the least-exposed design that satisfies [ACCESS_REQUIREMENT] without changing the environment. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 09: Draft a credential-encryption and TLS plan for the add-on and Node-RED. Distinguish Node-RED's credential secret from TLS private keys and service tokens, identify supported configuration locations at the pinned versions, and include generation, storage, rotation, backup, and recovery checks without displaying secret material. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 10: Produce a read-only diagnostic decision tree for an add-on that will not start. Order checks across Supervisor/add-on logs, schema validation, file permissions, Node.js startup, palette dependencies, credential decryption, ports, and resource limits; for each branch, give the expected evidence and a safe stopping condition. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 11: Write a concise orientation to the Node-RED editor's workspace, palette, Information/Debug sidebars, configuration nodes, and Deploy menu. Include a no-deploy exercise that lets a new operator inspect a flow and identify modified nodes without causing runtime side effects. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 12: Compare the Full, Modified Flows, and Modified Nodes deployment modes in Node-RED v5.0.2. Explain what each mode restarts, how shared configuration nodes can widen impact, when in-flight state may be lost, and which evidence should govern the safest choice for [CHANGE_SET]. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 13: Create a pre-deployment review for [CANDIDATE_FLOW]. Compare it with the approved export by node ID and property, and review wires, configuration nodes, disabled state, credentials, environment references, and side-effect paths. End with an explicit GO/STOP recommendation; do not deploy. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 14: Diagnose a node that shows disconnected. First identify whether its status comes from a Home Assistant server config, MQTT broker config, or another node, then correlate status text with scoped Status-node output and logs. Provide non-destructive checks for URL/DNS, authentication, TLS, and reconnect behavior. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 15: Design a safe flow-import procedure. Require review of the JSON before import, redaction of secrets and identifiers, verification of node types and configuration nodes, and disabling Inject nodes and every external side-effect path before the first deployment. Include an isolated test and a rollback gate. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 16: Explain the Node-RED message contract for msg.payload, optional msg.topic, and _msgid. Show how to inspect types with a Debug node, preserve unrelated properties through transformations, avoid relying on _msgid as a durable business identifier, and define the input/output schema for [FLOW_STEP]. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 17: Design type-safe routing with Change and Switch nodes for [INPUT_SCHEMA]. Validate property existence and type before comparisons, distinguish numeric, Boolean, and string values, provide an otherwise/rejection output, and specify Debug-based tests for missing, null, malformed, and valid inputs. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 18: Define a Split/Join contract for [COLLECTION_SHAPE]. Document every msg.parts field relied upon, preservation of msg.parts through intermediate nodes, ordering and correlation rules, completion behavior when count is unknown, timeout handling, and tests for interleaved sequences. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 19: Compare node, flow, and global context in Node-RED v5.0.2. Explain visibility, lifetime, subflow behavior, synchronous versus asynchronous store access, and named stores, then choose the narrowest scope for [STATE] and explain why secrets should not be placed in context. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 20: Plan persistent context and restart verification for [STATE]. Confirm the configured context store from settings, document the localfilesystem cache/flush behavior at the pinned version, define acceptable loss windows, and provide controlled restart and corruption-recovery tests without changing production. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 21: Choose between the Events: state and Events: all Home Assistant nodes for [EVENT_REQUIREMENT]. Compare event scope, filter precision, output shape, startup behavior, and event volume at node-red-contrib-home-assistant-websocket v0.80.3, then define tests using redacted sample events. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 22: Design a Current State decision for [ENTITY_PLACEHOLDER]. Specify when the state is evaluated, the exact property and type to compare, handling for unknown, unavailable, missing, and stale states, output routing, and a no-action rejection path. Do not call a Home Assistant action. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 23: Design a Get Entities query for [SELECTION_CRITERIA]. Use only filters and output options supported by v0.80.3, define the result's type and destination property, handle zero/one/many matches explicitly, and prevent broad queries from accidentally feeding an action node. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 24: Define the minimum validated input contract for an Action node at v0.80.3. Separate action, target, and data; allowlist the intended domain/action and target shape; reject missing or templated values that escape policy; and keep the Action node disabled while showing redacted positive and negative test messages. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 25: Design a Wait Until flow with a bounded wait for [STATE_CONDITION]. Specify whether the current state is checked on input, the timeout duration and units, success and timeout outputs, cancellation/retrigger behavior, and safe recovery so that a timeout can never fall through to an external action. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 26: Create one JSONata proposal that converts the redacted Home Assistant event sample [EVENT_SAMPLE] into [OUTPUT_SCHEMA]. Derive paths from the actual v0.80.3 node output rather than assuming them, preserve required metadata, and include expressions/tests for valid, missing, unavailable, and type-mismatched values. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 27: Review [JSONATA_EXPRESSION] for missing values and type safety. Explain the difference between an absent path, null, an empty sequence, and false/zero; guard conversions and comparisons; and provide a table of sample inputs and exact outputs or errors using the JSONata behavior available in Node-RED v5.0.2. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 28: Write one pure Function-node proposal for [TRANSFORMATION]. Define the input and output message schemas, avoid context, network, filesystem, timers, and nondeterministic state, preserve unrelated message properties, reject invalid input explicitly, and include executable sample messages with expected results. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 29: Review [FUNCTION_CODE] against Node-RED v5.0.2 message cloning and return/send semantics. Check single and multiple outputs, arrays of messages, node.send cloning behavior, asynchronous completion with node.done, error handling, and accidental mutation of shared nested objects; cite the exact documentation or source for each conclusion. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 30: Compare implementing [TRANSFORMATION] in a Change node with JSONata versus a Function node. Evaluate readability, type/error handling, testability, performance, team maintenance, and pinned-version support, then recommend one implementation and provide only that single proposed expression or function. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 31: Design one disabled HTTP In test endpoint for [TEST_CASE]. Pair every path with HTTP Response, define method/path, request validation, body-size and content-type expectations, authentication boundary, status codes, and a non-production test command; keep the endpoint inert until an explicit review and deployment gate. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 32: Audit an outbound HTTP Request path for [UPSTREAM]. Verify URL construction, allowlisting, method, headers, TLS validation, response parsing, timeout behavior supported by Node-RED v5.0.2, and Catch/statusCode handling. Permit retries only for demonstrably idempotent operations and require bounded backoff. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 33: Map every branch from an HTTP In node to exactly one HTTP Response node. Preserve the request/response object required by Node-RED, define success, validation, authentication, upstream-error, and timeout responses, prevent duplicate responses, and include a test matrix proving that no branch hangs. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 34: Design one disabled MQTT in/out example for [USE_CASE]. Use separate clearly named client configuration where appropriate, placeholder broker credentials, an allowlisted publish topic, explicit QoS and retain choices, payload validation, and a test-only topic namespace; explain how to verify it without contacting a production broker. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 35: Audit the MQTT broker, topic, and TLS placeholders for [MQTT_CONFIGURATION]. Validate scheme/host/port, client ID policy, authentication, CA trust, certificate hostname verification, MQTT version, QoS, retain behavior, and reconnect settings. Reject wildcard characters in publish topics and explain subscription wildcard scope. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 36: Inventory the backup scope for Node-RED flows, encrypted credentials, settings, installed palette dependencies, and Home Assistant add-on configuration. Distinguish what a flow export omits from what an add-on/Home Assistant backup captures, and record the credential-secret dependency needed for restoration. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 37: Plan an isolated restore drill for [BACKUP_SET]. Require a disposable environment with production network egress blocked, preserved encryption material, pinned dependencies, integrity checks, and substituted Home Assistant/MQTT endpoints. Define restoration success, cleanup, and STOP gates before any production use. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 38: Compare a Node-RED flow export with a complete Home Assistant backup that includes the add-on. List configuration, credentials, context data, custom modules, add-on options, and runtime data as included, excluded, or version-dependent, citing pinned evidence and avoiding any claim that an export is a full backup. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 39: Define a verifiable pre-update restore point for [PLANNED_UPDATE]. Include backup scope, timestamp/version manifest, checksum, encryption-key availability, offline copy/access controls, isolated restore evidence, rollback trigger, and owner approval; do not begin the update. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 40: Audit backup handling for secret exposure. Identify which artifacts may contain encrypted or plaintext credentials, tokens, private URLs, entity IDs, and certificates; verify encryption, access control, retention, transport, and deletion; and report metadata only, never secret values. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 41: Scan [REDACTED_FLOW_JSON] for secrets and identifying data without echoing findings. Cover inline Function/template values, headers, URLs, MQTT credentials, entity/device IDs, coordinates, configuration nodes, and environment references; return locations, severity, and placeholder-based remediation only. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 42: Audit whether all side-effect paths in [FLOW_JSON] are disabled. Include Home Assistant Action, MQTT out, HTTP Request, Exec, e-mail, file-write, database, notification, and Inject-triggered paths; account for Link and Subflow connections; and report the exact nodes that must remain disabled before testing. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 43: Create a least-privilege deployment matrix for Node-RED and Home Assistant access. Distinguish Node-RED adminAuth read versus full permissions, Ingress/access controls, runtime service credentials, and approval ownership; state explicitly where the pinned products do not provide per-flow or per-node authorization. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 44: Review [PALETTE_PACKAGE] before installation. Verify exact npm package/version, publisher and repository provenance, integrity/lock data, license, maintenance history, Node.js/Node-RED compatibility, transitive dependencies, known advisories, requested capabilities, and a removal/rollback plan; do not install it. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 45: Create a publication checklist for screenshots. Require masking of hostnames, URLs, tokens, user names, entity/device IDs, coordinates, QR codes, Debug payloads, and browser/account chrome; remove image metadata and hidden layers; and require a second-person review of the final exported image. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 46: Define a reproducible baseline for message rate and end-to-end latency in [FLOW]. Specify workload, warm-up, sampling window, percentile metrics, drops/errors, CPU, memory, event-loop delay, and instrumentation overhead. Use synthetic data and define thresholds before collecting results. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 47: Audit [FUNCTION_CODE] for event-loop blocking in Node-RED v5.0.2. Check unbounded loops, large synchronous parsing/serialization, expensive regular expressions, synchronous I/O, excessive cloning, and per-message setup; estimate workload assumptions and propose one bounded, testable remediation. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 48: Design rate limiting with the Delay node for [TRAFFIC_PROFILE]. Verify the exact v5.0.2 queue/drop options rather than inventing a maximum-queue setting; define rate, burst behavior, ordering, overflow policy, memory bound, and observability. If the core node cannot enforce the bound, propose one explicit gate-and-drop strategy. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 49: Audit context-store load for [STATE_USAGE]. Measure key size, read/write frequency, scope, store, localfilesystem flush behavior, and restart durability; identify write amplification and event-loop or storage risk; then recommend narrower state or lower write frequency with measurable acceptance limits. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 50: Plan a Home Assistant disconnect/recovery test for v0.80.3. Simulate connection loss only in isolation, observe status/reconnect timing, queue or loss behavior, stale state, duplicate events, and guarded actions after recovery; require fresh-state validation before any side effect can resume. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 51: Build a symptom-led decision tree for a failed Node-RED deployment. Separate editor validation errors, unknown node types, invalid configuration nodes, credential problems, runtime startup failures, and post-deploy node errors; cite the observable signal and non-destructive next check for each branch. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 52: Troubleshoot a node-red-contrib-home-assistant-websocket connection failure without exposing tokens. Check the configured server mode/URL, Supervisor integration where applicable, DNS and routing, authentication, TLS trust/hostname, proxy WebSocket support, clock skew, version compatibility, and reconnect logs in a least-invasive order. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 53: Troubleshoot a message that does not leave a Switch node. Inspect the complete incoming message, configured property path, missing/null values, runtime type, rule order, stop-after-first-match behavior, and otherwise output; provide a minimal redacted test matrix that isolates each rule. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 54: Troubleshoot [HTTP_OR_MQTT] timeouts by separating DNS, TCP, TLS, authentication, and application/protocol stages. Define stage-specific evidence, configured timeout/reconnect semantics, proxy or broker limits, and safe synthetic probes; do not recommend disabling certificate verification or using production endpoints. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 55: Create a troubleshooting runbook that uses Debug, Catch, and Status nodes correctly. Explain what each can and cannot observe, scope them to [TARGET_NODES], preserve correlation identifiers, redact payloads, define log retention, and map each signal to a safe next action and stopping condition. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 56: Create happy-path, rejection, boundary, and failure test cases for [FLOW_CONTRACT]. Specify exact input, expected output/status, invariant, and evidence for each case; mock Home Assistant, HTTP, and MQTT dependencies; and prove that rejected inputs cannot reach disabled side-effect nodes. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 57: Produce an acceptance matrix for [REQUIREMENT]. Map each requirement to pinned-source evidence, a repeatable test, expected result, collected artifact, owner, and pass/fail/STOP status. Keep assumptions and untested items visible rather than treating missing evidence as a pass. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 58: Review all 14 example flows for safe import. Validate JSON syntax, node types, unique IDs and wires, configuration-node references, pinned palette dependencies, placeholders, credential leakage, and disabled side-effect paths; report each example separately and do not import or deploy it. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 59: Write a release-ready change summary for [CHANGE_SET]. Include purpose, affected flow/node IDs, configuration and dependency changes, migration and rollback steps, test evidence, security/operational impact, known limitations, unresolved STOP items, and the exact pinned versions used for review. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.

Prompt 60: Create a pre-delivery checklist with automated checks and explicit human gates. Cover HTML/JSON syntax as applicable, flow importability, dependency/version pins, placeholder and secret scans, disabled side effects, test evidence, backup/rollback readiness, documentation, ownership, and final no-deploy approval. Inputs: [ENVIRONMENT_VERSIONS], [REQUIREMENT], and [EXPECTED_RESULT]. Use official documentation and the exact relevant tags or commits for Home Assistant Community Add-on v22.0.1, Node-RED v5.0.2, node-red-contrib-home-assistant-websocket v0.80.3, and FlowFuse Dashboard v1.30.2; cite each material claim with a URL and section, file path, or commit, and mark irrelevant layers as not applicable. Use [PLACEHOLDER] for all environment-specific values, and never request or reveal real secrets, private URLs, or entity/device IDs. Perform read-only analysis only: do not connect to, change, or deploy any environment. If evidence or required input is missing, state what is missing and write STOP. Respond in English.