I am controlling an insteon hub with HTTP Request, when I test them since tasker works, but when I export it as an application and use it on android 9, I have the error of cleartext http traffic to not permitted. It would be helpful to be able to configure like this:

An option for cooldown time to trigger the last skipped event (skipped during the cooldown time) after the cooldown time is over would be useful.

E.g. there are many changes of %LIGHT when moving. In a profile reacting on changes to %LIGHT and adding a cooldown time of ten seconds Tasker will probably not trigger the entering of a completely dark area where %LIGHT will not change anymore because it's constantly 0. The above change would allow to use a cooldown time AND to detect the % LIGHT changing to 0.

Please add this feature.

Thanks

Similar to this previous post: https://tasker.helprace.com/i214-tasker-on-android-tv

I don't mind sideloading etc, but the main issue is being able to access the full layout of Tasker. Currently the search button and 3-vertical-dots menu at top right corner do not show up on my TV (Sony running android 8). I tested latest released 5.7.2 and 5.8.0 beta 5. 

Is Tasker somehow compatible with some Android 8 TVs and not others?

Would it be possible to make the project bar along the bottom of the main Tasker interface larger (specifically, taller)? I'm finding that with full gesture navigation with the betas for Android Q, swiping sideways along the bottom of the screen switches between recent apps, and scrolling the project bar is really difficult (there are maybe a few pixels at the top of it that I can grab, but it's really tricky). Maybe there's another way to do it that I'm not aware of.

Tasker backup and recovery features, please support webdav.

Hello! Could you give the ability to run 2 event created with "IntentTask" plugin in split screen mode?

I would like to trigger tasks when (optionally specific) devices are connected/disconnected from my tethered network

I use Tasker for almost everything, Tasker in fact is my OS, I keep my settings in Tasker rather than in the OS menus as they will be with me with any device or any Rom I will use.

The most time consuming for me is to interact with the device and Tasker (Typing complex shell commands and navigate between the tasks and screens.

I understand this is big, but I would want some way to connect my laptop to Tasker and use Tasker as WebApp (with mouse and hotkeys)

Traditional app state contexts work but are static: the only way to change the apps included is by opening Tasker's UI. The App changed event allows specification of included apps using a variable, but this is only an event, not a state.

I would like a combination of the two: an app STATE context which activates only when the app name/package/whatever matches a text field where a variable may be used.

There should be a variable that can be set in place of the root toggle so that commands that are created and run dynamically can automatically set if root will be required or not. Moreover if projects are being shared with other people, some people might not need or want to run shell commands as root. This would make it easier to create those projects with like a global variable maybe. If the value is "1", then run with root, otherwise don't run with root.

There should be an option to change the text size of shell actions and also an option to disable word wrap. Writing multi-line scripts in shell actions is a mess with word wrap enabled and really hard to understand what is going on.

When entering the setting screen of an Auto series plug-in (for example, AutoInput), the Tasker UI language is switched to the OS language different from the preference until exit the tasker setting screen.

For example Event> Plugin> AutoInput> Gesture Action> Plugin> AutoInput> Action

Tasker: 5.8.0.beta.5 Android: 9 OS language: Japanese Tasker UI language preference: English

There are 3 options in setting quick settings action:

Active

Inactive

Disabled

Please add an option named "Toggle" so that there wouldn't be a need to define a wrapping variable to toggle a quick setting. It could be toggled when the option is set and the value of it being turned on or off could be accessible through an output variable. 

This makes tasker a bit easier for newbies. 

I'd like to suggest arrayed native/global vars. A user started a forum thread about date/time particulars. It seems to me that a hidden array is the perfectsolution, not just here but elsewhere. Example: DATE returns m-d-yy. Why couldn't DATE(1:4) return numbered year, month, day-of-month, and day-of-week? Same goes for TIME (i.e. hr, min, sec) but perhaps also encompassing TIMES and TIMEMS. Similarly, why not WIFI for the state, WIFI(1) for connection data, and WIFI(2) for scan data. DAYM, DAYW, TIMES, TIMEMS, and WIFII shouldn be delisted rather than deleted so that existing tasks will continue to function  I think this

A new option in Test Scene preferably called Elements that'll return the names of all the Elements in that scene.

Cell Near have the option to ignore certain towers, I don't see why WiFi Near can't have the same option for Mac Addresses(or even for SSIDs, but Mac is more useful to me)

Just like in the log where the user can select Profiles, Tasks and/or Actions; it would be great to have the same selection buttons in Search. The use case would be a more granular search for cases when you know the Task name or that the variable is used in a Profile without having to scroll through all of the actions which use the variable.

When complexity increases, meaning when a lot of sensors are included and they all talk to each other to reach certain outcomes, then as to what is going on when it operates there is little to no feedback as to what is needed, in order to understand what is going on.

So with such, there's little to no help, for instance, from RunLog. The best I know is to add voice feedback all over the place to try to make sense of the flows, but I figured it would be great to dramatically improve Tasker with greatly helpful feedback system,

It would be nice to have an option in WiFi Near to check if there's a known WiFi available. With this it would be possible to do profiles like:

On event 'Display on' AND WiFi Near (known WiFi) => Turn on WiFi