AutoHue

Regain control of your lights

As an Android user who’s familiar with the power that tools like Tasker can unleash, you probably can’t help but feel that there should be more use cases for your Philips Hue or Lifx smart light bulbs. Well, now with AutoHue there are! AutoHue plugs right into Tasker and allows you to control your lights based on any tasker trigger. Not sure where to starts? Check out our tutorial section!

Explore! You will love it.

AutoHue gives you all the power by allowing you to customize the exact json that will be send. Yet we make it easy to configure using a simple UI.

Bulb icon by www.Freepik.com from www.flaticon.com

Tasker’s power to control your Hue & Lifx bulbs.

Control every aspect.

The plugin supports all both Philips Hue and Lifx bulbs, and it aims to support every api provided by these manufacturers to control these lights!

Switch Power

Switch on the lights, or turn them off.

Change color

Use colors to set the mood to your liking.

Notify

Blink your light bulb, e.g. to inform you of incoming notifications!

Brightness

Set the brightness to match the moment.

Transition Time

Define how long it takes to move from one preset to another.

Tasker Variables

Need more power? Use Tasker variables to customize your tasks even further.

Basic Setup

In this tutorial we go over the basic setup of AutoHue and show how to change the state of a light.

Watch Tutorial

Using Variables

Time for the next step? Here we explain how you can use variables.

Watch Tutorial

Retrieving State

Understand the basics of variables? In this tutorial we retrieve the state of a light to toggle it.

Watch Tutorial

Hue 2.0 Variables

All the variables that will be filled after executing a Hue 2.0 action.

```
%hue_command
```
The command that was send to the bridge.
```
%hue_bridge_id
```
The id of the targeted bridge.
```
%hue_bridge_ip
```
The IP Address of the targeted Hue Bridge.
```
%hue_nr_lights
```
The number of lights that were targeted in this action. Useful to know how many %hue_response[i] to expect.
```
%hue_nr_groups
```
The number of groups targeted by this action. Useful to know how many %hue_response[i] to expect.
```
%hue_lights[i]
```
Contains the light IDs targeted by this action. The i should be replaced by the index of the light starting at 1. So when targeting three lights you would have %hue_lights1, %hue_lights2, %hue_lights3.
```
%hue_groups[i]
```
Contains the group IDs targeted by this action. The i should be replaced by the index of the group starting at 1. So when targeting three groups you would have %hue_groups1, %hue_groups2, %hue_groups3.
```
%hue_response[i]
```
Contains the response(s) from the hue bridge. The i should be replaced by the index of the light starting at 1. So when targeting three lights or groups you would have %hue_response1, %hue_response2, %hue_response3.
```
%hue_error
```
Contains an error explanation if something went wrong.
Note: Only available when ‘Continue Task After Error’ is set in Tasker.

HueState Variables

All the variables that will be filled after executing a HueState action are listed in the action configuration page. A selection includes %hue_on to indicate whether the bulb was on or off, %hue_sat which contains the current saturation value and many more. Those not listed inside the configuration screen are listed below.

```
%hue_bridge_id
```
The id of the targeted bridge.
```
%hue_bridge_ip
```
The IP Address of the targeted Hue Bridge.
```
%hue_light_position
```
The position of the light according to the Hue Bridge (and used to make this request).
```
%hue_light_id
```
The unique id of the light bulb.
```
%hue_error
```
Contains an error explanation if something went wrong.
Note: Only available when ‘Continue Task After Error’ is set in Tasker.

Available in the Play Store

Download now!