Elgato lights are known for being the perfect solution for content creators, providing high-quality illumination that enhances every stream, recording, or production. With this Homey app, you can now effortlessly manage your Elgato lights alongside all your other smart home devices, ensuring a smooth and unified control experience. Adjust brightness, color temperature, and power at the touch of a button, or include them in your custom scenes and automations to create a professional-grade environment that’s ready whenever inspiration strikes.
By integrating your Elgato lights into Homey, content creation becomes even simpler. Imagine being able to instantly set up your lighting for a shoot with a voice command or have the ideal mood lighting automatically activated when you start your stream—all in sync with the rest of your smart home. This app lets you focus more on creating great content and less on the technical details, making your workflow more efficient and enjoyable. Bring your lighting under control with Elgato Lights for Homey and create without limits.
Note: This app is not officially endorsed by Elgato.
I’ve been trying to get my hands on an Elgato Ring Light, but it seems like everywhere I look, they’ve jacked up the price to over 200% of the original MSRP.
So, I thought maybe you could help me out with some info @DJP. The Ring Light has pretty much the same features as the other Key Lights, so I should be able to set it up without even having one physically. The main thing I need to know is how it advertises itself on the network.
Could you please get me all the mDNS-SD information related to the Ring Light? You can use Discovery on macOS or Bonjour Browser on Windows to get this info.
Either a reply in this topic or a direct message is totally fine!
I am trying to setup this app - for some reason it only wants to detect one of my key lights. They are both available in control center and work fine. The only difference is the one not working correctly is the new MK.2 variant so I am not sure if there something “new and improved” there. Anyone see anything similar?
Hi @Sean_Larsen
I have a feeling that the mk.2 key lights present themselves differently on the network. Could you get me the mDNS-SD information of the Key Light that isn’t working? See my message to DJP above, on how to achieve this information.
With that information I should be able to update the driver and make it recognise the newer lights.
Here you go - it was interesting this second light didn’t show up until I actually powered it on from Control Center yet the other one did.
Funny enough when I tried to add a key light again - it appeared. So not sure if there is some new default behavior going on here or not. So I don’t know if there is anything to be done other than “power cycle your lights in control center before trying to add”
Thanks for giving it another try @Sean_Larsen and looking up the information for me.
The current implementation should recognize the MK.2 using the default Key Light driver, so I don’t need to update the discovery algorithm. That makes sense, considering it worked when you tried again.
I’ll probably just add a small notice about the power cycle on the first pairing screen, just to be safe. I’m not sure if there’s anything I can do about it not being discovered on the first try.
Appreciate the quick reply. Just very strange but glad it is working. I am tempted to chalk it up to the WiFi on these lamps not being the best. They will sometimes just stop communicating. Thanks again !
