For those who use tasker, version 6.2 is now officially released
I have been using the beta version for some time now, particularly the HTTP Server option to be able to send HTTP requests directly to Tasker without the need for AutoRemote.
What are the advantages/disadvantages of using the HTTP request versus Join? I currently use Join for a few things.
The main one I think is that a HTTP request goes directly to Tasker, you don't need an extra add-on. You define the HTTP request as the trigger for a profile.
You can also send a response, although I can't say I looked into what is possible in that regard with the other apps.
I will still use AutoRemote I expect for some things, and have included both options in the Mobile Controller app I am building.
Very interesting. I was reading though the release notes and having a http server is very promising for those of us repurposing old phones. I have old moto Androids that do LANnouncer, etc and this would be cool for some local automations that hubitat can't do.
1 Like
Thanks to HTTP request I finally have a way of getting notifications to my phone without going through the cloud. There are some quirks with HTTP request because it won't work correctly if you send certain characters, such a colon : and other special characters.
1 Like
I'll have to test that in my app... How are you trying to send the notification message, as part of the body of the request?
I am able to include at least a colon when sending a HTTP Post from HE to Tasker, where the notification is the body of the request. I haven't tried to send it as JSON, just the plain text. I can then reference the %http_request_body in a Notify action. I do actually split the HTTP request body using a Variable split beforehand, as I include a title in the body as well, i.e. title||text.
In Tasker I have it receiving as a GET and when I send below, it will fail but removing the colon it works
http://{taskerIP}:1821//Notification?msg="Hello World. The time is HH:MM"
You would need to urlencode the URL I would think, if you want to do it that way, or at least use the right code for the colon. You should be able to construct a POST in RM, so I would think you could do the same thing I included in my previous post (as an edit to what I originally posted).
Or you could try my new app 
. It's probably not quite ALPHA any more...
From what I can tell, %3A is the equivalent code for colon...
I use webCoRE and have a single piston that handles all notifications. It decides if connected to the internet it will send via Pushover, otherwise it sends to Tasker if my phone is connected to local WiFi. I have the piston configured to convert the troublesome characters and then convert them back in Tasker's Task.
2 Likes
Sorry to bring up an old topic. @stephen_nutt How are you sending Join requests to activate actions from HE?
If you just want to use Tasker to trigger a rule or send a command to a specific device on HE, you don't need to use Join. You just need to send an HTTP Request to HE from phone using Tasker. What exactly are you wanting to achieve?
The reverse. I'd like to execute a command from RM via Join on an android device that has my tasker automation.
Tasker now has "HTTP Request" that allows it to be called in order to trigger a task. As far as I know it only works on the local LAN because it is essentially a mini web server.
1 Like
If you use Join, you don't need to be local to send a message from HE to your phone. I do this using Node Red but you are essentially sending a HTTP Request but it is going thru the Join servers so can be done remotely.
Goto:
Click on your device then "Create a Join API link for your device". Fill out the form with all of the information you want. You really only need a specific phrase in the Text field or Title field to trigger Tasker Task. Once done, click on the Show API key and it should generate an secured URL that you can use in RM.
This is what mine looks like with simply "911" in the Title Field:
https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush?apikey=xxxxxxxxxx12409aa58e3c7f41a8b4bb&title=911&deviceId=xxxxxxxxxx78433d81677889f67f2a2d with apikey and deviceId partially redacted.
Now, go to Tasker and create a Profile. For the Event, choose Join Received Push. In settings, enter the phrase you chose above in Text or Title field in appropriate location. I would put 911 in the Title field in my example. Finally, create the Task to perform when Profile is triggered.
I haven't done this in a while so I am going by memory. Hopefully this makes sense and works.
4 Likes
AHHH. This is perfect. Exactly what I was looking for. Thanks for pointing me into right direction and the steps to execute this properly. I appreciate it.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
