This is a Kotlin API for the Philips Hue lights.1 It does not use the official Hue SDK but instead accesses the REST API of the Philips Hue Bridge directly. This library has been confirmed to work with the Philips Hue Bridge API version 1.32.0.
The code is a fork of ZeroOne3010/yetanotherhueapi with a to Kotlin conversation.
- Android Support - no
java.awt.Color
dependency - Plain Kotlin API without
Optionals
- Compiles on Java 1.6
- Android API level 9 instead of 26
First, import the classes from this library:
import io.github.zeroone3010.yahueapi.*;
Then, if you already have an API key for your Bridge:
final String bridgeIp = "192.168.1.99"; // Fill in the IP address of your Bridge
final String apiKey = "bn4z908...34jf03jokaf4"; // Fill in an API key to access your Bridge
final Hue hue = new Hue(bridgeIp, apiKey);
If you don't have an API key for your bridge:
final String bridgeIp = "192.168.1.99"; // Fill in the IP address of your Bridge
final String appName = "MyFirstHueApp"; // Fill in the name of your application
final java.util.concurrent.CompletableFuture<String> apiKey = Hue.hueBridgeConnectionBuilder(bridgeIp).initializeApiConnection(appName);
// Push the button on your Hue Bridge to resolve the apiKey future:
final Hue hue = new Hue(bridgeIp, apiKey.get());
Using the rooms and the lights:
// Get a room -- returns Optional.empty() if the room does not exist, but
// let's assume we know for a fact it exists and can do the .get() right away:
final Room room = hue.getRoomByName("Basement").get();
// Turn the lights on, make them pink:
room.setState(State.builder().color(java.awt.Color.PINK).on());
// Make the entire room dimly lit:
room.setBrightness(10);
// Turn off that single lamp in the corner:
room.getLightByName("Corner").get().turnOff();
// Turn one of the lights green. This also demonstrates the proper use of Optionals:
final java.util.Optional<Light> light = room.getLightByName("Ceiling 1");
light.ifPresent(l -> l.setState(State.builder().color(java.awt.Color.GREEN).keepCurrentState()));
By default this library always queries the Bridge every time you query the state of a light, a room, or a sensor.
When querying the states of several items in quick succession, it is better to use caching. You can turn it on
by calling the setCaching(true)
method of the Hue
object. Subsequent getState()
calls well not trigger a
query to the Bridge. Instead they will return the state that was current when caching was toggled on, or the last time
that the refresh()
method of the Hue
object was called. Toggling caching off by calling setCaching(false)
will direct subsequent state queries to the Bridge again. Caching is off by default. When toggling caching on/off
there is no need to get the Light
, Room
or Sensor
from the Hue
object again: you can keep using the same
object reference all the time. Objects that return a cached state will accept and execute state changes (calls to
the setState
method) just fine, but they will not update their cached state with those calls.
Add the following dependency to your pom.xml file:
<dependency>
<groupId>io.github.tobsef</groupId>
<artifactId>yetanotherhueapi</artifactId>
<version>1.2.0</version>
</dependency>
This library is not intended to have all the possible functionality of the SDK or the REST API. Instead it is focusing on the essentials: querying and setting the states of the rooms and the lights. And this library should do those essential functions well: in an intuitive and usable way for the programmer. The number of external dependencies should be kept to a minimum. Version numbering follows the Semantic Versioning.
See CONTRIBUTING.md.
See CHANGELOG.md.
1 Java 1.6, while old already, was chosen because it is easy to install and run it on Android and a Raspberry Pi computer.