Tasker’s latest beta allows you to create custom sleep tracking on Android

Google introduced a new sleep API this week to help developers build better sleep tracking apps. In response, developer Tasker wasted no time implementing the API in the new beta, allowing users to create a custom sleep tracker on Android.

For those of you unaware, Tasker is a popular automation app available on Android. You can create profiles that run tasks that consist of actions. These profiles can be run based on user states or events. Because Tasker is so extensible, there are limitless automation options. And now with Tasker 5.12.3 beta you can add sleep tracking automation to your combination. The latest beta 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 a user’s sleep state based on input from a light sensor and your phone’s movement.

João Dias, the developer behind Tasker, said he hasn’t had a chance to test new sleep tracking features overnight, so your mileage can vary. In addition, since the Sleep API is part of Google Play services, not Tasker, it can’t fix problems with it if it crashes on Google’s end. If you don’t get it out of the way, if you’re interested in taking control of your sleep data, or create your own sleep tracking tool, watch the video above to see how you can use the new sleep feature in the latest beta version of Tasker.

The full change log for Tasker 5.12.3 beta is below:

  • Added Sleeping condition: follow your dream with Tasker
  • Added assistant in HTTP request actions Headers a field for easy placement of common headers
  • Added ADB Wifi assistant to easily set commands for granting / revoking a license
  • Text not wrapped in Monospace in certain input fields made optional (Settings> UI)
  • Fix Highlight the event does not work reliably if the screen is turned off on some devices
  • Try fixing clipboard change detection on Android 11 on some specific devices
  • If you are looking for something like Perform when you add an action and have some “perform” tasks, don’t use them to autocomplete Complete the taskName field
  • Do not show structured global variables with. on their behalf on the VARS card
  • Now when you read structured output, if there is no match and if the variable is marked as a structured variable, it will evaluate correctly in the “If not set” state. If you use a variable with structure access, the literal value will be used.
  • When reading an HTML structure with square brackets, use curly braces to match attributes, e.g. {attr = value} instead [attr=value]
  • Allow the use of an empty key when accessing a structured variable, e.g. % json[]
  • Verify that the variable of the specific type used in the “Set variable structure type” action
  • Fixed crash when adding certain events / states
  • Corrected using the setLocal () function in Scene WebView for project / profile / task variables
  • Fixed setting of project / profile / task variables from the “Java function” action
  • Fixed a bug where if you select the “Execute task” action based on the task name search, the priority will be incorrectly started at 5 instead of% priority
  • Try fixing an external SD card or USB OTG on Android 11+. It doesn’t work completely yet.

Source