Received Text problem

[cdikland]

When I send a sms text message to my Galaxy S3 phone the Tasker profile I have set up to intercept it fails from time to time depending on the text I send. For example, Receive Text ='testing' or 'test' (no quotes) works just fine and the linked task executes. However, Receive Text ='disableJD' or 'disablejd' or 'lostmyphone' or 'lost-my-phone' (no quotes) do not. When I include an * at the start and end of any of the previous texts all is well (i.e. '*lostmyphone*')

The thing is that JuiceDefender has no problem intercepting any of these texts without the * so why is Tasker giving me such grief. I can live with using * but I have lost confidence that this will always work. Is there something I am missing here??

 

[electricpete]

However, Receive Text ='disableJD' or 'disablejd' or 'lostmyphone' or 'lost-my-phone' (no quotes) do not.

In what way does it not work?
Did you inspect the contents of %SMSRB after receipt of such message ?
Does it not contain what you sent?
Or did it come through correctly but subsequent operations didn't work?

It may be a Tasker problem but more likely digging into the details further will reveal why it's not working.

 

[cdikland]

The same text message was sent to both JuiceDefender (to disable it) as well as e-robot. Only Tasker behaved differently until I used wild cards. The subsequent operations are a task I have been using for some time now which was previously triggered by the AutoRemote plugin but would fail when the phone went to sleep and JuiceDefender shutoff Mobile data.

 

[electricpete]

I'm not trying to be a wise guy, but...

In what way does it not work?
Did you inspect the contents of %SMSRB after receipt of such message ?
Does it not contain what you sent?
Or did it come through correctly but subsequent operations didn't work?