Tasker → Youtube (via Pushover)

Tasker is a fantastic Android application that gives you extensive control over your device, including interaction with popular notification platforms like Pushover. This is a Tasker project than enables Youtube control on your android device via Pushover notifications. It's a very simple example, demonstrating:

How to target a specific device
A simple but adaptable message structure

Think of Pushover as a device control stream similar to MQTT, and you can start to see the potential power.

Prerequisites

The following apps need to be set up on your device prior to installing this project:

NOTE:

The process of installing Pushover involves creating an account on Pushover.net, and registring your device. It also installs the Tasker Pushover Plugin, which is used by this project.
During the registration process you can give your device a unique name. Remember this name, as you'll need it to send notifications (explained below).

Installing

As this is a Tasker Project file, with the profiles and tasks bundled up into a single XML file, installation is straightforward (assuming the prerequisites above have been satisfied), and can be performed in 2 ways:

Method 1: Via TaskerNet (easiest)

Click this link from your android device's browser. It will open the TaskerNet page for this project.
Follow the instructions on the page to complete the import.

Method 2: Via Github (this repo)

Download the XML file to your device.
Launch Tasker
Make sure you're not in Beginner Mode
Long-press on the Home icon (the house) at the bottom left of the screen.
Select Import... from the context menu that pops up.
Find the XML file on your device and select it.
DONE

Getting Started

This tasker project reacts to Pushover notifications that match a specific pattern:

device = <device_name> # from pushover.net, optional
title = 'youtube'
body = <control_command>
url = <youtube video URL> # optional

where:

device — If you have multiple Youtube apps active on your Pushover account, you can specify which device to control with this parameter. Omitting it turns the notification into a broadcast to all devices.
title — Currently hardcoded as youtube. The title acts as the "topic" filter (i.e. using different titles gives you different topics to control even more devices).
body — While the title identifies the topic/channel, the body is the "command". It differentiates which task script gets fired.
url — This only applies to the url command, and is the URL of the Youtube video to start playing.

Control Commands

Control commands are passed in the message body of the notification:

command	description
`next`	Wakes up the screen and starts playing the next video in the current playlist.
`pause`	Pauses the currently playing video in the Youtube app and blanks the screen.
`play`	Wakes up the screen and begins playing the current video in the Youtube app.
`prev`	Wakes up the screen ahd starts playing the previous video in the current playlist.
`stop`	Stops the currently playing video in the Youtube app and blanks the screen.
`url`	Wakes up the screen and starts playing the video (specified by the `url` parameter) in the Youtube app.
`volume.down`	Decreases the volume by 1.
`volume.up`	Increases the volume by 1.

Project Details

Profiles

There are 8 profiles, one for each message type:

Youtube Pause
Youtube Play
Youtube Next
Youtube Prev
Youtube Stop
Youtube URL
Youtube Volume Up
Youtube Volume Down

Tasks

There are 9 task scripts, broken down into 6 main scripts for individual commands:

youtube-pause
youtube-play
youtube-next
youtube-prev
youtube-stop
youtube-url

One script for handling volume up and down:

youtube-volume

And two "sub-scripts" called by the others:

youtube-init — Initializes some variables, including the Project's version number.
youtube-show — Turns on the device's display. (NOTE: This is the touchiest part of the project. I'm still chasing down erratic behavior when trying to turn the display back on, especially if the device has been sleeping for some time.)

Scenes

One scene is used (as part of the device wake-up process):

youtube-wake-screen

Both the background and text are set to transparent.

Variables

name	description
`%tVol`	Temporary variable used by `youtube-volume` to set media volume.
`%VERSION`	Project version number.

Notes & Troubleshooting

This is probably common knowledge, but it wasn't to me until it happened. In mucking around with the notification settings on my device, I learned that if you "silence" the Pushover app (i.e. turn off vibration, sound, etc. so the notifications get logged to the app but not displayed), this system will not work. It needs the pop-up part of the notification system to trigger Tasker. The Pushover/Tasker integration makes sure the pop up notifications don't appear.
While I tried to use AutoInput's ability to activate the display, it only reliably turned it off for me (not completely surprising, as every phone manaufacturer has to do things just a little differently ... "product differentiation" ... yeah ...). After much googling, I've incorporated a hack that first throws up a transparent Popup scene to "wake" the device before trying to turn the screen on. The youtube-show task list handles creating a Popup based on the youtube-wake-screen scene.

Background

I have an old Android phone in the lab (actually a couple, I tend to be a bit of a packrat), and wanted to put it to use, even trivially. It occured to me that it would make a great small TV screen (since I tend to listen more than watch videos when I'm working). And, initially, it was quick to get up and get running, and I was back to work while The Red Green Show played in the background (don't judge). All was right with the world.

But, after time, it got tiresome having to reach across the desk to tap the screen. There had to be a better way. Figuring "It's Android. It can run Tasker. Tasker can control Youtube. There's got to be something already existing to handle this!", I consulted the Google ... and couldn't find much. Seems most people are interested in turning their old phones into devices that either controll their TVs or cast video to them (the TVs). I couldn't find anything about doing it the other way around (playing video on the phone while controlling it from my desktop).

Time for some creative thinking. Either:

Get Tasker to control Youtube (play, pause, next, prev, stop, etc.), OR
Get Tasker to accept input from somewhere else.

Enter Pushover, which comes with a Tasker plugin for just such a connection.

So, the general pattern is:

Create a profile in Tasker based on a Pushover Event notificication — Remember to specify a unique title and body (each profile can respond to a different title/body combination).
Create your Tasker tasks (or task scripts) for the profile — You get access to the parts of a Pushover notification through the Tasker variables the Pushover plugin exposes.
Save your work — It's easy to overlook the checkmark that appears in the top bar when there are changes to your profiles or tasks. If you don't save, any changes don't get loaded and executed.
Push a notification — Use the Pushover.net website (or something like Markus Perl's pushover-cli) to send a notification to your device with the correct title and body values.

Voilà!

ScottJWalter/tasker-youtube-pushover