%INTERRUPT Variable not working?

1,156 views
Skip to first unread message

JST200

unread,
Jun 20, 2016, 8:04:04 AM6/20/16
to Tasker
Hi,

I am trying to identify when "Do Not Disturb" is enabled. I understand that "%INTERRUPT" is the appropriate variable to use. However, try as I might, I can't get the %INTERRUPT variable to do anything.

Initially I tried creating conditional statements using %INTERRUPT and it's documented values of "none", "priority", "all" or "alarms" but without success. So then I tried creating a Flash Task that just contained %INTERRUPT as the text. However, when I run it, all it flashes up is... %INTERRUPT.

As I am new to Tasker, I tried using other variables. Some worked as I expected, some did not. For example (using a random selection) %AIRR, %BLUE, %GPS, %LOC all work as expected. %CELLID, %HEART,  %LOCTMS all just repeat the text I have entered - so I am wondering if I don't understand their operating criteria yet.

My phone is an Galaxy S7 (SM-G930F) and is running Android v6.01 (Marshmallow [lightly toasted  :-) ]), with Tasker v4.8u5,

If it's of interest, what I am actually trying to do is turn of the LED when Do Not Disturb is enabled. Through reading other posts, I have successfully navigated creating tasks that will disable and enable the LED (using the "Samsung LED Controller" add-in), but just need to find a way to trigger the tasks on DnD.

Thanks for any advice or pointers!

Cheers, Jim

Pent

unread,
Jun 20, 2016, 11:05:12 AM6/20/16
to Tasker


I am trying to identify when "Do Not Disturb" is enabled. I understand that "%INTERRUPT" is the appropriate variable to use.

Correct. You also need to enable Notification Access for Tasker so it can access the variables (see Variables section
of the userguide).

>As I am new to Tasker, I tried using other variables. Some worked as I expected, some did not. For example (using a random selection) %AIRR, %BLUE, %GPS, %LOC all work as expected. >%CELLID, %HEART,  %LOCTMS all just repeat the text I have entered - so I am wondering if I don't understand their operating criteria yet.

In order to save battery, Tasker won't monitor (and so be able to report values for) some variables unless they are being used in a task linked from an enabled profile
(or widget), possibly that was your problem.

Pent

JST200

unread,
Jun 20, 2016, 12:32:58 PM6/20/16
to Tasker
Hi Pent,

Thanks for the swift reply!

As far as I can tell Tasker has every permission there is. But perhaps I am missing something. The only reference to Notifications, I can find in the settings, seems to be about allowing Notifications from the app. Is this what you mean? I can't find anything that allows the app to read notifications.

Thanks, Jim

Pent

unread,
Jun 20, 2016, 2:03:38 PM6/20/16
to Tasker
In the settings app, press Search at the top, type 'not', scroll down to
notification access, click it, enable for Tasker.

Pent

JST200

unread,
Jun 20, 2016, 2:30:58 PM6/20/16
to Tasker
Thanks! Outstanding support!

I searched through every option I could find through the "normal" settings options and couldn't find that page. As far as I can see it is only accessible via the search facility - weird.

Now on to the rest of my programming efforts.

Thanks a lot, Jim

JST200

unread,
Jun 20, 2016, 2:46:16 PM6/20/16
to Tasker
...which is now working!

Thanks,Jim

Reply all
Reply to author
Forward
0 new messages