New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Elgato Key Light integration #29592
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
# Cleanup | ||
del hass.data[DOMAIN][entry.entry_id] | ||
if not hass.data[DOMAIN]: | ||
del hass.data[DOMAIN] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't clean this up, because it is not set by the config entry.
By deleting this, if we are to reload a single config entry, we would crash on line 36, because hass.data[DOMAIN]
is no longer a dictionary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in 33023fe.
I moved it out of the setup, allowing both cleaning things up and prevent the described issue from occurring.
Is that an acceptable solution?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok to merge when final comment addressed.
Description:
Adds support for Elgato Key Lights to Home Assistant
https://www.elgato.com/en/gaming/key-light
Related issue (if applicable): n/a
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#11391
Example entry for
configuration.yaml
(if applicable): n/aChecklist:
tox
. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
python3 -m script.hassfest
.requirements_all.txt
by runningpython3 -m script.gen_requirements_all
..coveragerc
.If the code does not interact with devices: