-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[esp32_rmt] Enable pullup and od mode based on pin scheme #4634
base: next
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
WalkthroughThis pull request updates versioning information in configuration files and documentation, reflecting a new development version (2025.1.0-dev) while also modifying build and redirect configurations. Numerous documentation pages have been updated to clarify configuration variables, add new sections for audio components, BLE server functionality, and a web API for an alarm control panel, and to remove deprecated custom component content. Overall, the changes standardize version references, enhance documentation clarity, and consolidate outdated material. Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant WebAPI
Client->>WebAPI: GET /alarm_control_panel/my_alarm
WebAPI-->>Client: JSON { id, state, value }
Client->>WebAPI: POST /alarm_control_panel/my_alarm/arm_home (with optional code)
WebAPI-->>Client: 200 OK
Possibly related PRs
Suggested labels
Suggested reviewers
✨ Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Caution
Inline review comments failed to post. This is likely due to GitHub's limits when posting large numbers of comments.
Actionable comments posted: 1
🧹 Nitpick comments (11)
components/text_sensor/uptime.rst (1)
1-8
: Refine Title and Introductory Text
The new file introduces the "Uptime Text Sensor" well. However, in line 8 the sentence “Theuptime
text sensor provides a human-readable representation the time since boot.” is slightly off grammatically. Consider changing it to “...provides a human-readable representation of the time since boot.”components/remote_receiver.rst (1)
Line range hint
505-513
: New note on enabling pull-up resistors.
A very welcome note has been added regarding receivers such as the TSOP38238 that may require a pull-up resistor. The provided YAML snippet clearly demonstrates how to configure the pin (includinginverted
,input: true
, andpullup: true
).Suggestion: It might be useful to mention that the need for a pull-up resistor should be verified against the receiver’s datasheet since some boards might already have internal pull-ups enabled.
components/audio_adc/index.rst (4)
9-11
: Component Description Overview
The description concisely explains what theaudio_adc
component does. Consider mentioning specific supported ADC models or common use cases to further guide users.
12-17
: YAML Example Placeholder
The YAML code block provides a basic configuration example. For enhanced guidance, you might consider expanding the example with realistic placeholder values.
34-49
: Automations Documentation Detailingaudio_adc.set_mic_gain
The section on the automation action is well structured, specifying required fields with clarity. Enhancing it with an example automation workflow could further benefit users.
50-53
: See Also Section
The ‘See Also’ block is brief and functional. Revisit whether additional related references or external resources might be added to enrich the section.components/audio_dac/es8156.rst (1)
35-67
: Detailed Configuration Examples
The examples for the ESP32 S3 Box 3 Lite are comprehensive, illustrating the integration of multiple components (audio_dac, i2s_audio, speaker, and switch). Verify that the pin configurations and component identifiers reflect the current hardware recommendations.components/audio_adc/es7243e.rst (2)
15-20
: YAML Example for ES7243E
The YAML configuration example is succinct and illustrates the basic setup for the ES7243E. Consider adding another example that includes more parameters for a comprehensive guide.
38-62
: Comprehensive Configuration Examples
The configuration example for the ESP32 S3 Box Lite is thorough, covering multiple interconnected components. Double-check that the pin assignments and sample values match the latest recommended configurations for clarity and accuracy.components/audio_adc/es7210.rst (2)
15-20
: YAML Configuration Example Overview
The provided YAML snippet offers a clean, starter configuration example. Enhancing it with additional context or parameters could further improve user understanding.
36-40
: Automations Support Note
The confirmation that all Audio ADC automations are supported is helpful. A brief pointer to an example automation could be a nice enhancement in future revisions.
🛑 Comments failed to post (1)
components/udp.rst (1)
293-316:
⚠️ Potential issueResolve Variable Naming Inconsistency in Multicast Example
In the multicast example, the configuration key is written aslisten_addresses
, while in the configuration variables section it is defined aslisten_address
(singular). This inconsistency could confuse users. Please confirm the intended option name and update either the configuration documentation or the example accordingly.
Description:
Update docs for esphome/esphome#8178
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable): esphome/esphome#8178
Checklist:
I am merging into
next
because this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
current
because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/index.rst
when creating new documents for new components or cookbook.