The instructions to “follow the instructions” in the manual configuration section are not helpful when terminology is unclear.
Specifically, the Elgato light integration is highly unstable. It breaks more than it works, and “auto configuration” happens less (and less) frequently for me. Instead, it asks for “Host” and suggests a port (9123) I believe.
What is the “host”? I have three Elgato lights, so I’m not sure which reserved IP port I should use (and none seem to work). As there is no documentation, there’s no way to kno whether the suggested port is correct.
I’m not an IT person and admit I don’t know what I’m doing. That said, the buggy Elgato integration plus the unclear instructions are not attracting people to the Home Assistant ecosystem.
Thank you for providing me a place to provide feedback. I hope this is helpful and I don’t appear to just be a complainer. That is not my intent, but I do feel helpless and will spend more time lobbying Elgato to support Apple HomeKit, as the continuous “upgrades” that are made to Home Assistant seem to break the Elgato integrations.
I have many other devices (Bose, Samsung, Nuheat, etc.). Elgato is the most unstable by far; Nanoleaf is a distant second. All my problematic devices are LED lights I use for a home video/photography studio. It’s a shame that Lutron does not make the lights I need, as its technology is amazing and clearly confirms how powerful home automation can be when a business (or someone) has the commitment to building and maintaining a stable, relaible infrastructure).
Hey there @frenck, mind taking a look at this feedback 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 feedback.
- `@home-assistant rename Awesome new title` Renames the feedback.
- `@home-assistant reopen` Reopen the feedback.
- `@home-assistant unassign elgato` Removes the current integration label and assignees on the feedback, add the integration domain after the command.
- `@home-assistant add-label needs-more-information` Add a label (needs-more-information) to the feedback.
- `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information) on the feedback.
Feedback
The instructions to “follow the instructions” in the manual configuration section are not helpful when terminology is unclear.
Specifically, the Elgato light integration is highly unstable. It breaks more than it works, and “auto configuration” happens less (and less) frequently for me. Instead, it asks for “Host” and suggests a port (9123) I believe.
What is the “host”? I have three Elgato lights, so I’m not sure which reserved IP port I should use (and none seem to work). As there is no documentation, there’s no way to kno whether the suggested port is correct.
I’m not an IT person and admit I don’t know what I’m doing. That said, the buggy Elgato integration plus the unclear instructions are not attracting people to the Home Assistant ecosystem.
Thank you for providing me a place to provide feedback. I hope this is helpful and I don’t appear to just be a complainer. That is not my intent, but I do feel helpless and will spend more time lobbying Elgato to support Apple HomeKit, as the continuous “upgrades” that are made to Home Assistant seem to break the Elgato integrations.
I have many other devices (Bose, Samsung, Nuheat, etc.). Elgato is the most unstable by far; Nanoleaf is a distant second. All my problematic devices are LED lights I use for a home video/photography studio. It’s a shame that Lutron does not make the lights I need, as its technology is amazing and clearly confirms how powerful home automation can be when a business (or someone) has the commitment to building and maintaining a stable, relaible infrastructure).
Kind regards.
Paul Thomas
URL
https://www.home-assistant.io/integrations/elgato/
Version
2024.3.0
Additional information
No response