esphome / esphome/feature-requests

display initial delay feature

Open
#2,284 0 comments 1 reaction 0 assignees View on GitHub
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**

For e-paper displays (waveshare in my case but I do not see why others would be much different) if only a full refresh is supported then it can be the case that a minimum duration between refreshes could be quite long.
This can result in the screen coming up and starting at boot, then a very long delay before data is available on the screen as the next refresh has to be a long time later.
Rather a delay feature to allow the screen to only draw for the first time would allow a short say 30 second delay before the screen draws and thus data would be in place for the initial screen draw.

**Please describe your use case for this integration and alternatives you've tried:**

As the screen has a "minimum 180s between refresh" suggestion from the supplier it is not useful to show very dynamic data so I have decided to only do a full refresh once every half hour to lower power cost.
To get data on screen before that first 30 minutes is up I have an on boot sequence that delays 180 seconds and then refreshes the display component. This gives me data after the minimum refresh delay, though as the refresh takes 16 seconds I may not be quite accurate depending on timing during startup.

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the display component's refresh behavior and the reported on-boot sequence, focusing on how the first draw is scheduled after startup. Define how an initial delay would interact with the minimum refresh interval, then verify that the first display update occurs after the configured delay without changing later refresh timing.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.