custom_command_tasker
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
custom_command_tasker [2013/07/14 13:55] lukakama [Variables] |
custom_command_tasker [2013/07/14 15:37] lukakama |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Guide for custom commands integrated with Tasker ====== | ====== Guide for custom commands integrated with Tasker ====== | ||
| - | ---- | ||
| - | |||
| - | |||
| - | {{:work_in_progress_svg.png?nolink|}}{{:work_in_progress_svg.png?nolink|}} **!!!WORK IN PROGRESS (available on the beta)!!!** {{:work_in_progress_svg.png?nolink|}}{{:work_in_progress_svg.png?nolink|}} | ||
| - | |||
| - | ---- | ||
| Custom commands integrated with Tasker allow to merge the infinite possibilities of Tasker with the powerful voice recognition handling of KLets, giving you the ability to create commands to perform almost everything (from [[#"Take photo" Example|taking a photo]], to change the color of the light in a room using a wireless Arduino). | Custom commands integrated with Tasker allow to merge the infinite possibilities of Tasker with the powerful voice recognition handling of KLets, giving you the ability to create commands to perform almost everything (from [[#"Take photo" Example|taking a photo]], to change the color of the light in a room using a wireless Arduino). | ||
| Line 13: | Line 7: | ||
| In order to use them at their full power, you need to firstly understand how Tasker variables work reading its [[http://www.pocketables.com/2012/08/beginners-guide-to-tasker-part-2-variables.html|Online Guide]]. | In order to use them at their full power, you need to firstly understand how Tasker variables work reading its [[http://www.pocketables.com/2012/08/beginners-guide-to-tasker-part-2-variables.html|Online Guide]]. | ||
| - | |||
| - | ... TODO ... | ||
| ===== Activation phrases ===== | ===== Activation phrases ===== | ||
| Line 29: | Line 21: | ||
| Values that can be said for a variable depends on its "Type": it can be a number, a contact name, a contact phone, a phone number, a song name etc, and it can be specified while defining the variable (it is needed because KLets must exactly know which values are allowed for a variable in order to correctly handle voice recognition inaccuracies). | Values that can be said for a variable depends on its "Type": it can be a number, a contact name, a contact phone, a phone number, a song name etc, and it can be specified while defining the variable (it is needed because KLets must exactly know which values are allowed for a variable in order to correctly handle voice recognition inaccuracies). | ||
| - | KLets variables can be used from a Tasker's task by their names in lowercase prefixed by a percent. For example, if a variable in KLets is named "SECONDS_TO_WAIT", it can be used from a task with the name "%seconds_to_wait". Complex variables like contacts or audio entries are sent to Tasker splitted in more variables, each one prefixed with the variable name and with appended information name. Plase check the table below in order to know how complex types they are translated. | + | KLets variables can be used from a Tasker's task by their names in lowercase prefixed by a percent. For example, if a variable in KLets is named "SECONDS_TO_WAIT", it can be used from a task with the name "%seconds_to_wait". Complex variables like contacts or audio entries are sent to Tasker separated in more variables, each one prefixed with the variable name and with appended information name. Plase check the table below in order to know how complex types they are translated. |
| - | Other variable types can return multiple values, like contact name or audio entries variables. Klets can manage these variables in order to sent to Tasker only a single value, asking for which one to send, or it can send all results to Tasker. You can choose how to handle them selected the variable type ending with "(single value)" or "(multiple values)". | + | Other variable types can return multiple values, like contact name or audio entries variables. KLets can manage these variables in order to sent to Tasker only a single value, asking for which one to send, or it can send all results to Tasker. You can choose how to handle them selected the variable type ending with "(single value)" or "(multiple values)". |
| Multiple values are sent to Tasker as array variables. | Multiple values are sent to Tasker as array variables. | ||
| Line 48: | Line 40: | ||
| | Audio - Artist name | Only a name of an artist | ::: | %**media_var**_type | Will contain the type of matched entry. It can be "ALBUM", "ARTIST", "SONG" or "PLAYLIST" | | | Audio - Artist name | Only a name of an artist | ::: | %**media_var**_type | Will contain the type of matched entry. It can be "ALBUM", "ARTIST", "SONG" or "PLAYLIST" | | ||
| | Audio - Song name | Only a name of a song | ::: | %**media_var**_source | Will contain the source of the media info. It can me "STANDARD" or "POWERAMP". | | | Audio - Song name | Only a name of a song | ::: | %**media_var**_source | Will contain the source of the media info. It can me "STANDARD" or "POWERAMP". | | ||
| - | | Audio - Album name | Only a name of an album | ::: | %**media_var**_media_id | Will contain the standard Android media ID when the source is "STANDARD", otherwhise it will contains the Poweramp internal ID. | | + | | Audio - Album name | Only a name of an album | ::: | %**media_var**_media_id | Will contain the standard Android media ID when the source is "STANDARD", otherwise it will contains the Poweramp internal ID. | |
| | Audio - Playlist name | Only a name of a playlist | ::: | %**media_var**_google_music_3_id | Will contain the Google Music v3 internal id only when the source is "STANDARD" and Google Music v3 is installed. | | | Audio - Playlist name | Only a name of a playlist | ::: | %**media_var**_google_music_3_id | Will contain the Google Music v3 internal id only when the source is "STANDARD" and Google Music v3 is installed. | | ||
| | Contact | A name of a contact saved inside the cotact list | CONTACT | %**contact**_name | The name displayed inside the contact list for the contact | | | Contact | A name of a contact saved inside the cotact list | CONTACT | %**contact**_name | The name displayed inside the contact list for the contact | | ||
| Line 56: | Line 48: | ||
| | ::: | ::: | ::: | %**contact_phone**_label | The label for the contact phone number as displayed inside the contact list | | | ::: | ::: | ::: | %**contact_phone**_label | The label for the contact phone number as displayed inside the contact list | | ||
| | ::: | ::: | ::: | %**contact_phone**_number | The phone number | | | ::: | ::: | ::: | %**contact_phone**_number | The phone number | | ||
| - | | Contact - Email addess | A name of a contact email. It can be only the contact name, or the name with the email label | CONTACT_EMAIL | %**contact_email**_name | The name displayed inside the contact list for the contact | | + | | Contact - Email address | A name of a contact email. It can be only the contact name, or the name with the email label | CONTACT_EMAIL | %**contact_email**_name | The name displayed inside the contact list for the contact | |
| | ::: | ::: | ::: | %**contact_email**_contact_id | The internal Android id for the contact | | | ::: | ::: | ::: | %**contact_email**_contact_id | The internal Android id for the contact | | ||
| | ::: | ::: | ::: | %**contact_email**_label | The label for the contact email as displayed inside the contact list | | | ::: | ::: | ::: | %**contact_email**_label | The label for the contact email as displayed inside the contact list | | ||
custom_command_tasker.txt ยท Last modified: 2013/09/15 13:34 by lukakama
Page Tools
