I am in the process of adding the ability to allow the app to work with Tasker and other apps like NFC using what is called Intents via a uri.
What type of control would you like to have. For example you can run a scene with the following:
authomation://scene?id=12
I am thinking of adding devices as well.
authomation://device?cmd=on&id=12
This would turn a binary light on. I want to start with the basics as it can get complex quick.
You can use this to incorporate into an NFC tag.
Is it possible to use a more path-centric syntax vs queryString-centric?
eg. authomation://scene/12
eg. authomation://device/12/on
Then the parameters can be used solely for any parameters to the Action… When they’re not aliased to shortcut codes (like on/off). Just a thought.
guessed,
Looking at the documentation is it certainly possible. I would just have to go based off of an array and the proper location in that array. So I would just have to make sure that is a set path standard to go buy. So after device or scene, it would be id, command, command value if required (e.g. dimmable light to set the value authomation://device/12/dim/50). The other way, all I would have had to do was look up the parameter via a key/value type. The way you have suggested would limit the amount of input to enter and would also make say NFC tag storage use less storage.
I just made the changes in the code. I want to pick up some NFC tags to give this a try.
Cool. I think this form will be simpler for people to understand for the common cases. The more complex stuff could still be fully spelled out, or use parameters, but this one will keep it memorable.
Over time, you could add variants, for less commonly aliased ServiceIds, that take the full syntax.
eg. authomation://{scene|device|room}/{id|name}/{alias|serviceId/action}/{positionalParams}{?namedParams}
Of course, not a real lex, but hopefully it gives you the picture.
Btw, if it’s possible, you might want to use authomation:/ instead of authomation://
The latter format usually implies a host name after the // … Although my formal URL syntax conventions for custom protocols might be rusty.
Unfortunately, the documentation states that you have to use the authomation:// format and it can not be anything else. This is based of the URI format. Another example would be file:// or content://, etc.
In the process of getting this all added, I am also making modifications to the code on how it identifies the devices. If you are running firmware 1.5.372 or newer, it will use a new api command that Aaron @ MCV added for me. This will be able to poll the device by device id and return the device type. So when you either first retrieve data, a new device is added, or you are upgrading from an older version of the app and the device type is empty for that device, it will retrieve this data. The reason I mention this, it requires me to rewrite some of the code in the app to use either the device type or the category number if no device type is available. So it is taking me longer to get the tasker, nfc, and 3rd party app integration implemented. In the end, this will allow me to better support plugins.
I haven’t had as much as I liked to play with my Vera lately but just wanted to say I’m a big fan of Tasker and knowing there will be a way to control my Vera with Tasker makes me really happy 
Sent from my SGSII CM9 with Tapatalk 2
would be great to see Llama integration… a free, and very good, tasker alternative.
Aaron,
Can Llama issue URI commands? This is an api interface that any app can allow for other apps to use. I will have to check out the app. But if it allows you to input a uri into the task, than it will be compatible.
Aaron,
I wanted to post an update. I downloaded the Llama app and it appears that it does support issuing a uri command (Android Intent). Let me figure out what it wants in the settings and I’ll try some tests. By the way thanks for telling me about Llama, it looks like something I can use. I was going to buy Tasker (I use to be a beta tester of the app a long time ago).
[quote=“garrettwp, post:9, topic:171891”]Aaron,
I wanted to post an update. I downloaded the Llama app and it appears that it does support issuing a uri command (Android Intent). Let me figure out what it wants in the settings and I’ll try some tests. By the way thanks for telling me about Llama, it looks like something I can use. I was going to buy Tasker (I use to be a beta tester of the app a long time ago).
cool. Yeah, I used Tasker for a while in beta also. I like Llama a lot more… I think it is more intuitive and actually can ‘automate’ a lot more things, in more ways, than Tasker.
looking forward to the Llama integration!
Not sure when this version will be released. I am making some decent changes in the back end to better support 3rd party plugins. Also making minor UI tweaks and adding little other features. I’ll provide a beta in the near future.
any ETA on Llama support? 8)
It will be in the next 2.1 release but I do not have a set date. It may be a while as I have been busy lately.
Can someone who has this working with Tasker please clue me in on how to use it? I’ve tried the syntax above in the first text field of a Tasker intent action, but I can’t get anything to happen.
Thanks in advance!
Following this homebuddy video with Tasker integration is the same as my app. Just substitute the homebuddy syntax for authomation’s syntax.
[quote=“garrettwp, post:15, topic:171891”]Following this homebuddy video with Tasker integration is the same as my app. Just substitute the homebuddy syntax for authomation’s syntax.
Is this available in the most resent version on Google Play?
Thanks for working on this, this is something I really want to do in combination with NFC tags.
It is only available as an early build for testing. If you are feeling adventurous, you can find more info here:
http://forum.micasaverde.com/index.php/topic,11517.0.html
[quote=“Quixote, post:14, topic:171891”]Can someone who has this working with Tasker please clue me in on how to use it? I’ve tried the syntax above in the first text field of a Tasker intent action, but I can’t get anything to happen.
Thanks in advance![/quote][quote=“garrettwp, post:15, topic:171891”]Following this homebuddy video with Tasker integration is the same as my app. Just substitute the homebuddy syntax for authomation’s syntax.
Okay, now I’m on topic 
I have now tried using Authomation’s syntax in both Tasker AND Llama, and in neither application does anything happen at all, just like Quixote said. I followed the Homebuddy video as well as I could, but Tasker has changed slightly. Still, the same fields that were altered in the video are available, so those are the ones I edited. Every time I run a test of the task, it does nothing. In Llama, I also try running a test of the action, and nothing happens.
Would someone mind posting instructions for how to use this? I think it’s odd that there’s nothing here about it. Once I find where I packed my NFC tags, I’m going to use the instructions Garrett posted in the beta thread to get those set up, but until then I’d like to try to get one of these other apps working.
Thanks for any instructions you can provide…
Have you seen these screen shots for Llama?
http://forum.micasaverde.com/index.php/topic,11517.msg84232.html#msg84232
The authomation syntax will be different in the pictures as I made changes over the course of the app updates. But it should give you an idea what needs to be placed into the fields.
Garrett,
Thanks for the response. I hadn’t seen those images, but now I know that I was putting the right data into the right fields. I’m using the syntax from the first page of the beta thread. The only thing I can think of is that I have the wrong number for my Vera. All I know is that I must be doing something right, because when I run a test for the intent, I don’t get an error…
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules