1

Problem running tasks from Google Assistant

In my car, with the phone connected via Bluetooth, I can open Google Assistant by pressing the steering wheel button. I can then say, "Run <task name> with Tasker" and it will work, but only if the phone screen is on. If the screen is off, GA responds with, "Sorry, I didn't understand that".

I believe this to be an issue with Tasker (rather than GA) because, under the same conditions, I can run other apps with no problem. Tasker is the only one that fails this way. Thus, it's a failure unique to the GA/Tasker integration.

Some important information:

  • If I'm using Android Auto, the same commands work with the screen on or off.
  • The phone is not locked and is not on the lock screen.
  • I know Tasker is not being put to sleep because I have other profiles that don't involve GA and that work under the same conditions with the screen off.
  • My phone is a Samsung S10e running Android 12.
  • My vehicle is a 2021 Chevy Equinox with factory Bluetooth and head unit.
  • I've verified that all apps are up-to-date.
Follow

5 replies

Votes Newest Oldest

Hi. Can you please give me an example of a command that works with other locally installed apps with the screen off? Thanks!

Comment
DM

Sure. With the screen off I can say, "Play <playlist> with Samsung Music" or "Play <artist> on Pandora" and both of those will work.

Comment

Ok, that's different, because that doesn't use "App Actions" like Tasker does. That simply sends a music play intent to those apps which uses a completely different system.

Maybe you could try using AutoVoice with Google Assistant instead (which also uses a different system): https://joaoapps.com/autovoice/

That should work while the screen is off...

DM

OK, thanks!

Still, it seems strange to me that there's a difference. In both cases you're opening an app and telling it what to do (execute a task or execute a playlist). I'm surprised they don't use the same type of procedure.

But then, you know the "innards" of the process and I don't.

Comment

Tasker uses this: https://developers.google.com/assistant/app/custom-intents

While media apps use normal intents like these: https://developer.android.com/guide/components/intents-common#PlaySearch

Unfortunately those are not the same :) They look the same to the user though, you're right.

RW

Any workarounds? I have this same problem with pixel buds. Starting Google assistant from my phone/screen will activate tasker as expected, but the exact same command fails when coming from pixel buds

Comment

Unfortunately I don't control this, sorry! Google set it up like that and I can't change it...

XC

Hey, I thought of a work-around that I haven't made time to implement yet. Thoughts?,

If we set tasker to monitor the UI for the text "Okay google", anything else interpreted by Google assistant will appear in the same field... then we can take the text from that field and parse it to trigger relevant tasker profiles.

Example: 

1. User: "Hey Google, I'm clocked in."

2. AutoInput is monitoring for assistant to trigger, then it monitors the on screen text, and then tasker can parse the phrase for keywords (like: ...clock...in...)

3. Triggering a task:

3A. Close Assistant

3B. Perform[New calendar event, Sound Settings, Flash "Clocked in at 00:00, phone set to vibrate"]

Comment
Reply