Good point there, we'll have to find a way to fix this.
What happens is that we use the timer framework in the Atmel LWM framework to schedule regular checks of various stuff. This uses the Arduino
millis() timer, which only runs while not sleeping. This means that a check that is supposed to run every 100ms will only after 100ms have spent not sleeping.
Since we also have a timer that always runs, even when sleeping, it seems obvious to use that one for the timer framework. However, due to the way the framework is set up, this would mean that the timer would "catch up" for the time spent sleeping - if a timer runs every 100ms and you sleep for 60s, it would run the timer event 600 times when you wake up, which is probably not what we'd need. Modifying the timer framework to only run the event once when returning from sleep is probably tricky due to the way events are rescheduled, but I think we could figure it out. I'll see if I can find some time to look at this soon.