Build your own UI with AutoVera and Tasker


Using the Scenes feature of Tasker, not to be confused with Scenes on Vera, you can create your own custom UI to control any and every device on your Vera. Tasker scenes give you access to a what-you-see-is-what-you-get graphical editing tool. You can use Tasker variables in combination with AutoVera Device Info actions to dynamically populate menus and actions, making custom scene creation as easy as possible.

Below is a sample APK created with Tasker and exported as a standalone application. It consists of one scene and several actions to control a dimmable device. Once installed, it will populate a spinner element (dropdown menu) that contains all of the devices on your Favorite Vera. Once a device is selected, each of the elements in the scene will control that device. You can explore the XML shared below to see how to get each element triggering AutoVera Device actions. Screenshot here:

IMPORTANT: The only dependency to run this app is AutoVera, a user would not need Tasker installed to run apps created with Tasker.

Interface elements include:

[ul][li]Button - Tap to toggle[/li]
[li]Text - Tap To toggle[/li]
[li]Number Picker - New value sets light level(Dimmable Only)[/li]
[li]Slider - New value sets light level(Dimmable Only)[/li]
[li]Toggle - On = light on, Off = light off[/li]
[li]Image - Stroke Up = light on, Stroke Down = light off[/li][/ul]

Note: If status updates are enabled for the chosen device, the Image element will update to reflect the current state.

To install and run:

[ol][li]Set a favorite Vera within AutoVera[/li]
[li]Install APK from here:[/li]
[li]Launch Scene Sample app[/li]
[li]Choose a device to control from drop down menu[/li][/ol]

I’m also including the Tasker XML for the project, the “source code”. To install:

[ol][li]Download Tasker projext XML from here:[/li]
[li]Using a file explorer, attempt to open the XML file and choose to open with Tasker[/li]
[li]A popup will let you know the project is ready for import[/li]
[li]Open Tasker and press and hold on an existing project*. Choose Import and select the XML file from the projects folder[/li][/ol]

*You’ll need to have disabled beginner mode within Tasker.



Thanks for sharing… Makes for a great blueprint to make more scenes

Sent from my GT-N7100 using Tapatalk



The status updates don’t seem to be working for me. Where does it set the light level, so you can set the slider default value to the current light level status? I don’t see where it sets the variable or where it changes the element to reflect the change

Thanks in advance!



If you want to set the slider to the current value, you’ll need to do an AutoVera Device Info action, and set a variable based on the current value of %avlevel. You can then use this variable to change the element value of the slider to the numerical value of the light level. You’ll want to run these actions before showing any scene.

Create Scene
AV Device Info
Variable Set
Element Value Set
Show Scene



This is exactly how far I’ve gotten… can you modify this to work with HUE lights? I have followed tutorials that say use OI ColorPicker, and I can get it to pop up, but I don’t know how to convert from HEX to HSB afterwards to send that to the light with an Intent (SetHueSaturation).



Here is a screen shot of my ui with tasker



I’m wondering if you may be able to help. I’m using Tasker w/ AutoVera and able to create a widget that changes icon (light) when one of my vera lights is on vs. off. What I’m unable to do is use that same widget to turn on and off the light (and also have it change icon states). Ideas on how to do this in Tasker?



Does anyone have the files referenced in the first post, or an example of how to make work?

It’s not entirely intuitive (especially in the lastest version).

Also, does anyone have examples where it is toggling lock status? the avnewstatus variable doesn’t appear to work for this.