esphome / esphome/feature-requests

Make SDS011 play nice with PollingComponent

Open
#2,539 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**
I would like to trigger the sds011 sensor from my time component.

**Please describe your use case for this integration and alternatives you've tried:**
Example of use:
```time:
- platform: sntp
id: sntp_time
timezone: Europe/Amsterdam
on_time:
- seconds: 0
minutes: /5
then:
- component.update: shtc3_sensor
```
This works well for all the sensors in this project, but the moment you try with with the sds011 it seems not to be supported:
`ID 'sds011_sensor' of type sds011::SDS011Component doesn't inherit from PollingComponent. Please double check your ID is pointing to the correct value.`

**Additional context**
It works well with a set interval in the sds011 settings, but I like to trigger it based on actual time and not when the esp was booted. Ideally, if I set it to every /5 minutes, it should start heating up 4:30 and push the value at 05:00 (09:30/10:00, 14:30/15:00, etc).

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SDS011 component and its interaction with the PollingComponent interface, then compare how the time component invokes component.update for other sensors. Done means a time-triggered component.update can trigger SDS011 measurements while preserving the requested warm-up and reporting timing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
embedded-iot
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.