Skip to content
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

Power consumption is too high #7

Open
swede89 opened this issue Sep 9, 2019 · 1 comment
Open

Power consumption is too high #7

swede89 opened this issue Sep 9, 2019 · 1 comment
Assignees

Comments

@swede89
Copy link
Collaborator

swede89 commented Sep 9, 2019

The ESP is always in active mode and therefore consuming much power. The clock should offer a low-power mode that turns off wifi and force the ESP to sleep. The clock should only occasionally wake up to update the time and allow the user to access the web interface.

@obehr obehr self-assigned this Sep 11, 2019
@obehr
Copy link
Owner

obehr commented Sep 18, 2019

Did some improvements in #13 .

Suggest further efforts:

Power consumption can still be improved but this would make a change in behaviour neccessary. The clock should not be constantly available via Wifi but only ~5 Minutes after power up. Then the Wifi can be completely turned off and only switched on to synchronize the time via NTP server.

Wifi Off -> Deep sleep possible. Deep sleep would only be interrupted for scheduled events:

When is the next animation going to be displayed?
When does the displayed time need to be updated?
--> Calculate sleep timeout and wake up at the right time, then go to deep sleep again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants