esphome / esphome/feature-requests
deep_sleep options: no WiFi - Setup depending on wakeup_cause
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
To create a low power sensor device I would like to:
A- run sensor setup only once on true boot, not after each wakeup
B- boot with WiFi disabled where it will only connect after a sensor has data to send
C- keep sensor (filter values) in "RTC_DATA_ATTR" memory to continue operation between wakeups
For (A) I guess I could modify the sensor code and run the setup depending on the outcome of "esp_sleep_get_wakeup_cause"; would this be the best option - any alternatives?
For (B) I don't see an option: any idea's ?
(C) could possibly be achieved by implementing a custom filter derived form the Filter class -- is this the best way to proceed?
**Additional context**
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the deep_sleep and WiFi components, the esp_sleep_get_wakeup_cause usage, and the Filter class mentioned in the request. The three requested behaviors and their acceptance criteria need to be narrowed before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100