This post is probably not within the scopes of what Tasker should be able to do, but I would be happy if it can happen.

I have AutoWear already and don't get me wrong, it is a great tool. However, versus the average individual who has their phone and watch synced all the time, I am not really into that. I like my device to be self-sufficient. One of the things I liked about AutoWear was it allowed me to deploy somewhat of a miniature routine to the watch in the background. For example, I used the AutoWear (default buttons)

On my Pixel 6a running Android 13, I have found that the Display -> Status Bar action incorrectly wants me to enable accessibility for it to work. I understand that on some devices accessibility is in fact needed.

This results in a few interesting quirks:

1. When creating a Status Bar action, if it is set to Expanded, Tasker warns that I need to enable the accessibility service. But the action works fine to open the notification shade even if I decline to enable accessibility.
2. If the notification shade is open, the Status Bar -> Collapsed action works as expected. But

When using a variable to create part or all of the Action Label for an action within the Notify action, the notification correctly displays the variable value in the label. However, when clicking the action label to perform an action, the performed action's %caller variable displays the variable name instead of the variable value.

Steps to Reproduce:

1. Create a task with the Alert -> Notify action.
2. In the Notify action, scroll down to the Actions section and add an action.
3. Give the action a label that includes a variable.
4. Set the action to Alert -> Flash. Set the Flash action's

Hi. Vibrate, Vibrate Pattern actions don't work. There is no error, but there is no vibration. Android 11 Lineage Tasker beta 6.2.12-rc. All permissions from settings are obtained, as well as write_secure_settings

In API 30+ it is now possible to have the BiometricPrompt.Builder (used by the Authentication dialog) require only credentials. In the US, the government may compel the owner of a phone to unlock it using their fingerprint since the government views a fingerprint as "public record" versus where a password is not. Besides, a person who is sleeping can have their fingerprints used against them while unconcious.

As such, I feel that the Authentication dialog should allow the user of Tasker to specify that it should only ask for the device's password without prompting at all for biometrics.

This is

MQTT would be the most logical way of Tasker to integrate to a home automation or vehicle.

Current 3rd party plugins have various problems:

- "Join" requires Google Play framework

- "MQTT Client" by Webneurons is no longer maintained and it contains a google ad tracker

- "Node Red integration" requires Node Red, and feels unnecessary

For me, native MQTT support would be the most important feature of Tasker. If I'm not alone here, I'd be happy to take part (via Patreon) in covering the expenses of developing the native support.

When using "Element Add Geomarker" there is a field called "Spot Colour" which allows you to set the colour of the spot surrounding the marker.

If the spot radius is set to 0, this parameter disappears, which makes sense. But if you set spot radius to a variable (e.g. %marker(3)) the spot colour parameter also disappears. This means you can only use spot colour if the radius is a constant.

I imagine this isnt intended

Android: 13 (TQ3A.230705.001)

Help section is being shy hiding himself behind the triple dot menu.

IMHO, Tasker should have promoted him more to the user by actively presenting him in the upper layer.

I think placing him right next to the resect button will make the user notice him more. 

Or maybe Tasker could introduce a new way to call him for certain action. E.g long pressing the action in action list menu.

The former should be sufficient though. Thank you!

Hi, I was testing Tasker setting APP thinking that the Bluetooth connect will work but it not. So maybe it's a tasker bug? I run the last beta version of all the APP.

I use "Mode and Routine" on my Samsung phone to disconnect/connect Bluetooth device, but they're a delay that can't be predicted

It would be very useful to retain and display the most recent run time for each task.  

I would be of great assistance in troubleshooting (ie - did the task really run or not)

Also it would be useful in keeping things clean and deleting task that are no longer used.

As a user of Tasker, I need the way to be able to ensure that a scene is, and remains, a certain size, even after the scene has been edited through the Tasker Scene Editor UI. Often it is needed for the scene to be fullscreen and that any actions that alter the screen size/orientation cause the scene to be resized to fill the new screen size.

Sometimes, it is nice to be able to resize a scene programmatically to a specific size (not necessarily fullscreen) from a Task's or Scene's actions for a variety of reasons. An option in Create

(this is technically a duplicate of https://tasker.helprace.com/i1124-mock-up-on-tasker but the title of that post is misleading, at best. It also doesn't have very detailed requirements or a user story. So, here is a better one:)

As a user of Tasker, I need the ability to be able to set my system's location via the Developer Option's Mock Location App feature so I can ask Tasker to set a fake GPS location for the rest of the system.

I also need the ability for Tasker to "see past" that fake location so that profile conditions that use Location-driven conditions still work as

Hi

Can you add an action say "Get Wireless Debugging Port"? This action will do following.

1) Enable Wireless Debugging using custom setting if not enabled

2) Use NsdManager to get Wireless Debugging Port which can be used for enabling Wireless Debugging.

When Tasker enable Accesibility Service for itself, it disable Accesibility Service for other applications.

Uso la pulsación prolongada del botón de volumen-arriba para lanzar una tarea de Tasker. Para ello necesita tener habilitado el Servicio de Accesibilidad. Este servicio se desactivaba cada dos o tres días y tenía que volver a concederlo.

También uso constantemente el programa Quick Cursor, que también necesita el Servicio de Accesibilidad, pero nunca lo perdía.

Cuando se añadió la opción de que el propio Tasker vigilara si había perdido el Servicio de Accesibilidad y lo volviera a conceder, me alegré y lo active tanto para

I make a scene and it is 910w by 525h. I export it as an app. I then later decide I want my scene to be WIDER, so I change the width from 910 to 925. Looks normal in Tasker. When I export it as an App however, the resolution is still 910w instead of the new 925 and all my buttons are pushed horizontally into the others if they were on the edge past 910 pixels.

It would be great if AutoTools dialog list had an option to turn on a search field to find a specific entry on the display list.

Ideally, creating notifications would be possible from JSON inputs. You provide the necessary fields and it would create the AutoNotification with the properties. I assume this to be not too far away from how it works today. But it would help massively in re-using parts.

When I lock Tasker, it appropriately locks some task actions like “Disable Tasker”. I was wondering if you can allow the options of adding other actions to the list of not allowed when locked. For example, I want to lock access to “SecureTasks” plugin actions while Tasker has an active lock, because that plugin has full access to my phone.

Hello, I have a project that has enough tasks I had to break it into 2 different projects to be able to use the UI properly. There are 29 tasks for the project and as soon as the list of tasks goes over 17 on my phone screen, the ui starts getting janky and it becomes difficult to move and rename any of the tasks in the project. This made me realize that having folders that behave like the collapsable If or For actions would alleviate my issue, while also making organization within a project better. Cheers.

The ability to lock down any actions within a task you want so that it can't be deleted while it's locked. This is useful for creating tasks and basically using lock to save actions or sequences that are finished while still working on other portions of the task. Would also make deleting everything except the actions you want to keep much easier and prevent accidental deletion.