Add Zooz integration page #39709
Add Zooz integration page #39709
Conversation
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
There was a problem hiding this comment.
Pull Request Overview
This pull request adds a new integration page for Zooz that provides users with information about connecting and controlling Zooz Z-Wave series devices, along with relevant metadata for Home Assistant.
- Adds a new Zooz integration documentation file
- Provides metadata and a link to the Zooz website
Comments suppressed due to low confidence (1)
source/_integrations/zooz.markdown:12
- The integration description references Zooz Z-Wave devices, but the iot_standard is set to matter. Please confirm whether this field is correct or update it to reflect the intended standard.
ha_iot_standard: matter
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughA new documentation file for the Zooz brand integration has been added. This file provides metadata and descriptive content about Zooz Z-Wave device support in Home Assistant, specifying requirements, supported platforms, and integration details. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant HomeAssistantDocs
User->>HomeAssistantDocs: Accesses Zooz integration documentation
HomeAssistantDocs-->>User: Displays metadata and integration details
User->>HomeAssistantDocs: Follows link for more Z-Wave info
HomeAssistantDocs-->>User: Provides Z-Wave integration documentation
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
source/_integrations/zooz.markdown (2)
3-3: Minor wording tweak for clearer description“series devices” is redundant. A shorter description fits better in search previews:
-description: Connect and control your Zooz Z-Wave series devices using the Z-Wave integration +description: Connect and control your Zooz Z-Wave devices using the Z-Wave integration
16-16: Grammar improvement (“happening” → “done”)-Zooz Z-Wave devices work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required). As all connectivity is happening locally, status updates and controlling your devices happen instantly in Home Assistant. +Zooz Z-Wave devices work locally and integrate seamlessly with the Z-Wave integration in Home Assistant (Z-Wave stick required). Because all communication is local, status updates and control commands are applied instantly.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
source/_integrations/zooz.markdown(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`source/_integrations/*`: Integration documentation must use the provided template structure and section order.
source/_integrations/*: Integration documentation must use the provided template structure and section order.
📄 Source: CodeRabbit Inference Engine (.github/copilot-instructions.md)
List of files the instruction was applied to:
source/_integrations/zooz.markdown
🪛 LanguageTool
source/_integrations/zooz.markdown
[grammar] ~18-~18: Did you mean “Z-Wave” (= wireless protocol)?
Context: ...instantly in Home Assistant. {% my add_zwave_device badge domain=page.ha_domain %} ...
(Z_WAVE)
🔇 Additional comments (2)
source/_integrations/zooz.markdown (2)
12-12: Use the canonical slug for Z-Wave standardThe accepted slug in other brand pages is
zwave_js, notzwave.
Please verify and align with existing pages to keep filtering consistent.
18-18: ```shell
#!/bin/bashSearch for macro file with underscore after “z”
fd -I add_z_wave_device --extension njk
List all Zwave-related macro files to confirm the correct name
fd -I zwave --extension njk
</details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
| --- | ||
| title: Zooz | ||
| description: Connect and control your Zooz Z-Wave series devices using the Z-Wave integration | ||
| ha_release: '2025.7' | ||
| ha_iot_class: Local Push | ||
| ha_category: | ||
| - Lock | ||
| ha_domain: zooz | ||
| ha_integration_type: brand | ||
| ha_platforms: | ||
| - lock | ||
| ha_iot_standard: zwave | ||
| ha_brand: true | ||
| --- |
There was a problem hiding this comment.
YAML front-matter order doesn’t follow the mandated template
source/_integrations/* pages must keep the exact key order defined by the brand-page template.
Please reorder the keys (and keep the 2-space indents for list items) to avoid the build bot rejecting the page.
Typical order for a brand page:
title
description
ha_release
ha_integration_type
ha_iot_standard
ha_domain
ha_iot_class
ha_category
ha_platforms
ha_brand
🤖 Prompt for AI Agents
In source/_integrations/zooz.markdown lines 1 to 14, the YAML front-matter keys
are not in the mandated order required by the brand-page template. Reorder the
keys to follow this exact sequence: title, description, ha_release,
ha_integration_type, ha_iot_standard, ha_domain, ha_iot_class, ha_category,
ha_platforms, ha_brand, while preserving the 2-space indentation for list items.
Proposed change
Add Zooz integration page
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit