I am a heavy Tasker user and I have never heard of AutoXBMC. Gonna have to try this. I said in another forum thread that I had Tasker on my Ubi last year but it bricked one of my Ubi's so I was reluctant to use VNC Viewer again in fear that I may brick another.
Can you show us your Tasker profiles? I tried looking for AutoXBMC but it isnt available for the public. The creator said it was in Alpha testing. Also, in the video is XBMC on your computer or your phone? How did you get it to cast like that?
AutoXBMC is in alpha, but I use it most days and haven't had any problems with it.
You need an Autoapps subscription, which might be discouraging. I personally use almost all of Joao Dias' autoapps, however, so am happy to reward him for his extraordinary development.
To access the alpha, you just need to become a tester which you can do via the google plus community via the autoapps app in play store.
Let me know if you want advice on proceeding with that.
An alternative option would be to use Yatse and send xbmc intents from tasker, but as far as I recall that's a paid subscription feature in Yatse and it also wouldn't allow finding the 'latest' episode for example.
I am using an HTPC with eventghost and xbmc installed there.
I tell AutoXBMC the ip of the HTPC, and then it can query the XBMC over the network. It then sends the command to play the file on the XBMC, so there is no casting involved.
Happy to post the tasker profiles, but I'm at work so won't be until tonight (Australian time), sorry.
Also, in terms of bricking Ubi, all of this could be achieved without tasker on Ubi at all...
Option 1 - Ubi has tasker, autoremote and autoxbmc installed
pros - local, probably faster (not tested), more elegant
cons - might brick Ubi
Option 2 - Ubi sends autoremote message to an alternate android device that does the heavy lifting with tasker, autoremote and autoxbmc.
pros - not brick Ubi
- needs to be always powered on, and always on wifi (use keep wifi app from play store)
- if device inaccessible whole workflow fails
- inelegant (second device adds to risk of failure of workflow)
Ubi can commence either one of those options via ACB from voice command, using the autoremote direct communication http request url. That step requires no additional software installed on Ubi, you just set up in ACB to send an http request using the autoremote format and the ip address of the android device you want to use (http://localhost:1817/?message=your_message_here
for Ubi, http://192.168.x.xxx:1817/?message=your_message_here
for the alternate device if you go that route).
So it is really up to you whether you'd prefer to risk the Ubi or use an alternate android device that remains on the network at all times.