Meshtastic

Sleep explainer

As a new user, I can understand that it make sense to have the device sleep frequently, but it’s not obvious what the effect of sleep is on how to use the system. I’d really like a doc that explains to newbies like me how to think about sleep.

For example, if the app knows it’s associated, but the device is asleep, and I send a message, can I expect that the message will get sent? Or do I need to wake the device first? Is there an indication that it’s not sent yet but will be?

If devices are sleeping, are they doing so in sync, so that when my device sends a message I can expect that other devices in the mesh are also awake to listen for it?

I can guess answers to all of these questions, but I think it would help new users a lot to have a doc that clearly spells it all out.

To piggyback on this question because I was wondering the same thing,
I would also like some more info on the options on ‘advanced settings’ in the app. Assuming “broadcast position period” is how often your coordinates are pinged to the rest of the mesh, but is the “device sleep period” how long the device sleeps, or how long the before the device goes to sleep after waking it?

1 Like

@geeksville , @sachaw

I’m also trying to find out details about how sleep works – and the other side, when/how does the device wake? For now, since I’m operating with a fixed location, I’m setting phone_timeout_secs to a high value and that seems to do what I want.

Currently it resides in a few places:

(I split router off of power settings because it seemed like something lots of people want to mess around with)

Note: There’s still some shuffling happening and duplication in the docs, so these may move around slightly. But they are good as of today.

2 Likes

We have talked about building some diagrams to show how the various cycles run on the device with specific settings, but haven’t had the bandwidth to do it yet.

This section on the docs goes into some detail about how you can tell if your device is connected/sleeping/out of range on android.