I’ve been meaning to add my Elgato Keylight Air to HomeKit for a while, and thanks to this post on Reddit I finally worked out how. And it turned out to be pretty simple.
Pre-requisites Have a working Homebridge system connected to HomeKit. Install the homebridge-http-lightbulb plugin. Before you begin Assign your Keylight Air a static IP address via DHCP. Replace 192.168.1.80 in the JSON configuration below with the IP address you assigned in the previous step.
In a previous post, I explained how to add Flic buttons to HomeKit
using my homebridge-button-platform plugin. The same plugin can now be used
to enable HomeKit automation from an Elgato Stream Deck.
Note: The Flic Hub LR is now HomeKit certified. This plugin is provided for legacy purposes, but will not receive regular updates.
My Flic Hub LR and Flic 2 buttons finally arrived today and as my primary automation system is HomeKit, I set about working out how to get them integrated via Homebridge. The result is a generic Homebridge plugin that creates a StatelessProgrammableSwitch which is identical to a Flic in operation. It supports three press events: single, double and hold, but doesn’t maintain state.
I know a bunch of HomeKit enthusiasts that use Homebridge even with LIFX’s native HomeKit support in their newer bulbs. After the LIFX team implemented firmware effect calls in the HTTP API, I knew it would be possible to create a HomeKit switch that would turn an effect on and off and here it is.
I’m a huge fan of Homebridge and use the web interface provided by homebridge-config-ui-x extensively. I’m also a huge fan of Caddy to automate the creation and management of HTTPS-based websites using Let’s Encrypt.
Lot’s of people ask me why I’m such a fan of Caddy and it’s because configuring it to reverse proxy something is usually pretty easy. In this case, the Caddyfile for homebridge-config-ui-x is as simple as: