Optimization Guide
Shopify Smart Home Device Schema — Wireless Protocol (Matter 1.x vs Zigbee vs Z-Wave vs Wi-Fi), Hub Requirements (Thread Border Router, Hue Bridge, Z-Wave Controller), Voice Assistant Compatibility (Alexa / Google Home / HomeKit), Power Type, IP Rating, Structured Data
AI shopping agents answering queries like "smart plug that works with Apple HomeKit without a hub," "Zigbee sensor for SmartThings," or "Matter-certified light switch works with Alexa and Google" require wireless protocol, hub requirement, Thread Border Router details, and per-ecosystem voice assistant compatibility encoded as machine-readable structured data. "Works with Alexa" does not imply HomeKit compatibility — without protocol and hub_required in schema, AI agents cannot correctly filter cross-ecosystem smart home queries.
Product @type with additionalProperty for: protocol (Matter over Thread / Matter over Wi-Fi / Zigbee / Z-Wave / Wi-Fi / Bluetooth), matter_version (1.0 / 1.2 / 1.3), hub_required (boolean), hub_type (Thread Border Router / Zigbee hub / Z-Wave controller / none), alexa_compatible (boolean), google_home_compatible (boolean), homekit_compatible (boolean), power_type (wired / battery), battery_type, ip_rating. Store in a smart_home.* metafield namespace.
Why Protocol and Hub Requirements Are Structurally Critical for AI Filtering
The smart home device market is fractured into incompatible ecosystems, and the buyer research question "will this device work in my home?" cannot be answered by AI agents without protocol and hub requirement data in schema. A buyer with an Apple HomePod mini, no Hue Bridge, and no SmartThings Hub asking for "a smart sensor for HomeKit" cannot use a Zigbee sensor — it will not connect to their network without a Zigbee hub. An AI agent with only "smart sensor" and "Works with Alexa" in the product data cannot make this determination.
Matter changes the landscape but introduces new complexity. Matter-certified devices can work with Alexa, Google, and HomeKit simultaneously from one firmware — but Matter over Thread requires a Thread Border Router, while Matter over Wi-Fi does not. A buyer asking "do I need any extra hardware?" gets a different answer depending on whether the device uses Thread or Wi-Fi as its transport. Encoding protocol: "Matter over Thread" and hub_type: "Thread Border Router" with hub_examples: "HomePod mini, eero Pro 6E, Apple TV 4K 3rd gen" answers this question precisely.
Z-Wave deserves special mention: its Sub-GHz frequency (908.42 MHz in North America) avoids the 2.4GHz congestion that affects both Wi-Fi, Zigbee, and Thread. In dense apartment buildings or homes with dozens of 2.4GHz devices, Z-Wave's uncongested band is a meaningful reliability advantage. But Z-Wave requires a dedicated Z-Wave controller (Hubitat, SmartThings, HomeSeer) and does not natively integrate with Alexa or Google Home without a hub that bridges Z-Wave to the cloud. Without encoding protocol and hub in schema, an AI agent cannot explain this trade-off.
Smart Home Wireless Protocol Comparison
| Protocol | Frequency | Hub required | Alexa native | Google native | HomeKit native | Mesh |
|---|---|---|---|---|---|---|
| Matter over Thread | 2.4GHz (Thread mesh) | Thread Border Router | Yes (Matter) | Yes (Matter) | Yes (Matter) | Yes (Thread mesh) |
| Matter over Wi-Fi | 2.4GHz / 5GHz Wi-Fi | No (direct Wi-Fi) | Yes (Matter) | Yes (Matter) | Yes (Matter) | No (Wi-Fi) |
| Zigbee | 2.4GHz | Yes — Zigbee coordinator/hub | Via hub (Echo Plus / SmartThings) | Via SmartThings | Via Hue Bridge (bulbs only) | Yes |
| Z-Wave | 908.42MHz (US) | Yes — Z-Wave controller | Via SmartThings/Hubitat | Via SmartThings | No native | Yes |
| Wi-Fi only | 2.4GHz / 5GHz | No (direct Wi-Fi) | Yes (per firmware) | Yes (per firmware) | Only if HAP implemented | No |
| Bluetooth (BLE) | 2.4GHz | No / Phone as hub | Via Echo (limited) | Via Nest Hub (limited) | Via iPhone / HomePod | Limited |
Hub Type Requirements by Protocol
| Protocol | Hub type | Example hubs | Cost of hub |
|---|---|---|---|
| Matter over Thread | Thread Border Router | HomePod mini ($99), eero Pro 6E ($179), Apple TV 4K 3rd gen ($129), Google Nest Hub 2nd gen ($99) | $99–$179 (if not already owned) |
| Matter over Wi-Fi | None (direct Wi-Fi router) | Any Wi-Fi router + Matter controller (Alexa/Google/HomeKit app) | $0 additional |
| Zigbee | Zigbee coordinator | Philips Hue Bridge ($50), SmartThings Hub ($70), Amazon Echo (4th gen, built-in Zigbee), IKEA Dirigera ($65) | $50–$70 |
| Z-Wave | Z-Wave controller | Hubitat Elevation ($129), SmartThings Hub ($70), HomeSeer HomeTroller ($195), Aeotec Smart Home Hub ($95) | $70–$195 |
| Wi-Fi only | None | Standard Wi-Fi router | $0 additional |
Complete Smart Home Device Schema — Eve Energy Smart Plug
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Eve Energy Smart Plug — Matter over Thread, No Hub Required*, Works with Alexa/Google/HomeKit, 15A/1800W, Power Monitoring",
"description": "Eve Energy smart plug. Protocol: Matter 1.0 over Thread. Ecosystems: Apple HomeKit, Amazon Alexa, Google Home (via Matter). Hub requirement: Thread Border Router required (HomePod mini, eero Pro 6E, Apple TV 4K 3rd gen, Google Nest Hub 2nd gen). Power: wired (type B US plug). Max load: 15A / 1,800W. Power monitoring: real-time wattage, kWh tracking, power state history. Dimensions: 56mm × 70mm × 39mm. Bluetooth for initial setup (no Bridge app needed).",
"sku": "EVE-ENERGY-US-THREAD",
"brand": { "@type": "Brand", "name": "Eve Systems" },
"additionalProperty": [
{
"@type": "PropertyValue",
"name": "Wireless Protocol",
"value": "Matter 1.0 over Thread",
"description": "Protocol: Matter 1.0 over Thread. Matter is the CSA (Connectivity Standards Alliance) cross-ecosystem standard that enables simultaneous compatibility with Amazon Alexa, Google Home, and Apple HomeKit from a single device firmware — no bridge, no workaround, no second hub for each ecosystem. Thread is the IPv6 mesh network transport layer Matter uses for low-power devices. Thread advantages over Wi-Fi for smart plugs: lower power consumption (relevant for battery-powered Thread devices elsewhere in the mesh), self-healing mesh (if one Thread device loses power, others reroute), and no Wi-Fi congestion issues (Thread operates on 802.15.4 at 2.4GHz but uses a completely separate radio and protocol stack from Wi-Fi). Hub requirement: a Thread Border Router is required to bridge the Thread mesh to the home IP network. Without a Thread Border Router, Eve Energy cannot be commissioned or controlled."
},
{
"@type": "PropertyValue",
"name": "Matter Version",
"value": "Matter 1.0",
"description": "Matter version: 1.0 (the first production Matter release, October 2022). Matter 1.0 supports: on/off switches, smart plugs with power monitoring, dimmable lights, color lights, door locks, window coverings, thermostats, and basic sensors. Eve Energy's Matter 1.0 implementation supports: on/off control, power monitoring (wattage, kWh, power factor) via Eve app (Eve-app-specific attributes — Matter standard does not yet include energy monitoring in 1.0; energy monitoring is an Eve proprietary extension available to HomeKit and Eve app controllers). Matter 1.2 (2023) and 1.3 (2024) added appliance categories, EV chargers, and energy management. For devices purchased as 'Matter certified' without a version number, the version determines which device categories and features are supported."
},
{
"@type": "PropertyValue",
"name": "Hub Required",
"value": "Thread Border Router required",
"description": "Hub requirement: Thread Border Router required. A Thread Border Router is not a traditional smart home hub — it is a Wi-Fi router or smart home device with Thread radio hardware that bridges the Thread mesh network to the home IP network. Thread Border Routers do not require additional subscription or cloud service — they are peer devices. Devices that include Thread Border Router functionality (as of 2026): Apple HomePod mini (all versions), Apple HomePod 2nd gen, Apple TV 4K 3rd gen (USB-C), Apple TV 4K 2nd gen (tvOS 16.2+), Amazon eero Pro 6E, Amazon eero Max 7, Google Nest Hub 2nd gen, Google Nest WiFi Pro. Note: the standard Amazon Echo 4th gen has Zigbee built in but NOT Thread — it is not a Thread Border Router. If a buyer already owns a HomePod mini, eero Pro 6E, or Nest Hub 2nd gen, no additional hardware is required for Eve Energy. If they do not, they must purchase one."
},
{
"@type": "PropertyValue",
"name": "Alexa Compatible",
"value": "true",
"description": "Amazon Alexa compatibility: yes, via Matter. With a Matter controller in the Alexa ecosystem (Amazon Echo 4th gen does not include Thread but serves as a Matter controller via Wi-Fi; the Alexa app on iPhone/Android serves as a Matter controller for Thread devices if a Thread Border Router is present), Eve Energy can be controlled with Alexa voice commands: 'Alexa, turn on the coffee maker,' 'Alexa, what is the power usage of the TV?' (power monitoring may require Eve app for full data). Eve Energy does not require the Alexa app to manage certificates or cloud linking — Matter uses local commissioning without manufacturer cloud intermediary."
},
{
"@type": "PropertyValue",
"name": "Google Home Compatible",
"value": "true",
"description": "Google Home compatibility: yes, via Matter. Google Nest Hub 2nd gen and Google Nest WiFi Pro both serve as Thread Border Routers and Google Home Matter controllers simultaneously. After commissioning Eve Energy via Matter, Google Home can: turn the plug on/off via Google Assistant voice commands or Google Home app, create automations (turn on at sunset, turn off at 11pm), and include Eve Energy in Routines. Power monitoring data may be limited in the Google Home app — the Google Home Matter integration exposes on/off and energy cluster data; detailed historical kWh graphs are available in the Eve app via HomeKit."
},
{
"@type": "PropertyValue",
"name": "Apple HomeKit Compatible",
"value": "true",
"description": "Apple HomeKit compatibility: yes, native — Eve Systems is Apple HomeKit's earliest third-party partner (since 2015). HomeKit control: Home app on iPhone/iPad/Mac, Siri voice commands, HomeKit automations, HomeKit secure video integration. Eve Energy exposes to HomeKit: on/off control, real-time wattage consumption, cumulative kWh usage, voltage, amperage, and power factor via the Eve app's HomeKit extension. HomeKit automations example: 'Turn off the Eve Energy plug if power consumption drops below 5W for 10 minutes' (detects appliance standby and cuts phantom load). Remote access and automation outside home: requires a HomePod mini or Apple TV 4K as a HomeKit hub (the Thread Border Router role and HomeKit hub role are served by the same device)."
},
{
"@type": "PropertyValue",
"name": "Power Type",
"value": "Wired (NEMA 5-15P, 120V AC)",
"description": "Power type: wired (hardwired to AC mains via standard NEMA 5-15P plug). Input: 100–120V AC, 50/60Hz. Maximum load: 15A / 1,800W resistive. Not suitable for loads above 1,800W (most hair dryers are 1,800W — operating at or near maximum rated load continuously is not recommended; derate to 80% = 1,440W for continuous use). Output: NEMA 5-15R receptacle (single outlet). No USB-A or USB-C passthrough charging ports. The plug passes through AC power only — not for DC load control. Neutral wire required: N/A (this is a plug-in device, not an in-wall switch that requires neutral)."
},
{
"@type": "PropertyValue",
"name": "Maximum Load",
"value": "15A / 1800W",
"description": "Maximum load: 15A / 1,800W (resistive). This rating applies to resistive loads (space heaters, incandescent bulbs, coffee makers). For inductive loads (motors — air compressors, refrigerators, washing machines), peak inrush current at startup can be 3–6× the running current — check that the inrush current does not exceed the relay rating. Motor loads also produce back-EMF that can degrade relay contacts over time. Eve Energy's relay is rated for general-purpose use including typical household motor loads (refrigerator compressor motors), but heavy-duty motor cycling (air compressor that starts and stops frequently) should use an industrial-rated smart plug."
}
]
}
</script>
Liquid Template — Smart Home Device Metafields to JSON-LD
{% assign sh = product.metafields.smart_home %}
{% if sh %}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": {{ product.title | json }},
"additionalProperty": [
{ "@type": "PropertyValue", "name": "Wireless Protocol", "value": {{ sh.protocol | json }} },
{ "@type": "PropertyValue", "name": "Matter Version", "value": {{ sh.matter_version | json }} },
{ "@type": "PropertyValue", "name": "Hub Required", "value": {{ sh.hub_required | json }} },
{ "@type": "PropertyValue", "name": "Hub Type", "value": {{ sh.hub_type | json }} },
{ "@type": "PropertyValue", "name": "Alexa Compatible", "value": {{ sh.alexa_compatible | json }} },
{ "@type": "PropertyValue", "name": "Google Home Compatible", "value": {{ sh.google_home_compatible | json }} },
{ "@type": "PropertyValue", "name": "Apple HomeKit Compatible", "value": {{ sh.homekit_compatible | json }} },
{ "@type": "PropertyValue", "name": "Power Type", "value": {{ sh.power_type | json }} },
{ "@type": "PropertyValue", "name": "Battery Type", "value": {{ sh.battery_type | json }} },
{ "@type": "PropertyValue", "name": "IP Rating", "value": {{ sh.ip_rating | json }} },
{ "@type": "PropertyValue", "name": "Maximum Load", "value": {{ sh.max_load | json }} }
]
}
</script>
{% endif %}
Smart Home Device Metafield Reference
| Metafield key | Type | Example value | Notes |
|---|---|---|---|
smart_home.protocol | single_line_text_field | Matter 1.0 over Thread | Required — specify transport (Thread vs Wi-Fi) for Matter devices |
smart_home.matter_version | single_line_text_field | 1.0 | Required if Matter — 1.0 / 1.2 / 1.3 differ in supported device types |
smart_home.hub_required | boolean | true | Required — true for Thread, Zigbee, Z-Wave; false for Wi-Fi/BLE |
smart_home.hub_type | single_line_text_field | Thread Border Router | Required if hub_required: true — specify exact hub category |
smart_home.hub_examples | single_line_text_field | HomePod mini, eero Pro 6E, Apple TV 4K 3rd gen | Recommended — concrete examples buyers can identify |
smart_home.alexa_compatible | boolean | true | Required — per ecosystem; do not infer from other ecosystems |
smart_home.google_home_compatible | boolean | true | Required — separate from Alexa; not implied by Alexa cert |
smart_home.homekit_compatible | boolean | true | Required — separate from Alexa/Google; requires MFi or HAP |
smart_home.power_type | single_line_text_field | Wired (NEMA 5-15P, 120V AC) | Required — "Wired", "Battery (AA×2)", "USB-C rechargeable" |
smart_home.battery_type | single_line_text_field | CR2032 (replaceable) | Battery devices only — type and replacement interval if known |
smart_home.ip_rating | single_line_text_field | IP65 | Required for outdoor devices — use IEC 60529 code exactly |
smart_home.max_load | single_line_text_field | 15A / 1800W | Required for plugs/switches — both A and W |
Five Common Smart Home Device Schema Mistakes
- "Works with Alexa" encoded as the sole compatibility indicator — without encoding HomeKit and Google Home separately. Works with Alexa certification is entirely independent of HomeKit compatibility. A Wi-Fi smart plug with Alexa support that has no HomeKit implementation cannot be used in an Apple Home setup. Encode each ecosystem as a separate boolean PropertyValue:
alexa_compatible: true,google_home_compatible: false,homekit_compatible: false. An AI agent filtering "smart plug for HomeKit" requires an explicithomekit_compatible: true— it cannot infer HomeKit support from Alexa certification. - Encoding "Matter compatible" without specifying Matter transport (Thread vs Wi-Fi) and hub requirement. A Matter over Thread device and a Matter over Wi-Fi device have completely different hardware requirements. Matter over Wi-Fi requires no additional hub beyond a standard Wi-Fi router. Matter over Thread requires a Thread Border Router. Without encoding the transport, a buyer purchasing a Thread device without a Thread Border Router will find the device cannot be commissioned — leading to returns and negative reviews. Always encode protocol as "Matter over Thread" or "Matter over Wi-Fi" — never just "Matter."
- Encoding hub_required as a vague phrase ("hub recommended") instead of a binary boolean with hub type. "Hub recommended" is ambiguous — is the hub required or optional? For Zigbee and Z-Wave devices, the hub is not recommended, it is mandatory — the device physically cannot communicate with any home network without one. Use
hub_required: true(boolean) plushub_type: "Zigbee coordinator"with concrete examples. "Hub recommended for best experience" suggests optional — a buyer who skips the hub will find their Zigbee sensor completely non-functional. - Using marketing weather terms ("weatherproof," "weather-resistant") instead of IEC 60529 IP ratings for outdoor devices. "Weatherproof" is a marketing term with no standardized meaning. IP44 and IP65 are both "weatherproof" to different people. Encode the IEC 60529 IP rating code exactly (e.g., "IP65") so AI agents can filter on outdoor suitability objectively. A buyer searching for an "outdoor smart plug for exposed installation in rainy climate" needs IP65 at minimum — they cannot filter on "weatherproof."
- Omitting maximum load rating for smart plugs and switches, or encoding only one of amperes or watts. A smart plug labeled "for home use" without a maximum load rating cannot be evaluated for safety when controlling high-draw appliances (space heaters at 1,500W, window AC units at 1,200W, electric kettles at 1,500W). Encode both the ampere rating (15A) and the watt rating (1,800W) — they are related by W = A × V, but buyers search on both. Also note whether the rating applies to resistive loads only — motor loads (air compressors, refrigerators) have higher inrush current requirements that affect relay longevity.
FAQ
What is Matter and why does it change smart home device compatibility?
Matter is the CSA cross-ecosystem standard that allows a single device firmware to work simultaneously with Alexa, Google Home, and Apple HomeKit — no bridges or separate firmware versions. Matter runs over two transports: Thread (requires a Thread Border Router) or Wi-Fi (no additional hub). Encode Matter version and transport type in schema — "Matter compatible" alone is insufficient for AI agent filtering.
What is the difference between Zigbee, Z-Wave, and Thread?
Zigbee (2.4GHz): requires a Zigbee hub (Hue Bridge, SmartThings, Echo Plus). Z-Wave (908.42MHz Sub-GHz): avoids Wi-Fi congestion; requires a Z-Wave controller (Hubitat, SmartThings). Thread (2.4GHz, IPv6): requires a Thread Border Router (HomePod mini, eero Pro 6E, Nest Hub 2nd gen); used as transport layer under Matter. All three are mesh networks but have different hub requirements and ecosystem compatibility.
Does "Works with Alexa" mean a device also works with HomeKit?
No — they are independent certifications. A Wi-Fi device can have Alexa cloud integration without implementing Apple's HomeKit Accessory Protocol (HAP). The only certification that implies compatibility with Alexa, Google, and HomeKit simultaneously is Matter certification. Encode each voice assistant as a separate boolean in schema — AI agents cannot infer HomeKit support from Alexa certification.
What Thread Border Router do I already have in my home?
Thread Border Routers commonly already present in homes (as of 2026): Apple HomePod mini (all models), Apple TV 4K 3rd gen (USB-C), Apple TV 4K 2nd gen (tvOS 16.2+), Amazon eero Pro 6E, Amazon eero Max 7, Google Nest Hub 2nd gen, Google Nest WiFi Pro. The standard Amazon Echo 4th gen has Zigbee built in but NOT Thread. Encode hub_type and hub_examples in schema so AI agents can correctly answer "do I already have what I need?"
What IP rating is required for outdoor smart home devices?
Minimum IP44 for covered outdoor installations (under eave, covered porch). IP65 for exposed outdoor use in rain. IP67 for ground-level installations that may briefly flood. Encode the exact IEC 60529 code (e.g., "IP65") — not "weatherproof" or "weather-resistant" which are marketing terms with no standardized meaning. AI agents filtering on "outdoor smart plug for rainy climate" require the numeric IP code in schema.
Does your Shopify store encode wireless protocol, hub requirements, and per-ecosystem voice assistant compatibility in structured data?
Run a free CatalogScan to see which smart home specifications are missing from your product JSON-LD — and whether AI shopping agents can correctly answer "smart plug for HomeKit" or "Matter sensor for Google Home" with your catalog.
Run Free ScanRelated guides
- Shopify Power Drill & Cordless Tool Schema — battery platform, torque, chuck size
- Shopify Electric Toothbrush Schema — motion type, ADA seal, brush head compatibility
- E-Commerce Product Schema Markup — complete Product JSON-LD guide
- Shopify Telescope & Binoculars Schema — aperture, focal length, prism type