Adding documentation for idle mode for SPS30 sensor #3913
Closed
Conversation
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
esphome#3884) Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
* Set SN74HC165's clock_inhibit_pin as optional The use of only 3 pins is mentioned, but the configuration values don't reflect that. Datasheet specifies the pin can be directly connected to ground. The code already expects the pin to not be used: https://github.com/esphome/esphome/blob/ec3162282cd5a2c3455dd7a8669b4f762c481a20/esphome/components/sn74hc165/__init__.py#L35 * Update sn74hc165.rst * Update sn74hc165.rst --------- Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
… usage (esphome#3723) Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
Update to the Addressable Color Wipe Example to correctly include gradient as an option of the color rather than the entire effect
Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
* doc: wifi reboot_timeout disabled if ap enabled * Update wifi.rst * Update wifi.rst --------- Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
…esphome#3762) * Update template.rst * Update template.rst
…e#3771) It's probably clear to most people that setting up a trigger for the 31st of every month will fail in February, but apparently triggers between 1am and 3am are also fragile once a year. For non-disruptive or regular triggers, this might not be an issue -- if you want to turn off a device at 2am using on_time, you should know that it will fail once a week. Similarly, if you want to do a daily trigger at 1am, you should know that it will trigger twice a day once a year. This does not seem super-obvious until you've run into it, so I propose adding a note to the documentation. It also doesn't feel like something that should be changed in the functionality to match cron's behavior, given that it would change the functionality of existing triggers. I'm not invested in the exact wording / location; I suspect pulling it out a bit into a more visible place makes it less likely for people to miss. (Brought to you by a trigger that turns off an expensive device at 2am, only for it to run a full day instead :-)).
This Example has previously not been referenced and had been misplaced at the top of the variants.
* Improve SGP30 compensation documentation * Use must instead of should, fix celsius spelling
…#3446) * Add Seeed Studio XIAO ESP32S3 Sense pins to esp32_camera.rst Added camera pin configuration for Seeed Studio XIAO ESP32S3 Sense to Camera page * Added missing blank line * Update esp32_camera.rst --------- Co-authored-by: H. Árkosi Róbert <robreg@zsurob.hu>
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
13 tasks
|
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. |
|
This is still waiting for review.
…On Sat, Aug 3, 2024, 6:51 PM github-actions[bot] ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#3913 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFPT7N2PGZAWT2VFE72D5KLZPWCLJAVCNFSM6AAAAABIY4SMF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRXGIZTQOJZGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description:
Adding documentation for idle mode for SPS30 sensor.
Related issue (if applicable): fixes esphome/feature-requests#2133
Pull request in esphome with YAML changes (if applicable): esphome/esphome#6828
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
/index.rstwhen creating new documents for new components or cookbook.