While viewing a Sleep activity on the dashboard (tagged with the app or autodetected), it can happen that some data points (sleep%, sleep efficiency, etc.) are missing. When this happens, there will usually be a message in Yellow to pinpoint the issue at play. Below are some examples of these warning messages, their meaning, and how to correct them:
No underlying data. Sleep not processed
The data of your session is missing, make sure to synchronize your device with HxServices or look at the Records tab for the status of your record (incomplete, syncing, overlap, etc.). Refer to the article: Missing data on Hexoskin Dashboard
The end of the sleep range finished when the device was not connected
The "Sleep" activity was ended after the record itself ended. This usually happens if you press "end" on the sleep activity (mobile app) after disconnecting the device from the shirt. In this case, the sleep metrics will be processed with the available data.
The device was disconnected for less than 5% of the night
The device was unplugged from the shirt for a short period. The sleep metrics will still be processed with the available data. Make sure to place the device in the shirt pocket to avoid any accidental disconnections.
The device was disconnected for more than 5% of the night. There is not enough data to perform the sleep analysis
The device was unplugged from the shirt during the sleep session. The sleep metrics will not be processed as they will not reflect accurately on the data. Make sure to place the device in the shirt pocket to avoid any accidental disconnections.
The beginning of the sleep was started when the device was not connected. Sleep not processed
This usually happens if a "sleep" activity is started (using the mobile app) before the device is connected to the shirt. To correct this, in the dashboard, simply delete the initial sleep activity and add a new one within the range of data. Refer to this article for more information Editing an Activity or Annotation Flag (Hexoskin dashboard)
Range too large for sleep processing - longer than a day. Sleep not processed
Our sleep algorithms do not support sessions longer than 24 hours. You can split the sleep activity by deleting the first activity and adding 2 new ones. Refer to this article on Editing an Activity or Annotation Flag (Hexoskin dashboard)
Range too small for sleep processing. Sleep not processed
Our sleep algorithms require a minimum of 4 hours of sleep data in order to properly display all the data points. Sessions shorter than this will not have all the sleep metrics (sleep phases, % , etc.)
Range does not have REM and NREM period. Sleep not processed
Our sleep algorithms take into account the user's movements using the accelerometer to calculate the Sleep Phases and Sleep Positions. When there is a lot of movement during the night, especially if the user gets out of bed and walks around (even for a short period), our algorithms cannot process the sleep data accurately. To correct for this situation, please refer to this article: Range does not have REM and NREM period (How to Fix)
Keywords: Sleep, missing, metrics, data, yellow, box, rectangle,