-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Waveshare I/O Expander (ch32v003) #5334
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
base: next
Are you sure you want to change the base?
Conversation
|
@esphomebot generate image WAVESHARE_IO_CH32V003 |
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.
Pull Request Overview
This PR adds documentation for the new Waveshare CH32V003 I/O Expander component, which provides GPIO expansion capabilities through an I²C-connected microcontroller module.
- Creates comprehensive documentation for the new component including configuration examples and pin usage
- Adds the component to the index page for discoverability
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| content/components/waveshare_io_ch32v003.md | Complete documentation for the new Waveshare CH32V003 I/O expander component |
| content/components/_index.md | Adds the new component entry to the components index table |
|
@latonita Here is the image for the component https://github.com/esphome/esphome-docs/actions/runs/17476960724/artifacts/3931729613 |
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@esphomebot generate image WAVESHARE_IO |
|
@latonita Here is the image for the component https://github.com/esphome/esphome-docs/actions/runs/17477083966/artifacts/3931773391 |
|
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions. |
|
waiting for review |
|
Hi @latonita, there are some lint and build errors, maybe this is blocking review? Would love to see this added since my 7B board is arriving soon. Where can I help, apart from checking that it works for that board at least? |
Description:
Related issue (if applicable): fixes esphome/feature-requests#3202
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
/components/index.rstwhen 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 UPPER_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
images/folder of this repository.Use the image in your component's index table entry in
/components/index.rst.Example: For a component called "DHT22 Temperature Sensor", use: