sleep() [ Sleep ]
SystemSleepConfiguration::network, network, SystemSleepConfiguration.network
// PROTOTYPE SystemSleepConfiguration& network(network_interface_t netif, EnumFlags<SystemSleepNetworkFlag> flags = SystemSleepNetworkFlag::NONE) // EXAMPLE 1 SystemSleepConfiguration config; config.mode(SystemSleepMode::STOP) .duration(15min) .network(NETWORK_INTERFACE_CELLULAR); // EXAMPLE 2 SystemSleepConfiguration config; config.mode(SystemSleepMode::ULTRA_LOW_POWER) .duration(15min) .network(NETWORK_INTERFACE_CELLULAR, SystemSleepNetworkFlag::INACTIVE_STANDBY);
This option not only allows wake from network activity, but also keeps the network connected, making resume from sleep significantly faster. This is a superset of the
SLEEP_NETWORK_STANDBY feature. This should also be used with cellular devices with sleep periods of less than 10 minutes to prevent your SIM from being banned for aggressively reconnecting to the cellular network.
|Network Wake Support||Gen 2 Wi-Fi||Gen 2 Cellular||Gen 3 (any)|
|Wake from STOP sleep||✓||✓|
|Wake from ULTRA_LOW_POWER sleep||✓|
|Wake from HIBERNATE sleep|
The first example configures the cellular modem to both stay awake and for the network to be a wake source. If incoming data, from a function call, variable request, subscribed event, or OTA request arrives, the device will wake from sleep mode.
The second example adds the
SystemSleepNetworkFlag::INACTIVE_STANDBY flag which keeps the cellular modem powered, but does not wake the MCU for received data. This is most similar to
Note: You must not sleep longer than the keep-alive value, which by default is 23 minutes in order to wake on data received by cellular. The reason is that if data is not transmitted by the device before the keep-alive expires, the mobile network will remove the channel back to the device, so it can no longer receive data from the cloud. Fortunately in network sleep mode you can wake, transmit data, and go back to sleep in a very short period of time, under 2 seconds, to keep the connection alive without using significanly more battery power.
If you are waking on network activity, be sure to wait for
Particle.connected() to be true before entering sleep mode. If you device has not completely connected to the cloud, it will not be possible to wake from sleep by network activity.
If you use
INACTIVE_STANDBY, then data from the cloud to the device (function, variable, subscribe, OTA) will wake the device from sleep. However if you sleep for less than the keep-alive length, you can wake up with zero additional overhead. This is offers the fastest wake time with the least data usage.
If you use
INACTIVE_STANDBY, the modem is kept powered, but the cloud is disconnected. This eliminates the need to go through a reconnection process to the cellular tower (blinking green) and prevents problems with aggressive reconnection. The device will not wake from sleep on functions, variables, or OTA. However, it also will cause the cloud to disconnect. The device will be marked offline in the console, and will go through a cloud session resumption on wake. This will result in the normal session negotiation and device vitals events at wake that are normally part of the blinking cyan phase.
For more information on using network sleep modes, see Learn more about sleep modes.
P2 and Photon 2 Devices:
Wake on network is not supported on the P2, Photon 2, or Tracker M.