You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I get the intent of actualMS variable, but it could be misleading. If the device is awaken from the sleep mode by a hardware interrupt (for instance arduino uno deep sleep could be interrupted by an external pin interrupt on pins 2 and 3) then there is no way to tell how long the device has been actually slept (unless of course you have an external clock source like a RTC to check against).
Not a big deal, but worth a mention in the REAMDE perhaps.
The text was updated successfully, but these errors were encountered:
I would call this a bug. If you've gone to sleep and an interrupt has woke you up, the return value is wrong. It should be possible to store the value of the RTC before sleep and after, subtract the two, and return that instead.
Hi,
I get the intent of actualMS variable, but it could be misleading. If the device is awaken from the sleep mode by a hardware interrupt (for instance arduino uno deep sleep could be interrupted by an external pin interrupt on pins 2 and 3) then there is no way to tell how long the device has been actually slept (unless of course you have an external clock source like a RTC to check against).
Not a big deal, but worth a mention in the REAMDE perhaps.
The text was updated successfully, but these errors were encountered: