Adds documentation for new integration BirdNET-Go - #47934
Conversation
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
🟢 Approval recommended
The added integration page follows existing Home Assistant integration doc structure and includes the key setup, entity, update, and removal details.
Pull request overview
Adds a new integration documentation page for the BirdNET-Go integration, describing setup via config flow and the sensors it provides.
Changes:
- Added a new integration page with front matter (domain, platforms, iot class, quality scale, release).
- Documented config flow fields (host/port/SSL/auth) using
config_flowandconfiguration_basic. - Documented provided sensors, polling interval, and standard removal steps.
File summaries
| File | Description |
|---|---|
| source/_integrations/birdnet_go.markdown | New documentation page covering configuration, sensors, polling cadence, and removal for the BirdNET-Go integration. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
🔵 Needs a closer look
The integration page is missing the required “BirdNET-Go automation examples” section expected by the current integration documentation template.
Review details
Suppressed comments (1)
Previously missed (1) — in code that hasn't changed since the last review.
source/_integrations/birdnet_go.markdown:52
- The integration documentation template expects an automation examples section ("## BirdNET-Go automation examples") before Data updates, with example headings starting with "### Automation:". Adding this section helps readers understand practical ways to use the provided sensors in automations.
- Files reviewed: 1/1 changed files
- Comments generated: 0 new
- Review effort level: Lite
There was a problem hiding this comment.
🟡 Changes recommended
The added automation YAML examples include a template that can error and hard-coded entity IDs that likely won’t match reader installations.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
source/_integrations/birdnet_go.markdown:94
- This entity ID is unlikely to match a reader’s installation because BirdNET-Go entities are named from the config entry title/device name. Use a placeholder entity ID so readers know they must select their own entity.
- trigger: numeric_state
entity_id: sensor.birdnet_go_station_detection_streak
above: 6
- Files reviewed: 1/1 changed files
- Comments generated: 2
- Review effort level: Lite
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
One of the included automation YAML examples is invalid due to a condition being placed under triggers: instead of conditions:.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
source/_integrations/birdnet_go.markdown:80
- This
message:line is long for an example block and is hard to read; using a folded scalar keeps the YAML within typical line-length rules and makes the template clearer.
title: "New bird species identified"
message: "A new bird species was recorded! Total lifetime species: {{ trigger.to_state.state }}."
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Proposed change
Adds documentation for new integration BirdNET-Go
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.