Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A different take on sleep than #231
Set a timer to wake on the turn of the global second.
For non lead scouts, just go fully to sleep setting the usual symbol counter.
If you're a lead scout, use a systimer to sleep only the radio, so you're still alive for hq comms. Ive found that if you 'pause' the lwm stack in addition to putting it to sleep you can queue up to NWK_BUFFERS_AMOUNT (default 5) frames.
https://github.com/jacobrosenthal/library-atmel-lwm/tree/pause
Either way, on wakeup set a systimer for the wakems to put the device back to sleep again (current default 100ms)
Im seeing 2-4ma usage with this combination vs ~12-14ma fully on or 1ma fully off. But Im also able to communicate with 'sleeping' scouts. Its still takes a few attempts to get through as I dont have a synchronization protocol for meshOffset and thus meshtime yet.