Google this week introduced a new sleep API that will help developers build better sleep tracking apps. In response, the Tasker developer wasted no time implementing the API in a new beta, allowing users to create a custom sleep tracker on Android.
For those who don’t know, Tasker is a popular automation application available on Android. You can create profiles that initiate tasks that consist of actions. These profiles can be triggered based on user-defined states or events. Because Tasker is so extensible, there are unlimited possibilities for automation. And now with Tasker 5.12.3 beta, you can add sleep tracking automation to the mix. The latest beta version uses Google’s new Sleep API to centralize battery-efficient sleep detection processing. The Sleep API uses a machine learning model on the device to infer the user’s sleep state based on the input of light and motion sensors on your phone.
João Dias, the developer behind Tasker, said he didn’t have the opportunity to do any overnight testing of the new sleep tracking features, so his mileage may vary. Furthermore, as the Sleep API is part of Google Play Services and not Tasker, it cannot fix any problems if it breaks on Google. With that fixed, if you’re interested in taking control of your sleep data or making your own sleep tracker, check out the video above to see how you can use the new sleep state feature in the latest beta version of Tasker.
The full changelog for Tasker 5.12.3 beta is below:
- Added Sleeping status: track your sleep with Tasker
- Helper added HTTP request shares Headers field to easily define the most used headers
- Added ADB Wifi auxiliary for easy configuration of permission grant / revoke commands
- Made monospace text without line breaks optional in certain input fields (Preferences> UI)
- To repair Marking event does not work reliably if the screen is off on some devices
- Try to fix the clipboard change sensor on Android 11 on some specific devices
- If you search for something like Run when adding an action and you have some tasks with the word “run” in them, don’t use them to automatically fill in the Run TaskName field
- Do not show global variables structured with. on your behalf on the VARS tab
- Now, when reading a structured output, if there is no match and the variable has been marked as a structured variable, it will be evaluated correctly in the “If Not Set” condition. If you use the variable with access to the structure, the literal value is used.
- When reading the HTML structure with the bracket notation, use brackets for matching attributes, for example. {attr = value} instead of [attr=value]
- Allow the use of an empty key when accessing a structured variable, for example. % json[]
- Check that a variable is of the specific type used in the action “Define the structure type of the variable”
- Failed to add certain events / states
- Fixed using the setLocal () function in the Scene WebView for project / profile / task variables
- The configuration of project / profile / task variables for the “Java Function” action has been corrected
- Bug fixed where if you select the “Run Task” action based on a search for a task name, the priority would start incorrectly to 5 instead of% priority
- Try to repair the external SD card or USB OTG on Android 11+. It is still not fully functioning.