Wake-up Triggers

The device can wake from Deep Sleep through several triggers:

• Scheduled wake-up times
• Presence detection with radar
• Soft power button (which remains illuminated during Deep Sleep)

Configuration Options

• xConfiguration Standby Level DeepSleep Mode:  <On/Off/OutsideOfficeHours> (default: Off)
  

  OutsideOfficeHours: The device enters Deep Sleep after the configured delay once office hours end (as defined by “xConfiguration Time OfficeHours”). If the device has already been idle for the required time, it enters Deep Sleep immediately. Before the next workday, it wakes up at a randomized time between 20 to 40 minutes before office hours start. This randomization helps distribute system load and allows time for updates to install, ensuring readiness.

  On: The device enters Deep Sleep after the configured delay regardless of office hours and wakes before office hours start the next workday.

• xConfiguration Standby Level DeepSleep Delay
  

  Delay in minutes before entering Deep Sleep, range “<1...1440>” (Default: 8 minutes)

Common Wake-up Behavior

The device wakes once nightly between 00:00 and 06:00 to install low urgency updates, then returns to Deep Sleep after a default 20-minute delay. It wakes before scheduled meetings if the meeting was planned before entering Deep Sleep. Deep Sleep is prevented during ongoing scheduled meetings, even if the device is unused.

Integration and Notifications

Before entering Deep Sleep, the device sends a status post with the expected wake-up time to Control Hub, marking the shutdown as expected. This status appears separately in Control Hub and suppresses offline alarms.

An xapi event is emitted 1 minute and immediately before Deep Sleep, providing countdown and wake-up time details. Example events include:

  xEvent Standby StandbyInitiatedDeepSleep SecondsToDeepSleep: 0  
  xEvent Standby StandbyInitiatedDeepSleep MinutesToWakeup: 641  
  xEvent Standby StandbyInitiatedDeepSleep WakeupTimeUTC: "2025-02-17T13:36:46Z"

Important Considerations

The device will not enter DeepSleep if presence is detected in the room. By default, presence detection is disabled outside office hours. To enable wake-up by radar detection outside office hours, configure the following setting:

xConfiguration Time OfficeHours OutsideOfficeHours Standby AutoWakeup: Enabled

The device remains offline during Deep Sleep; therefore, network-dependent operations such as web interface access, xapi bookings, and commands are unavailable. Configuration changes made through Control Hub apply only after the device wakes from Deep Sleep.

Control Hub disables certain actions (Reboot, running xCommands, reporting problems) during Deep Sleep. The Delete option remains available but may require manual follow-up for operations like factory reset.

If the Board Pro is in Deep Sleep during a scheduled RoomCleanup (e.g., unsaved whiteboards), cleanup occurs immediately upon boot if the scheduled time has passed.

Troubleshooting guide

• If the board does not enter Deep Sleep as expected:
  • Check the logs for relevant information.
  • Search for the keyword "StandbyCtrlImpl" in either application.log or all.log to identify the cause.
• If the board does not wake up as expected:
  • Manually wake up the board.
  • Retrieve the logs from the time it entered Deep Sleep.
  • Search for "StandbyCtrlImpl" or more specifically "DeepSleep" in application.log or all.log
  • Before entering Deep Sleep, the logs will show a message like "Waking up in xxx minutes", indicating the expected wake-up time.
• After the board wakes up it is possible to verify if Deep Sleep was the reason for the shutdown.
  • Check the status by running the command: xStatus SystemUnit LastShutdownReason
  • If Deep Sleep caused the shutdown, the output will show: *s SystemUnit LastShutdownReason: Standby