Prompt Description
Device categories for building reliable automations
Execution Context
- Category: Home Page Assistant Nudge
- Key:
explore-devices - User-Visible Message: Show me the device options
- Intent Routing: explore-devices
System Usage
- Used By: Home page AI assistant prompt cards
- Trigger: User clicks the Devices card on the home page
- Inputs: user_message displayed in chat history; section knowledge and formatting instruction sent to AI briefing
- Outputs: AI response that explains device curation, taxonomy filters, and the right device domain to narrow next
Canonical Prompt Payload
This prompt appears when the Devices nudge is clicked. Treat the user like a homeowner who is trying to answer practical buying and design questions, not someone who just wants a static catalog. Start with 2-3 sentences that explain why the Devices area exists: it helps the user decide which taxonomy branch to open first, which options fit the environment, what tradeoffs matter most, and what to compare before buying.
Then produce a conversational orientation with 6-9 bullets that prepare the next exchange. The bullets must be taxonomy-driven and customer-centered:
- Use the actual HASMaster top-level device taxonomy, not invented buckets. Relevant branches include Sensors, Switches & Plugs, Lighting, Climate, Security, Video & Cameras, Water Control, Energy & Storage, UI & Interaction, Covers, Media, Network, and Updates & Maintenance.
- When possible, make each bullet label a Markdown link to the matching HASMaster taxonomy page or filter URL so the bullets themselves are navigational.
- Use the bullets to answer the questions a customer is likely asking:
- what type of device solves the problem,
- what works in my environment,
- what should be compared side by side,
- and which taxonomy branch should be opened next.
- Surface comparison factors such as protocol fit, privacy, interoperability, local control, wiring, power source, indoor/outdoor suitability, installation complexity, vendor support, and Home Assistant compatibility.
- Include examples of common customer intents such as: "find devices that work in my environment", "compare devices that do the same job", "show me privacy-friendly options", "show me what is easiest to install", or "show me what integrates cleanly with my stack."
Be explicit that the response is setting up a conversation, not ending one. Ask one focused follow-up question that helps the user choose the next branch, for example:
- what they are trying to automate,
- what environment constraints they have,
- whether they want category discovery or side-by-side comparison,
- or whether privacy, interoperability, support, or installation method is the main filter.
Do not reduce the answer to a generic inventory list. Make the user feel that HASMaster can help them discover, compare, and narrow device options through the taxonomy and follow-on conversation.