catch an error message on tasker?

2,277 views
Skip to first unread message

RadioTop40.Net

unread,
Feb 13, 2013, 9:45:09 AM2/13/13
to tas...@googlegroups.com
Is there a way to catch an error message on tasker?

The background is to check if there is an external app working with tasker correct or not.
In my case it is the "say command" with text to speech from ivona (com.ivona.tts.voicebeta.deu.deu.marlene)
Sometimes, if it is not working I get an error message "TTS: unsupported locale co.ivona.tts:deu-DEU.".
Can I catch that message to react?

Is it generally possible to catch Errors? I know that it is possible to set "Continue task after error" but it would be very nice to know that there was an error.
In the logfile all errors are very fine listet;)

Best regards
Radioman

TomL

unread,
Feb 13, 2013, 2:02:01 PM2/13/13
to tas...@googlegroups.com
I've seen this, and it's not Tasker's fault.  I encountered a similar problem with using Loquendo TTS.  The first time I use TTS after rebooting my phone, the TTS  returns an error.  After that, it works fine.  Sometimes randomly too, if my phone has been on for days, TTS will throw an error when I try to get it to talk, and then it'll be ok.

Strangely, this procedure seems to work for me:

Task: InitTTS
1. Misc > Say > Text: " " (it's [doublequote] [space] [doublequote]), Engine: pico:eng-USA, Cont Task Immediately: no
2. Misc > Say > Text: Ready, Engine: loquendo:eng-USA, Cont Task Immediately: no

So, after reboot, I run the task InitTTS.  For some reason, saying " " with pico and then saying something with loquendo fixes the problem for the rest of the session.

Tom

Rich D

unread,
Feb 13, 2013, 2:33:48 PM2/13/13
to tas...@googlegroups.com


> Is it generally possible to catch Errors?

As far as I know it is not..  A work around I use for testing for a error is to ---set up a separate task that will repeat the error-- 'checking task'
- from the original task use 'perform task' to start the checking task ( you can send some variables with %par1, %par2.)
- in the 'checking task' do not check 'continue on error' for the action that will usually throw the error.  After that action do a return value.. 

So if you get a error you will not get a return value because the task will exit.

If you get a return value then there will be no error...

Let me know if that is not clear....

Not sure if this will work in your case but it is the only error checking I know.  You could search the group for other possible solutions..

Hope this helps in some way...  Rich..

bdanders

unread,
Feb 13, 2013, 3:40:33 PM2/13/13
to tas...@googlegroups.com
Do you know if the error message is captured by %NTITLE?


On Wednesday, February 13, 2013 9:45:09 AM UTC-5, RadioTop40.Net wrote:

RadioTop40.Net

unread,
Feb 14, 2013, 3:34:14 AM2/14/13
to tas...@googlegroups.com
I found a workaround from Pent
https://groups.google.com/forum/?hl=en&fromgroups=#!topic/tasker/_Y6QznENJgQ
It seems to work until now.
I'll check it for the next days without switching the mobile off.

THX & regards
Radioman
Reply all
Reply to author
Forward
0 new messages