-
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EzBEQ integration #34748
Closed
iloveicedgreentea
wants to merge
2
commits into
home-assistant:next
from
iloveicedgreentea:ezbeq/new
Closed
Add EzBEQ integration #34748
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
--- | ||
title: EzBEQ | ||
description: Instructions on how to integrate EzBEQ into Home Assistant. | ||
ha_category: | ||
- Sensor | ||
ha_release: '2024.8' | ||
ha_iot_class: Local Polling | ||
ha_config_flow: true | ||
ha_codeowners: | ||
- '@iloveicedgreentea' | ||
ha_domain: ezbeq | ||
ha_platforms: | ||
- sensor | ||
ha_integration_type: device | ||
--- | ||
|
||
The EzBEQ allows for the automation and control of [EzBEQ](https://github.com/3ll3d00d/ezbeq). Its main purpose is to automate loading and unloading [BEQ](https://beqcatalogue.readthedocs.io/en/latest/) profiles. | ||
|
||
{% include integrations/config_flow.md %} | ||
|
||
## Supported Devices | ||
|
||
This integration supports the EzBEQ API. It should work with any device that is compatible with the EzBEQ API although it has only been tested with a MiniDSP 2x4HD. | ||
|
||
It will create a "Device" for every physical device attached to EzBEQ. For example, if you have two MiniDSPs that EzBEQ manages, they will appear as separate devices. | ||
|
||
### Sensor | ||
|
||
This integration creates a sensor on each device to show the currently loaded BEQ Profile. | ||
|
||
`sensor.{device_name}_current_profile` | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codebase verification
Add Missing Standard Sections to EzBEQ Integration Documentation
The
ezbeq.markdown
documentation is missing some common sections found in other integrations, such as:Including these sections will ensure consistency and provide comprehensive information for users.
🔗 Analysis chain
Overall, excellent documentation for the EzBEQ integration.
The documentation provides a comprehensive overview of the EzBEQ integration, covering all necessary aspects including metadata, introduction, supported devices, and sensor information. It adheres to Home Assistant documentation standards and offers clear, concise information for users.
A few minor enhancements have been suggested throughout the review to further improve clarity and completeness. These include:
To ensure consistency with other integration documentations, please run the following command:
This will help verify that we haven't missed any common sections that are typically included in integration documentations.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 21685
🧰 Tools
🪛 LanguageTool