Torque and tasker

[Jonathan Seymour]

Hey guys,

So I bought a car on the weekend that included a bluetooth adapter to get OBD II data.  So I can use an app like Torque to present data like RPM, gas mileage etc on my phone.

What I want to know is, is there a way to get this data through tasker and display in in a scene.  I already have a car dock scene that displays a map and some buttons.  A couple of OBD II parameters would be cool to include as well.

Might be a bit much to ask, but just thought I put the question out to the community to see if it's possible.

Cheers,

Jonathan

[Matt R]

I think your options are:
-find an app that has a Tasker plugin
-message the developer of one of the apps to see if they'll make a Tasker plugin, or an open intent that you could catch
-try to figure out what Bluetooth intents are being sent from the OBD II adapter and capture them directly with Tasker's intent receiver

Matt

[Scott Miller]

Torque does broadcast some intents, but to find out what they do, I'm afraid you will need to contact the developer of torque. There are a couple of threads here that talk about it, but none with the detail you need. At least one, though, does make a reference to the developer providing some help, so contacting him may not be so difficult. Good luck, and if you do learn anything, please post it here. There seems to be quite a few other people here that use torque, and would probably appreciate anything you find out from the developer.

[Jonathan Seymour]

Thanks, I thought that might be the case.

I've emailed the developer about a possible tasker plugin.  Never dealt with capturing bluetooth intents, so I don't even know where I'd start with that.

[Ian Hawkins]

Hi!

You'll want to do something like this:

In Tasker go to: Tasks / + / "Give a name" / + / Misc / Send Intent

There you just have to fill in:

Action: org.prowl.torque.REQUEST_TORQUE_QUIT

Package: org.prowl.torque

All other input fields can be left as tey are.

Save by pressing the green check twice.

Ian

[Ian Hawkins]

For completeness, there are also several other intents that are sent by Torque that you may also be interested in - most are pretty self-explanitory:

org.prowl.torque.OBD_CONNECTED
org.prowl.torque.OBD_DISCONNECTED
org.prowl.torque.APP_LAUNCHED
org.prowl.torque.APP_QUITTING

[ihf]

These intents are useful but what would really transform Torque is a way, preferably using a plugin, to monitor OBD variables and use them in actions.

[Brandon Horwath]

preferably using a plugin

Then contact the developer, good sir :-)

[ihf]

A Tasker plugin would be really useful if it permitted OBD values to be monitored variables in Tasker. Torque Pro would be far more extensible than it already is.

[Brandon Horwath]

Not gonna argue that.

What did developer say?

[Jacob Klein]

You guys realize the developer is Ian Hawkins who posted above?

Or at least I think it is because that's what his developer name is in the play store.

[Doug Eubanks]

When I send the org.prowl.torque.REQUEST_TORQUE_QUIT intent and I test it, Torque closes properly.

If Torque is the active application, the dashboard closes and then immediately relaunches.

Do you have any ideas?

Doug

On Wednesday, August 7, 2013 1:23:10 AM UTC-4, Ian Hawkins wrote:

[Mike Wilson]

Depending on exactly what you're trying to do, you could use Tasker's Go Home function to get back to your launcher before calling Torque's quit function.  That's what I do for my car dock and it seem to work just fine.