Tasker Android 13

[Rhett Espinoza]

Im looking for a way for Tasker to be used as a trigger in Hubitat. Initally I am looking for a way to turn on/off a light when I remove/put my phone on a wireless charger and I thought using tasker would be the best solution

I am using it for my radio to start, before my alarm clock goes off.

Alltough i wanted to have a look at the send alarm clock function in the android app in the future.

But i am not sure if this will fit my needs.

My alarm app has events that happen some time before the alarm starts and this is very comfortable combined with tasker.

I used exactly the same one before, to dim the lights in the morning before the alarm. But then I got a child and I do not need the alarm at all now

But in the winter it is very useful as it gets very dark and difficult for me to wake up.

Location: I similarly have a small set of locations where my phone may need to do something when I arrive, like home, work, etc. This is also implemented similarly to the time of day so I can use them in other profiles and tasks.

The last bit seemed like the easiest way to get Tasker to send a command to Google Home, though it remains a bit weird waking up to my own voice. There are AutoApps to do it, but this method is simple and reliable.

But with Tasker, you can detect if a SSID is nearby (or AP MAC address if you want that added bit of specificity) and get a much faster and much tighter detection which is fast enough to be used for arrival detection.

I also use sleep as android, and had it integrated with tasker, and had it send the alarm time to domoticz (before I switched to OpenHab) every night.

And then I had lights come up in that 30min period before the alarm, which helps me a lot with waking up. It was important to me to skip this waking up routine when the alarm is off.

I use MQTT Client plugin for tasker to send mqtt message to OpenHAB. I was a total mqtt noob when I set this up, never did mqtt in OpenHAB before, stumbled thru the set up, got it working and then set tasker up to send mqtt messages.

If I have left the office, then I want to go ahead and switch off the silent profile, and back to normal. If I haven't yet left the office, I'd like the task to sleep for 15 minutes, and then try again (sometimes I work late).

Now with your latest details, a raw approach. As you are on a stock ROM, switching GPS might not work out-of-the-box. In case it doesn't work, take a look at the Secure Settings plugin, which should be able to help out.

I assume your raw concept is: 8am to 5pm is work time, and you want different settings during work hours and after leaving work, considering eventual late-work issues. So this should preferably turn out as a single profile: At work do... and After work switch to.... So here's what shoud basically work:

So you see you neither need GPS nor the 15min wait loop. At 8am the "Work" Profile gets active, and switches your phone to silent mode. As you do not really need GPS, you can define some dummy Exit Task here (e.g. again switching Silent Mode on), as otherwise Tasker would automatically revert to the "before" mode.

The second profile does not even check conditions before "Work" has completed, as Tasker remembers which Profiles are active. After that, it starts monitoring the surrounding mobile cells -- which are either known by the phone as needed for telephony. If none of the surrounding cells match any of the scanned cells, the attached task is executed and Silent Mode turned off.

Sounds like what you want is pure location-based profiles. Tasker is very powerful, but if you are willing to try an alternative, there is Llama. It is roughly the same as tasker, except that almost every action is location-based. It 'learns' a location you want to set up (like home), by scanning the antennae of the mobile network in the immediate area. That is a lot more energy-efficient than using GPS.

For the things you want to set up, Llama will be much simpler to configure. Let the phone learn the places you want to use in your conditions, and add one or more actions. E.g. "leave home" -> do "enable bluetooth" "disable wifi".

Or if you have some bespoke profiles that are unique to Tasker, you can also have Tasker trigger SharpTools rules using Rule HTTP Triggers. This is a pretty powerful feature as you can continue to use your Tasker profiles and update them to call to a Rule HTTP Trigger (and even pass in parameters). From there, you can either store things in SharpTools Variables or connect those rules up to Virtual Devices.

@josh With the SharpTools tasker app is going away. Would you be able to help explain it and possibly supply some example of how to use the http action an the API calls to help us that depends on SharpTools to interact with tasker and SmartThings.

Copy the HTTP trigger URL to your clipboard and save the rule

You can tap the copy icon in the HTTP trigger to copy it to your clipboard. You can always visit SharpTools.io from your phone and reopen the rule to more easily copy the HTTP Trigger URL.

In Tasker, you create a new profile and pick "State" and "plugin" and find "AutoLocation Geofence", press the pencil then specify one of your Geofences in the picker that appears when you press the top menu item.

Press the back button and you'll be prompted for a task name to match your profile. Enter that and you'll be at a blank screen with a plus sign in the middle of the bottom area on the screen. Once you press the plus sign, you'll then press "Plugin" and then find Mobilinc and press on that.

Long press on the task name to the right of the green arrow, then you can add an exit task to happen once you do exit your Geofence with the instructions I gave in the previous two paragraphs. Simple as that!

Before you write off Tasker because it's complicated to use, please ask as many questions as you'd like, I'll try to answer them all to the best of my ability. Hell, if you have a complicated one, you can even call me if needed.

I realize this is a very old post, but I may have a need for both these programs and would like to know if they will do what I want...Do you still use these programs? Do you still feel the same way after using them for over a year?

Each tasker profile can be setup with entry and exit action. In essence, when a profile becomes true (connected to wifi, for example), perform an action. Then, when disconnected, perform another action. I susepct it would be a trivial exercise to create an isy program to turn up the thermostat, and one tk turn it down. The tasker actions would simply initiate the programs via mobilinc.

Trivial....Sounds like something for me...I like the idea of WiFi as opposed to gps or any other battery robbing setting on my phone. I leave WiFi enabled on my phone all the time as the draw on the battery is negligible. Do both Mobilinc and Tasker have good documentation? I can make most things work, granted I have the documentation and time...

And, yes, tasker has pretty good documentation, but there was a definite learning period for me. Mobilinc was pretty intuitive, and I found minimal need for manuals. I should disclose, however, that I really don't use the mobilinc interface much. I rely near exclusively on mobilinc and tasker widgets on my home screen to control my house from phone and tablets.

Currently it seems like only dismissing any alarm is possible with Tasker. It would be nice if disabling the next alarm by label would be possible (or a currently ongoing one, if there is one). That would make it possible to specifically disable an automatically created alarm, without affecting any manually created ones. Wildcard support would be especially good.

I am able to use a shell command like this: am broadcast --user 0 -p com.urbandroid.sleep -a com.urbandroid.sleep.alarmclock.ALARM_STATE_CHANGE --es alarm_label fri --ez alarm_enabled false. That works just fine, so not sure what the differences are/what I am doing wrong. Any help would be appreciated.

It looks like your android application is trying to create an OAuth 2.0 connection here. Jira Cloud can be integrated via OAuth 2.0. We have documented how to do this over in OAuth 2.0 (3LO) for apps.

3a8082e126