Elgato Key Light (sadly off) Air
6 days, 11 hours ago nablopomo elgato mdns keylightair
Back in the early days of the pandemic, when it became clear I was going to be spending a lot of my life on video calls, I decided to invest in some decent lighting, so that those in calls with me would have the delight of a clear, bright view of my face.
As part of this I bought a Key Light Air from Elgato. It's basically a well-made, bright but diffuse LED light, of which you can control the brightness and colour temperature. It also has a sturdy stand. I have this light directly pointed at my face, and another bright light pointed at the white wall beside me; between the two sources of light arriving from different angles that gives pretty decent illumination - bright, but not to shiny and without sinister shadows. And largely without dazzling me, either, which I appreciate.
It is a solution that has worked very well for years. But, a couple of days ago, it stopped working...
Naturally, when I start a call, I need to turn the lights on, and then turn them off some time later. This is fiddly to do manually: there's an app for the Key Light Air, and the other light can be controlled using a smart plug over a web interface, but switching both involves a lot of presses, which is not ideal when I'm racing to get a call set up in time.
So I wrote a short Python script that talks the respective protocols of both lights, and turns them both on/off in one go. And installed this on my phone using Termux, and even created some icons to run the script using Termux:Widget. This means I can turn both lights on or off just by pressing one icon on my phone's home screen. Fantastic!
Or it was... until a few days ago. The other light, connected to the smart plug, dutifully turns itself on and off, but the Key Light Air resolutely stays in whatever state it was. I've had occasional glitches before (where it seems to get disconnected from the wifi and so not respond for a little while), but that usually resolves quickly, and if not then power-cycling the light has always fixed things. But this is different: those do not re-enable my scripts. Indeed, it doesn't seem to be a problem with the light itself - the Elagato app still controls it just fine.
Time for some investigation.
The script is erroring out, complaining that it can't resolve the mDNS entry for the light - it looks up a service type of _elg._tcp.local. with a name of Elgato Key Light Air XXXX (where XXXX is a hex code identifying the specific light), and appears to be getting no response.
The first thing to try is running the script on a device other than my phone. I happened to have the script checked out there, so I ran it, and... it worked fine, the lamp responding quicker than ever, as if to taunt me. So what's up with running it from my phone?
This will require further investigation...
0 comments