Is there a way that Tasker can prevent Android from making sounds or vibrating when setting ringer volume?  I mute my phone at night, then I have a profile that runs in the morning that turns the ringer on, and it makes an annoying beep when the Ringer Volume action runs.  I saw one post that seemed to address this (https://tasker.helprace.com/i869-adjust-ringer-volume-0-without-sound), but setting Do Not Disturb didn't stop the sound for me.  I would also like to prevent the vibration when setting the ringer volume to zero.

In addition to setting Do Not Disturb = No Interruptions, I've also tried

Very simple yet quite useful for testing change. You can set priority or something like that when you currently long click. Two additional field for par1 and par2 wuld make testing certain tasks a lot quicker.

This would be ideal for us that has monday as the first day of the week.

Being able to toggle focus mode from the Digital Wellbeing settings and read the state. 

The file actions are awesome but I can't seem to figure out a way to create files from inside tasker itself, only write them. May be wrong and it's already possible. But if not, would be awesome to have a "Create file" action. Being able to input a title, select the location to place the file, and even select what kind of extension is used (.txt,.csv, Etc.). Would save time by not having to create a file ahead of time to use inside of tasker. 

In A11, running `dumpsys location` throws an exception that the user needs android.permission.INTERACT_ACROSS_USERS (android.permission.INTERACT_ACROSS_USERS_ALL)

These do look to be system/privileged, so should be grantable via ADB.

Thanks.

Is there any way to use taskers own color selector subroutine (as when choosing font color in a scene) as a stand alone action fur users to use as a color picker? 

Currently we have the ability to manually run entire tasks. I use this to debug the task itself, before moving on to debugging the profile context, by adding strategic Flashes and Stops.

I think adding a full blown Debug mode like an IDE might be asking for too much, since Tasker is not an IDE, which means we still may continue to have to rely on Flashes to check variable contents. But if the Task is really long and we specifically want to Debug a specific part, it's super annoying having to run the entire Task many times while moving

I want to execute function X on given situation:

A AND (B OR C OR D)

But app lets only this:

A AND B

A AND C

A AND D

I have to define them one by one individually, OR statement would be so nice.

Enable tasker to launch Wyze app and invoke rules within the Wyze app

I have a raspberry pi zero with two vibration sensors to send me pushbullet notifications when my laundry is done. I want to use tasker Autonotification to read those notifications then broadcast by Autocast through my google homes the same message for when I don't have my phone on me. 

This is just one use case, i have other ideas that I'd like to Autocast audio messages to a group of google homes. 

Similar to the "Broadcast" feature natively built into the google home devices. 

At this point with so many folks using Tasker for so long - a lot of people have A LOT of Project Folders/Tabs.

It is very difficult to keep scrolling left/right to jump from one Project to another very easily.

A new feature should be added so that when the user long-click on any Project Tab, the first Action (lowest on list below "Set Icon") should be a menu option for "Show Project List".

This would then display a simple vertical list menu of all Projects and one can easily be chosen. There can also be an option for "Sort

"Hey google, start task xyz with Tasker"

Could this be doable with Google assistant ? See https://codelabs.developers.google.com/codelabs/appactions

Maybe it's already possible ?

This could be really useful when using Android Auto: start a specific task with a voice command, especially since AutoVoice has been blocked by Google (I'm not sure if it is working again for all languages) and since IFTTT is not free anymore...

Hi,

At present we have Application, Day, Event, Location, Time, State context. And that's way old thing when tasker was built.

But App, Time, Location, Day can be classified either in State or Event context and no strong logic they should have separate category.

Should we simplify context to only state and event category?

This would make debugging much easier.

A variable like %lc_entry that just contains the whole logcat entry from the event... Opens alot of new possibilities!

Most of us have Tasker handling several Profiles such as Car, Home, Work and Sleep. In my personal setep, the Sleep profile disables many things in the phone to save battery in case it is not plugged in.

Would be great to have a "Pause Tasker Services" action that would disable Tasker services/wakelocks... Choosing which type of monitoring will be disabled or just keeping a time based one (Time Event/State). During this time, all Profiles that depend on the monitors, will stay in the same state (Active/Inactive) during the whole period and will not change until the monitors are activated

Hey Joao, So I never like the toast messages on android. Don't like the gray background and the font. So I thought maybe you can add something that kill system toast messages, and replace theme with custom toast messages. I tried to do it with scene that will trigger with logcat, and will cover the android toast messages. The problem is that the toast appear on top of the scene messages I made. What do you think? Thanks again for the help.

1) Allow the "perform task" action to have unlimited number of parameters

2) Allow the "perform task" action to return an array variable

I don't know the rest of the users, but I find a bit annoying (just apperance) the '<' icon at the right when using the List Dialog action. -> https://i.imgur.com/IdMcUa1.jpg   I know that the following "workarounds" can be applied currently to get rid of it: - Switch to variable mode (press arrows icon) and leave the text field just as: %. - Switch to variable mode (press arrows icon) and leave the text field just as: 0. - Add 1 to the current %array(#) as: %num To %arrar(#) + 1, specially useful when there are more than 100 elements