Document sensor.integration.set_value action#6208
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughDocumentation was added for the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/content/docs/components/sensor/integration.mdx`:
- Line 56: The span element currently has an incorrect id
"sensor-integration-set__value_action" (double underscore); update the id to
"sensor-integration-set_value_action" to match the action name and restore
correct deep-linking behavior, ensuring any references to this anchor elsewhere
(e.g., links or tests) are updated to the new id as needed.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7bd8c9a3-b0d4-4056-9599-588186803f7c
📒 Files selected for processing (1)
src/content/docs/components/sensor/integration.mdx
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![esphome[bot]](https://avatars.githubusercontent.com/in/247347?s=60&v=4){kind=small}
There was a problem hiding this comment.
As this is a feature matched with a PR in https://github.com/esphome/esphome, please target your PR to the next branch and rebase.
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
There was a problem hiding this comment.
As this is a feature matched with a PR in https://github.com/esphome/esphome, please target your PR to the next branch and rebase.
There was a problem hiding this comment.
As this is a feature matched with a PR in https://github.com/esphome/esphome, please target your PR to the next branch and rebase.
Added documentation for the `sensor.integration.set_value` action, including an example of setting a specific value for the integration sensor.
Updated the span ID for the sensor integration set value action.
There was a problem hiding this comment.
Pull request overview
Adds documentation for the sensor.integration.set_value action in the Integration Sensor docs, and also updates the documentation site’s tracked ESPHome release/changelog to 2026.2.4.
Changes:
- Document
sensor.integration.set_valueaction, including YAML example and configuration options. - Add a “Release 2026.2.4” section to the 2026.2 changelog.
- Bump
data/version.yamlrelease from2026.2.3to2026.2.4.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
src/content/docs/components/sensor/integration.mdx |
Adds a new section documenting the sensor.integration.set_value action and its options. |
src/content/docs/changelog/2026.2.0.mdx |
Appends a new 2026.2.4 patch release entry. |
data/version.yaml |
Updates the tracked release number to 2026.2.4. |
You can also share your feedback on Copilot code review. Take the survey.
Added documentation for the
sensor.integration.set_valueaction, including an example of setting a specific value for the integration sensor.Description
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable):
Checklist
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/src/content/docs/components/index.mdxwhen creating new documents for new components or cookbook.New Component Images
If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.
To generate a component image:
Comment on this pull request with the following command, replacing
component_namewith your component name in lower_case format with underscores (e.g.,bme280,sht3x,dallas_temp):The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.
Extract the SVG file and place it in the
/public/images/folder of this repository.Use the image in your component's index table entry in
/src/content/docs/components/index.mdx.Example: For a component called "DHT22 Temperature Sensor", use:
Note: All images used in ImgTable components must be placed in
/public/images/as the component resolves them to absolute paths.