Please add support for OpenAI. I have some problems with the current AI options.

1. Google Cloud Payment rejected my debit card.
2. Open Router has very limited free tier.

Open AI accepted the same debit card rejected by Google and the free tier credit is also far more generous than Open Router. People can opt in to give away their data as well to upscale the daily limit.

This is just personal choice at this point but I like their dashboard and credits balance as well. I top up $5 into my balance and limit $1 for monthly usage. I never

Tether works manually and used to work with tasker until a while ago.

Here is the log for the activation: 22.12.21/E current state: 1 22.12.21/E Compartilhamento WiFi: cur: false new: true 22.12.21/E Compartilhamento WiFi: setWifiEnabled() 22.12.21/E Compartilhamento WiFi: Couldn't do with class com.joaomgcd.taskerm.tether.l: couldn't enable tether: "Service Unavailable" 22.12.21/E Compartilhamento WiFi: Couldn't do with class com.joaomgcd.taskerm.tether.j: android.net.IConnectivityManager.startTethering [int, class android.os.ResultReceiver, boolean] 22.12.21/E Compartilhamento WiFi: Couldn't do with class com.joaomgcd.taskerm.tether.k: android.net.IConnectivityManager.startTethering [int, class android.os.ResultReceiver, boolean, class java.lang.String] 22.12.21/E Device doesn't support Wifi Tether 22.12.21/E Ação Compartilhamento WiFi falhou. 22.12.21/E result: stop task (error) 22.12.21/E Erro: 1 22.12.21/MacroEdit action finished exeID 1

Tapping the notification created with the notify action dismisses it. An option to perform an action instead (as autonotification does) would be helpful and also prevent accidental dismisses. 

If the cellular signal of the current/active SIM1 falls below a 'threshold', I would like Tasker to switch to the other SIM2 (dual SIM device). If Tasker could check the cellular signal of SIM2 before switching (in case it too is poor) that could prevent a loop condition.

Some kind of logging would be great to track when Tasker switched between the SIMs.

Motorola Stylus G 2022 - Android 13

I have pretty much followed the FAQ and Dontkillmyapp suggestions. Tasker works fine while the screen is on. But as soon as it locks I have a problem. I set up a simple task of turning off Airplane Mode, waiting 10 seconds, then turning Airplane Mode back on and exiting. It does this every 2 minutes. With the screen off (and locked) it will turn off Airplane Mode but doesn't turn it back on. So when I turn on my screen I see my cell connection is on. So with the screen off,

App stopped recognizing the cell towers I was near. When I try to rescan nearby cell sites, a pop-up appears that says "error:listen" Tasker version 6.5.11, Android version 15, Samsung Galaxy S23, One UI version 7.0

Sometimes it's useful or necessary to find something in tasker to change the tasker language to English. But for retrieving the correct results for datetime parse actions in correct language tasker needs to use the correct language again, so it's would be handy to have the tasker action to change it's language automatically. 

After migrating to my new phone I have this missing plug-in:

com.intangibleobject.securesettings.plugin

But when opening googleplay store. The plug-in is no longer available. Any help?

Hi there, I want to intercept a notification from an app. But that app will only send the notification on an android device when the screen is active. But the project is to have an android device that is not used, that intercepts these notifications. Any ideas how I could make this work? I tried everything to have the app send the notifications when the display is off, but no luck.

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

Hello,

On grapheneos (degoogled phone), installed the direct apk and purshased / activated license from paetreon, whenever i try to 'download' a task (dev task) i get a notification that the service wont run without google play services, when i try to import a task from a browser i get notification 'unknown google error', and when i have google play services temporarily enabled (sandboxed) i get asked to login to a gmail account, which is not something i want to do and defeats the purpose of getting a standalone version. 

i tried installing and uninstalling multiple times aswell ass clearing

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!

Here to say that Sophos InterceptX has restarted its blocking of all AppFactory installed apps and AppFactory itself. Nothing new per se, just returning to behaviour we thought was solved.

Despite placing everything with the Api Key, and the Device ID, I get:

User defined text or allow the setShowWhen tag to be used.

https://developer.android.com/develop/ui/views/notifications/live-update#status-chips

System dialog "Chose input method" is shown, but closes/disappears immediately (~half a second).

I've been using Tasker and the Hotword plugin mainly to launch HomeAssistant's assist.AssistActivity to use voice control. It has been working great for months. Since the last 2 weeks it simply stopped working. I installed an older version of the HA companion app because I thought a recent update caused the issue, but that wasn't it. I used other apps to see if it's a general issue, but it only seems to happen when using Home Assistant. When using the Android Home button, the Assistant launches just fine.

The log is below. Any ideas where the issue lies and how

Can the developer of Tasker contact me at my Gmail address sam.polenta ? I would like to ask about hiring him. :)

In Tasker, when setting up a Termux Action with a script, the configuration saves correctly and the script runs as expected. However, after restarting Tasker (e.g., force-closing the app), executing the Action results in an error. Opening the Configuration shows that the previously set path and script are empty.

• Android version: 14

• Tasker version: 6.6.3-beta

• Termux version:0.118.1