-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add a sleep/dsleep chapter to Lua Developer FAQ #1861
Comments
Good idea, but at the moment I'm still somewhat overloaded :/ While I've started to catch up on things a wee bit, I've still got something like 250 outstanding github notifications to make my way through. |
I've just finished doing the plumbing and central heating system for my new house. And then I want to crack on with the Lua 5.3 implementation which kinda got stalled with the house work. Sorry. In terms of the FAQ, there's bits that really need updating like once we've got the early memory leaks out of the way, using UpVals is solid, fast and efficient, but there are gotcha's which need explained for the beginners. So what I am saying is that this is a great idea, but not one that I've got time for at the moment. |
@TerryE i was going to open a new issue, but i saw you mentioning lua 5.3. Is Lua 5.3 support in the works? That be pretty sweet, i just checked the lua homepage and 5.1.* seems pretty old. |
@marcelstoer Marcel, I need to add this and I will include this in the next push of my draft. Thanks 😄 |
Marcel, definitely #1861 belongs in here. #1862 belong in the Extension Developers FAQ, though there is a parallel one about how Lua developers have debugger support. Even if we ported the rest of the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@TerryE's FAQ has a nice chapter about techniques for reducing RAM and SPIFFS footprint. I believe it'd be very useful to add a related chapter about "How to reduce power consumption and how to sleep/dsleep".
We have documentation on
node.sleep
,wifi.nullmodesleep
,rtctime.dsleep
, andrtcfio.sleep_until_sample
. What we're missing is the bigger picture. When to use which? Which function is intended for which use case? What is the best strategy for (quasi-)autonomous, battery/solar-powered devices? What are the gotchas? It'd also be nice to document the required wiring graphically (linking tonode.sleep
).@eyaleb or @jmattsson would you have time to put together a draft (assuming you agree with my request)?
The text was updated successfully, but these errors were encountered: