Tasker variable (contents of incoming sms) to webcore

#1

1) Give a description of the problem
can’t get tasker to pass the contents of a SMS message to webcore to process as it pleases. it’s probably a simple error that you guys will solve in about 3 seconds.

2) What is the expected behaviour?

I have an android phone just for the house which can receive and send text messages. I’ll add a filter at a later date, but I’d like to have tasker grab the contents of a received text, pass it onto a webcore piston in order to do…whatever with it .

3) What is happening/not happening?

text is intercepted, but kioskbrowser keeps saying “null” instead of the actual text. I’m obviously not setting the argument correctly.

4) Post a Green Snapshot of the pistonimage

image
image.png1178×461 19.7 KB

the tasker part is currently:

1. variable set
name %status To %antext

2. variable set
name %pistonURL to https://xxxxx

3. httpget
serverport %pistonURL?status=%status

(unknown device is kioskbrowser… not that it seems relevant.

5) Attach logs after turning logging level to Full

REMOVE BELOW AFTER READING
If a solution is found for your question then please mark the post as the solution.

#2

Have you tried
Speak “{status}”

Mine worked with my Echo Dot as…

Speak text “{Test_Variable}”

I am not familiar with kioskbrowser.

#3

A few observations:

  1. In Tasker, if you change %status to %Status, (capital S), then you can refer to that text message variable from other profiles. (advanced, but very cool feature)

  2. On this same note, since %pistonURL has a capital letter, it sticks (lingers), so there is no need to keep writing the same URL each execution.

  3. Perhaps more importantly though is, instead of testing Tasker and webCoRE and kioskbrowser all at the same time, why not separate to get to the root of the problem? In other words, in my test piston, I would just store the incoming args to a variable. (which is easy to verify) Once that part is working, then I’d focus on the speak section.

Just my two cents.

#4

Not familiar with the tasker portion, I would log $args.status to make webCore is receiving what you expect before echo tries to speak.

FWIW, when I am using args, i like to leave my variables initially set to nothing, then set the variable within the piston so that the data is visible. Also easier for troubleshooting as you can set the variable once then play with the rest of the code.

#5

I forgot to mention this. This is very helpful!!

#6

Thanks all, appears the ‘little knowledge is a dangerous thing’ was fairly appropriate here.

I took into account the advice above, and (also) realised I was using completely the wrong variables in tasker.

So at the minute, here’s ,my basic solution (still need to add a filter etc).

Tasker:

1. Variable set
Name %Smsmessage to %SMSRB
2. Variable set
Name %pistonURL to https://xxxxxxxxx:
3. HTTP Get
Server:port %pistonURL?Smsmessage=%Smsmessage

And my piston:

image
image.png1178×482 21.6 KB

Cheers all!

#7

Lookin’ good!

It should be easy to add now that the core concept is working…

Just be careful if you add any conditions, because they are treated as triggers by default.