Failed to connect to Elgato Key Light Air

[norburban]

The problem

I just installed an Elgato Key Light Air on my WiFi network via iOS app. When scanning the network, I find it with an mDNS Name = elgato-key-light-air-c433.local The network scan also indicates port 9123 is open as type grcp. I am able to ping both IP and mDNS from within a terminal session on HA. I have rebooted and restarted HA, and it won't auto discover. I get a 'Failed to connect' error when trying to manually configure the integration with both IP and mDNS values. Nothing shows up in the logs when I enter acceptable values. [As a test, I added :9123 to the host entry (knowing it's invalid) and the log presented errors.]

What version of Home Assistant Core has the issue?

core-2024.2.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

elgato

Link to integration documentation on our website

https://www.home-assistant.io/integrations/elgato

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (elgato) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of elgato can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign elgato Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

elgato documentation elgato source _{^{(message by IssueLinks)}}

[nicocoetzee]

I have the same issue... To ensure proper functionality of the light in Home Assistant, it is necessary to assign a static IP address. However, the light tends to switch to an IP range outside the local network, despite having a static IP set on the router. Attempts to reach out to Elgato for assistance have been unsuccessful, with long wait times on hold and no response to emails. Any advice or guidance on this issue would be greatly appreciated. Thank you.

[norburban]

@nicocoetzee - that's why it's important to use mDNS name. Unfortunately, neither IP or mDNS is working for me at the moment.

[norburban]

Hello @frenck - can you assist me with this? Neither mDNS name or IP get resolved when trying to setup the integration. It doesn't auto discover either. Other devices (like Apple TV) auto discover with no issues (as an example).

When going into SSH Terminal for an nslookup, it finds the .local mDNS value & IP address.

This also resolves: docker exec homeassistant ping elgato-key-light-air-c433.local PING elgato-key-light-air-c433.local (192.168.1.114): 56 data bytes 64 bytes from 192.168.1.114: seq=9 ttl=255 time=836.141 ms

[norburban]

Hello @frenck , Any thoughts why HA doesn't see my Key Light Air?

[kmanan]

Getting this error after upgrading to the new HA version

[BrianDagan]

Fellow Key Light Air user here; was about to throw them in the e-waste when I put a last what-I'd-thought-would-be-futile Google search in and--thanks to Google giving Reddit a crap-ton of money for exclusive search rights--led me to a thread that ended, somewhat precipitously, on a mention of having loaded this integration into their Home Assistant: https://www.reddit.com/r/elgato/comments/112ayek/lights_keep_disconnecting_key_light_air_strip/

My issues were similar--I'd reboot, reset, re-reset, (had already set up another Wi-Fi network that was 2.4 GHz only just for them anyway, but also) tweaked the crap out of the Wi-Fi settings with every conceivable yet reasonable change I thought'd help. But these things--they'd come back to their static IP, squeak out about 10-20 pings, and then die. Then maybe resurrect after a few reboots, but then the pings would drop again.

The only other thing that'd changed was having added this integration into Home Assistant and adding the Key Light Air(s) (2) to it. So I threw a continuous ping up against the lights and disabled them one-by-one in the Home Assistant integration. It took a fair amount of time (maybe 5-10 minutes) before the ping response time stabilized, but suddenly Susan. All of the machines with the Control Center app see the Key Light Air devices again ("Mostly" -Eric Cartman). Yes, these devices are still needlessly Wi-Fi-ed with the worst chipset ever apparently.

At any rate, I believe this integration's doing something that these devices don't much like--maybe polling too aggressively, or sending color temperature human-running-the-slider updates into a queue that's firing commands at an increasingly-overloaded processor on the unit itself (pings seem to climb-climb-climb-DROP-repeat when the integration's enabled).

@frenck this hypothesis is based only on observed behavior; these devices are 80% reliable as-is, but I'm back to 80% after disabling this integration's polling of my Key Light Air devices... happy to discuss more.

[BrianDagan]

Welp, so much for that theory. Yes, I did disable the integration and yes, everything's been working as-well-as-can-be-expected for these lights once again. Then I noticed a firmware update notification for 1.0.3 (222) from Control Center (can not seem to find the release notes on Elgato.com though). As expected, the firmware update was about as finicky as these lights (took 3 attempts on the first light) and after it failed once on the second light, I thought, "Wait, I have an opportunity for some A/B testing on the different firmware versions (1.0.3 (220) vs. 1.0.3 (222)) and see if the integration treats these lights better now! I enabled the integration again and...

...both lights are behaving themselves. The pings hardly (if ever) drop. On/off/on/off/multiple brightness & temperature changes... nothing could make them flake out again.

So, it seems that my blame on the integration is entirely misplaced, as clearly something else must've changed. I'll keep an eye (and a constant ping) up against both lights now that the integration's running and both lights seem happy, but I guess the TL;DR is "dang it, thought I was onto something." At any rate, sorry @frenck for the tag. Home Assistant and HACS are great, and thank you for all that you do!

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Brix1965]

Hi all, I have an Issue with Elgato EVE Light Strip. After the install process and configuration with IP (or even the name) and port the integration discover the LED Strip but say "attention required" Field "power_on_brightness" of type int is missing in Settings instance. Logs are: Unexpected error fetching elgato_10.0.2.112 data 07:50:40 – (ERRORE) Elgato Light - il messaggio si è verificato per la prima volta alle 07:08:37 e compare 42 volte Detected a device that has been reported to have firmware issues with light transitions. Transitions will be disabled for this light.

Unexpected error fetching elgato_eve-light-strip.fritz.box data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 379, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/elgato/coordinator.py", line 51, in _async_update_data self.has_battery = await self.client.has_battery() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/elgato/elgato.py", line 137, in has_battery settings = await self.settings() ^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/elgato/elgato.py", line 253, in settings return Settings.from_json(data) ~~~~~~~~~~~~~~~~~~^^^^^^ File "", line 22, in mashumaro_from_json mashumaro.exceptions.MissingField: Field "power_on_brightness" of type int is missing in Settings instance

Any ideas? Thanks in advance

[janegilring]

I faced the same issue, and noticed the light had an APIPA (169...) IP address. After updating to the latest firmware 1.0.3 (222), the device got a proper IP and is reachable from Home Assistant.

[jjpeersman]

I am already on that latest firmware since september but still encounter the 169.xxx address. i have to turn the device off and on for it to be temporarily fixed. Very weird behaviour but since the device itself is not getting a proper IP (for some unknown reason after a while), i don't think this issue is within Home Assistant.

FYI: my router is OPNSense with KEA DHCP reservations.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[norburban]

The issue remains unresolved with the latest HA versions