-
Add Support for User Created Actions and Contexts
Recently, we’ve gotten a Java Code feature that allows users to interact directly with Android APIs. This gives us the freedom to create custom solutions however we like.
However, to use the code, we still have to call the task where our code resides using Perform Task, which has limitations when used as an “interface.”
Unlike built-in Tasker actions, Perform Task only allows users to set two variables. While we can technically pass any variables, we still have to make sure their names match, which isn’t ideal.
Since Tasker doesn’t currently have a way to read a task’s description or
-
Exclude logs of a specific profile or task in Run Log
Hi,
I have a profile that is using a for loop, which makes logs very long and unreadable.
Can we have a function to exclude a profile or a task in logs?
Thanks.
-
connectivity changed event
There is an action "Get Network Info" avilable but i think there is also need of Connectivity Changed / Network Changed event as per
https://developer.android.com/training/monitoring-device-state/connectivity-status-type
I know i can use android.net.conn.CONNECTIVITY_CHANGE but that itself is desperated and event fires more than 20 times when there is a change.
-
Add an option in "Set Variable" to designate it as a PROJECT variable or a TASK variable
There is currently no way to programmatically create project or task variables. Only global variables or fleeting local variables that don't persist when the task ends. If you want something to be a task variable or project variable, you have to create it by hand within the gear menu for a task or project.
PLEASE add a "storage" option when setting a variable that allows us to designate a variable as a project or Task variable. This would enable the programmatic creation of these variables.
-
Feature Request: AutoInput v2
In AutoInput v2, there is a "Wait For Element" action that waits until an element appears on the screen.
My current AutoInput workflow is like this: click(id, %button_id) --> waitForElement(id, %loader_id) --> click(id, %button_id)
Since the loader's element ID is often hard to get (as it disappears instantly due to fast loading), could you add a "Wait For Element to Disappear" action that waits for an element to disappear?
This way, the workflow would only depend on %button_id and would become like this: click(id, %button_id) --> waitForElementDisappear(id, %button_id) --> click(id, %button_id)
*Note: The loader element makes the button disappear from
-
Widget V2 rotation, blur, and element filtering
Would love to see a few additions to tasker widget v2! I'd be able to leave kustom entirely if it had the following:
1. the ability to rotate elements (either around centre or other defined anchor points)
2. the ability to filter elements by other elements (i.e. remove portion of element that's overlapped by another element)
3. Adding a "blurr" option in addition to color would be sick as well!
-
🐍 Feature Request: Python Interpreter in Tasker
Summary
Add support for running Python code natively inside Tasker tasks, similar to the current Java interpreter, to give users a broader scripting option.
Why This Matters
Ease of Use: Python is widely regarded as simpler and more readable than Java, making it more approachable for beginners while still powerful for advanced users.
Ecosystem Power: With its vast standard library and third-party packages, Python enables advanced automations like data analysis, machine learning, web APIs, and IoT device control directly from Tasker.
Community Adoption: Python has one of the largest developer communities, meaning Tasker could benefit from a huge ecosystem of
-
Status Chips If "Live" Checked For Notification
User defined text or allow the setShowWhen tag to be used.
https://developer.android.com/develop/ui/views/notifications/live-update#status-chips
-
[Text/Image Dialog] Add Image Buffer to list of image sources
As it is currently available in scenes. Thanks
-
Stop an app without using root
Current kill app only works when use root is checked. If possible, I'd like the ability to stop another app on an unrooted phone (this is the only remaining thing I still need root for).
-
Get Task execution ID and Stop a task using (also) its execution ID
Hi, it would be very nice
- An action to get, inside a task, its execution ID
- Stop a task execution using its execution ID (instead of its name)
These features would be very useful expecially with multiple instances of the same task running together
-
Ask for storage access permission for all relevant tasks and actions after restoring a backup to a different device
I restored the Tasker settings to a second device (same model) I had installed a Custom-ROM on. The backup contained many tasks that need storage access. When one creates such a task manually Tasker requests permission for that access. This does not happen when tasks are restored from a backup. Now each time such a task is triggered by a profile for the first time, Tasker requests storage permission. But the request neither contains the task nor the requested directory. This is very inconvenient and may lead to data loss.
I have two requests:
- Short term: Show the requesting task
-
[REQUEST] List Dialog and Input Dialog actions improvement
Hi,
I would like to know if the following actions could be improved as described:
- List Dialog: Add 'Output Variable Name' field. - Input Dialog: Add custom buttons like in the List Dialog action.
Thank you!
-
Feature Request: Indicator for Ignored Cells in "Cell Near" Recent Cell List
When editing a “Cell Near” state, the Recently Connected Cell List currently shows:
✅ Tick mark for cells already added to the trigger list
❌ Cross mark for cells not yet added
However, it does not indicate which cells are already in the Ignore list. This makes it difficult to manage or fine-tune ignored cells, especially when the cell list is long.
🎯 Feature Request:
Please add a third indicator (e.g., a grey mark, pause icon, or any visual cue) beside the cell IDs that are already added to the Ignore list, within the “Recently Connected Cell” popup. This will
-
Scene Editor > slider events
We already have "on value selected" when the user releases the slider in a different position.
It would be nice to have "on value changed" so we can do things while the user is still sliding it.
-
Copy the open-source Be Nice app's split screen functionality to fix Tasker
There is an open-source app called Be Nice that seems to have successfully implemented split screen support for modern Android devices. Perhaps Tasker could use it for inspiration on getting its Split Screen feature working again. Here's the source on GitHub: tkuenneth/BeNice: Split-screens on Android made easy
(Note: I'm not affiliated with Be Nice. I just ran into it on Reddit.)
-
Better support for HTML in actions like Text/Image Dialog or List Dialog
There are a lot of times when you want to show some text data on the screen but right now if you want make a style change to your text you are limited to use mostly 3 options: 1. Scenes which has serious problem with sharing with other people devices. 2. AutoTools Web Screen which is for more advanced users. 3. AutoTools Dialog seems to not support RTL languages.
I am suggesting to give more html tags support for more popular actions like Text/Image Dialog or List Dialog that most people use. I would prefer a more "native" style so
-
Combine Music Play action with Play Ringtone action
How about adding option in the Music Play action to choose an internal ringtone from the ringtones/notifications menu of the device? There is the Play Ringtone action but as you know it can do a lot of harm (less funny) when you get loop of audio playing. I would even suggest to remove it completely and adding all the options to the Music Play action but i know you afraid of breaking stuff for users.
-
Name tag for Tasker licenses
Having more than one Tasker license makes it more difficult to know which license belong to which device. That is why i am suggesting to have the option in https://taskernet.com/?licenses to add a name/Name tag to each license so it would be no brainer to know which one belongs to which device.