Google unveiled a new sleep API this week that will help developers build better sleep apps. In response, the developer of Tasker wasted no time in implementing the API in a new beta, which enables users to create a custom sleep tracker on Android.
For those who do not know, Tasker is a popular automation application available on Android. You can set up profiles that launch tasks, consisting of actions. These profiles can be activated based on user-defined statements or events. Because Tasker is so extensible, there are limitless possibilities for automation. And now, with Tasker 5.12.3 beta, you can add sleep tracking automation to the mix. The latest beta uses Google’s new Sleep API to centralize sleep tracking processing in a battery-efficient way. The Sleep API uses a machine learning model on the device to derive the user’s sleep state based on the input of your phone’s light and motion sensors.
João Dias, the developer behind Tasker, said he had not yet had the opportunity to test the new sleep detection features overnight, so your mileage may differ. In addition, since the Sleep API is part of Google Play Services and not Tasker, it can not solve any problems with it if it breaks at the end of Google. If you are unable to control your sleep data or create your own sleep tracker, watch the video above to see how you can use the new sleep status feature in the latest Tasker beta.
The complete change log for Tasker 5.12.3 beta is below:
- Added Sleep state: keep an eye on your sleep with Tasker
- Helper added in HTTP request action’s Recipes field to set easy-to-use headers
- Added ADB Wifi helper for easy compilation of assignments that grant / revoke permission
- Made the Monospace non-wrapped text optional in certain input fields (Preferences> UI)
- Get ready Check event does not work reliably when the screen is off on some devices
- Try fixing the clipboard change on Android 11 on some specific devices
- If you are looking for something like Perform when you add an action and you have some tasks with the word “execute”, do not use it to fill it automatically Perform taskName field
- Do not include structured global variables. in their name in the FRESH tab
- If a structured output is now read, and if the variable is not marked as a structured variable, it will be evaluated correctly in the “If not set” state. If you use the variable with structure access, the literal value will be used.
- If you are reading HTML structure with the square bracket, use curled brackets to match the attribute, e.g. {attr = value} instead of [attr=value]
- Allow you to use an empty key if you have access to a structured variable, for example% json[]
- See if a variable is of the specific type used in the action “Set variable structure type”
- Fixed crash when adding certain events / statements
- Fixed using setLocal () function in Scene WebView for project / profile / task variables
- Fixed variable project / profile / task variables from the “Java function” action
- Fixed bug, if you select the “Perform task” action based on a task name search, the priority will start incorrectly to 5 instead of% priority
- Try fixing an external SD card or USB OTG on Android 11+. Not quite working yet.